Reminder to Submit Presentations for NANOG 87
NANOG Community, The NANOG Program Committee (PC) would like to remind you that we are accepting proposals for in-person or live remote presentations at all sessions of NANOG 87, a hybrid meeting, taking place in Atlanta, Georgia on 13-15 Feb 2023. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at https://www.nanog.org/program/call-presentations/. Requested Topics: Based on feedback from our survey results, we have seen numerous requests for the following topics: - Network Automation - practical uses, how to get started - Network Future - forecast for changes in technology, design, applications - Research & Education - what research is happening now in network operations - Security - developments in, problems/solutions, various protocols of - Tutorials - all levels, IPv6, BGP, Segment Routing, DNS, MPLS, VXLAN We are looking to schedule over 1,800 minutes of content between General Session and Breakout Rooms for NANOG 87, and have confirmed 165 minutes already - so don’t wait! Presentation abstracts and draft slides should be submitted no later than Monday, 9 Jan 2023 to be considered for NANOG 87. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional, or discuss proprietary solutions. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the form Timeline for submission and proposal review: - Submitter enters abstract (and draft slides if possible) in the Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — typically within 2 weeks. - Submitter develops draft slides of talk if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic. - FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (9 Jan 2023). - PC evaluates submissions to determine presentations for the agenda (posted on 30 Jan 2023). - Submitters notified. - Agenda assembled and posted. - Final presentation slides must be submitted prior to the published deadline for slides (6 Feb 2023 for in person + live remote presentations). If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nano...@nanog.org), and a representative will respond to you in a timely manner. Otherwise, submit your talk, tutorial, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 87 Calendar of Events Date Event/Deadline Mon, 14 Nov 2022 CFP Reminder Announcement Mon, 12 Dec 2022 CFP Reminder 2 Announcement Mon, 9 Jan 2023 DRAFT Presentation Slides Due Mon, 16 Jan 2023 Topics List Published Mon, 30 Jan 2023 Meeting Agenda Published Mon, 6 Feb 2023 Final Slides DUE Sun, 12 Feb 2023 On-Site Lightning Talk Submissions Open Final slides for accepted presentations must be submitted by Monday, 6 Feb 2023. Materials received after that date may be updated on the website after the completion of the conference. We look forward to seeing you in February! Sincerely, Cat Gurinsky Program Committee Chair Sent on behalf of the NANOG PC
[NANOG-announce] Reminder to Submit Presentations for NANOG 87
NANOG Community, The NANOG Program Committee (PC) would like to remind you that we are accepting proposals for in-person or live remote presentations at all sessions of NANOG 87, a hybrid meeting, taking place in Atlanta, Georgia on 13-15 Feb 2023. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at https://www.nanog.org/program/call-presentations/. Requested Topics: Based on feedback from our survey results, we have seen numerous requests for the following topics: - Network Automation - practical uses, how to get started - Network Future - forecast for changes in technology, design, applications - Research & Education - what research is happening now in network operations - Security - developments in, problems/solutions, various protocols of - Tutorials - all levels, IPv6, BGP, Segment Routing, DNS, MPLS, VXLAN We are looking to schedule over 1,800 minutes of content between General Session and Breakout Rooms for NANOG 87, and have confirmed 165 minutes already - so don’t wait! Presentation abstracts and draft slides should be submitted no later than Monday, 9 Jan 2023 to be considered for NANOG 87. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional, or discuss proprietary solutions. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the form Timeline for submission and proposal review: - Submitter enters abstract (and draft slides if possible) in the Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — typically within 2 weeks. - Submitter develops draft slides of talk if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic. - FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (9 Jan 2023). - PC evaluates submissions to determine presentations for the agenda (posted on 30 Jan 2023). - Submitters notified. - Agenda assembled and posted. - Final presentation slides must be submitted prior to the published deadline for slides (6 Feb 2023 for in person + live remote presentations). If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nano...@nanog.org), and a representative will respond to you in a timely manner. Otherwise, submit your talk, tutorial, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 87 Calendar of Events Date Event/Deadline Mon, 14 Nov 2022 CFP Reminder Announcement Mon, 12 Dec 2022 CFP Reminder 2 Announcement Mon, 9 Jan 2023 DRAFT Presentation Slides Due Mon, 16 Jan 2023 Topics List Published Mon, 30 Jan 2023 Meeting Agenda Published Mon, 6 Feb 2023 Final Slides DUE Sun, 12 Feb 2023 On-Site Lightning Talk Submissions Open Final slides for accepted presentations must be submitted by Monday, 6 Feb 2023. Materials received after that date may be updated on the website after the completion of the conference. We look forward to seeing you in February! Sincerely, Cat Gurinsky Program Committee Chair Sent on behalf of the NANOG PC ___ NANOG-announce mailing list NANOG-announce@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog-announce
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 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 12 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: 914964 Prefixes after maximum aggregation (per Origin AS): 345602 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 441991 Total ASes present in the Internet Routing Table: 73771 Prefixes per ASN: 12.40 Origin-only ASes present in the Internet Routing Table: 63375 Origin ASes announcing only one prefix: 26011 Transit ASes present in the Internet Routing Table: 10396 Transit-only ASes present in the Internet Routing Table:421 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: 1047 Number of instances of unregistered ASNs: 1049 Number of 32-bit ASNs allocated by the RIRs: 40587 Number of 32-bit ASNs visible in the Routing Table: 33639 Prefixes from 32-bit ASNs in the Routing Table: 163086 Number of bogon 32-bit ASNs visible in the Routing Table:10 Special use prefixes present in the Routing Table:1 Prefixes being announced from unallocated address space:520 Number of addresses announced to Internet: 3064036352 Equivalent to 182 /8s, 161 /16s and 124 /24s Percentage of available address space announced: 82.8 Percentage of allocated address space announced: 82.8 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: 310802 APNIC Region Analysis Summary - Prefixes being announced by APNIC Region ASes: 239088 Total APNIC prefixes after maximum aggregation: 68087 APNIC Deaggregation factor:3.51 Prefixes being announced from the APNIC address blocks: 233936 Unique aggregates announced from the APNIC address blocks:96889 APNIC Region origin ASes present in the Internet Routing Table: 13046 APNIC Prefixes per ASN: 17.93 APNIC Region origin ASes announcing only one prefix: 3757 APNIC Region transit ASes present in the Internet Routing Table: 1749 Average APNIC Region AS path length visible:4.6 Max APNIC Region AS path length visible: 28 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8299 Number of APNIC addresses announced to Internet: 773753216 Equivalent to 46 /8s, 30 /16s and 137 /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-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:267115 Total ARIN prefixes after maximum aggregation: 121839 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 268506 Unique aggregates announced from the ARIN address blocks:129060 ARIN Region origin ASes present in the Internet Routing Table:19064 ARIN Prefixes per ASN:
Re: Why do ROV-ASes announce some invalid route?
> ROV belongs on the input path, let's not ROV on the output towards > customers / route collectors. 8893 randy
Re: Re: Why do ROV-ASes announce some invalid route?
On Fri, 11 Nov 2022 at 14:00, Christopher Morrow wrote: > Also, also, possibly the output path on the session(s) here is not > filtering in an OV fashion. ROV belongs on the input path, let's not ROV on the output towards customers / route collectors. Announcing bigger, ROV valid/unkown aggregates, while really routing based on possibly ROV-invalid more specifics in the FIB is akin to actively obscuring routing security, "cheating" your way to a RAS. Yes, there are some very specific situations where output ROV is beneficial (a peering box not supporting ROV and you ask your peer to ROV their output), but let's not normalize ROV on the output path. Thanks, Lukas
Contact for AS 19338
Hello 'body, I'm looking for a NOC contact for AS 19338, the old Telmex Chile AS. Anybody have anything? Thanks, Elmar.
Re: Re: Why do ROV-ASes announce some invalid route?
There are 2 sides to the bgp conversation for any ASN, and then really 4 sides. customer -> RAS -> peer (settlement-free) peer(sfp) -> RAS -> customer customer -> ras -> transit transit -> ras -> customer Depending on the RAS's capabilities or status in their journey to 'fully RAS', it's possible that they may have: o "We OV all customer sessions" (notably not SFP peers) o "We OV all sessions(*)" (noting not all, and maybe depending on platform specifics) There are a bunch of ways this goes wrong :( This also doesn't really tell what sort of peering the RAS has set up with RouteViews (customer? peer? partial peer?) Also, also, possibly the output path on the session(s) here is not filtering in an OV fashion. On Thu, Nov 10, 2022 at 9:13 AM 孙乐童 wrote: > > Hello Job, > Thank you very much for your reply! I got that no AS can actually filter > all the invalids. Yet I was trying to figure out why we couldn't see > reasonable amount of withdrawals from AS6939 about invalid prefixes, as they > explained how they implement ROV > (https://mailman.nanog.org/pipermail/nanog/2020-June/108309.html). Perhaps we > need to learn their detailed implementations. > Thank you very much! > > Best wishes, > Sun Letong > > 在2022-11-08 00:11:24,Job Snijders写道： > > Dear 孙乐童, > > > > On Mon, Nov 07, 2022 at 08:40:57PM +0800, 孙乐童 wrote: > > > We learned from Cloudflare's https://isbgpsafeyet.com/ that some ASes > > > have deployed RPKI Origin Validation (ROV). However, we downloaded BGP > > > collection data from RouteViews and RipeRis platforms and found that > > > some ROV-ASes can announce some invalid routes. For example, from RIB > > > data at 2022-10-31 00:00:00, 13 out of 17 ASes which declared to > > > deploy ROV announced invalid routes, and we list the number of related > > > prefixes for each AS below. > > > > > > [snip] > > > > > > As a comparison, we count the invalid routes the non-ROV ASes (also > > > declared in https://isbgpsafeyet.com/) announces, as below: > > > > > > We can see that ROV ASes announced apparently fewer invalid routes > > > compared to the non-ROV ASes, though they did not filter all the > > > invalids. > > > > > > [snip] > > > > > > Can anyone help us to correctly interpret this case? Thank you very much. > > > > You ask great questions! I hope an answer to your questions can be found > > in a message I sent a year ago: > > > > https://mailman.nanog.org/pipermail/nanog/2021-April/213346.html > > > > The summary: in any sufficiently large network, chances are not 100% of > > all equipment supports RPKI-based BGP Route Origin Validation; in such > > cases a handful of invalid routes may still percolate through the > > system. Another contributing factor might be certain types of software > > upgrades; where ROV temporarily is disabled on one or more devices. Or > > perhaps an ISP made a handful of exceptions for test/beacon invalid > > routes to propagate. > > > > Kind regards, > > > > Job >
