AS21990 Network Operations RFC 2350 description of contact and policy Liberty Security Services, LLC https://as21990.net/policies/rfc2350.txt 1. Document Information This document describes how to reach the operations desk for Autonomous System 21990, in the format defined by RFC 2350. Read section 3.1 before deciding whom to contact. AS21990 does not operate a CSIRT. It operates a network, and this describes the desk that answers for it. 1.1 Date of Last Update Version 1.0, published 2026-08-23. 1.2 Distribution List for Notifications There is no notification list for changes to this document. Changes appear at the location in 1.3. Re-read it rather than expect to be told. 1.3 Locations where this Document May Be Found https://as21990.net/policies/rfc2350.txt The copy served from that URL over HTTPS is the authoritative one. 1.4 Authenticating this Document This document is not signed. No PGP key is published for AS21990 at present (see 2.8), so a signature would not be verifiable against anything you could obtain independently. Saying so plainly is more useful than a signature you cannot check. What you can verify without trusting this file: - AS21990 and 206.109.108.0/23 are registered to Liberty Security Services, LLC. ARIN's registry is authoritative: https://search.arin.net/rdap/?query=AS21990 - https://as21990.net/.well-known/security.txt lists the same contacts as section 2. - The role addresses below are registered as points of contact with ARIN and in PeeringDB (net/40787). If those sources disagree with this document, the RIR record is correct and something here is wrong. Please tell us. 2. Contact Information 2.1 Name of the Team "AS21990 NOC" - the network operations desk for Autonomous System 21990, operated by Liberty Security Services, LLC. It is not a CSIRT and does not claim to be one. See 3.1. 2.2 Address Liberty Security Services, LLC 877 Grant Ave Lake Katrine, NY 12449 United States of America 2.3 Time Zone America/New_York (US Eastern: UTC-05:00, UTC-04:00 under daylight saving). 2.4 Telephone Number +1-845-418-3577 ext. 4 Extension 4 reaches the NOC. Use it for anything affecting live traffic, in or out of staffed hours. 2.5 Facsimile Number None. 2.6 Other Telecommunication None. 2.7 Electronic Mail Address noc@as21990.net operational and routing issues, security reports abuse@as21990.net traffic originating from our address space peering@as21990.net interconnection requests These are role addresses, not individuals. Mail addressed to a named person is slower and may not be seen at all. 2.8 Public Keys and Encryption Information None published. If you need to send something you would rather not put in plain email, write to noc@as21990.net saying so, and we will agree a channel before you send it. 2.9 Team Members Not published. Liberty Security Services, LLC is the operator, and the role addresses in 2.7 reach whoever is on duty. 2.10 Other Information Network information, routing policy and the peering process: https://as21990.net/ Vulnerability disclosure policy: https://as21990.net/policies/vulnerability-disclosure 2.11 Points of Customer Contact Email is preferred for all contact, at the addresses in 2.7. Telephone is available for matters affecting live traffic. The desk is staffed 07:00-21:00 Eastern. Outside those hours an on-call rotation covers issues affecting live traffic, and both noc@as21990.net and the telephone number in 2.4 reach the engineer on call at any hour. We publish no out-of-hours response-time target. We would rather state that than publish a figure we have not measured; the commitment is that someone is reachable, not that they will answer within a stated number of minutes. If what you are reporting affects live traffic outside staffed hours, say so in the subject line and telephone as well as writing. 3. Charter 3.1 Mission Statement To keep AS21990 and the address space it originates working correctly, and to be reachable and useful to other operators when something coming out of that space affects them. This is a network operations function, not an incident response service. We do not perform incident response for third parties, we do not analyse malware, and we do not coordinate disclosure between other organisations. What we do is answer for our own network: routing problems, abuse originating from our prefixes, and security issues in infrastructure we operate. 3.2 Constituency - Autonomous System 21990 - The IPv4 address space 206.109.108.0/23 - Liberty Security Services, LLC, and the customers to whom it assigns addresses from that space AS21990 holds no IPv6 allocation, so no IPv6 space falls within this constituency. If you are reporting an address outside 206.109.108.0/23, it is not ours whatever the report says it is. ARIN's registry will tell you who holds it. 3.3 Sponsorship and/or Affiliation Operated and funded by Liberty Security Services, LLC. No affiliation with any national CSIRT, with FIRST, or with any sector body. 3.4 Authority The NOC acts with the authority of Liberty Security Services, LLC over the resources in 3.2 and over no others. It has no authority over a customer's internal network beyond the terms of that customer's service agreement, and none at all outside the constituency. 4. Policies 4.1 Types of Incidents and Level of Support We accept and act on: - Routing incidents involving AS21990 or 206.109.108.0/23: hijacks, route leaks, RPKI or IRR problems, or a prefix originated by us that should not be. - Abuse originating from our address space: spam, scanning, compromised hosts, attack traffic. - Security vulnerabilities in infrastructure we operate, under the vulnerability disclosure policy referenced in 2.10. Support is best-effort, prioritised by effect on live traffic. Within staffed hours that covers everything above; outside them, the on-call rotation in 2.11 covers what is affecting traffic now, and the rest waits for the next staffed period. Reports concerning a customer's own systems are relayed to that customer; we do not diagnose them on your behalf. We are not a clearing house for reports about networks that are not ours. 4.2 Co-operation, Interaction and Disclosure of Information We will co-operate with other operators, with RIRs, and with CSIRTs on anything affecting our constituency, and prefer to do so directly and early. What happens to information you send us: - We do not publish your report or your identity. - We pass the technical content to whoever needs it to fix the problem, typically the customer responsible for the host or an upstream provider. If you do not want your identity passed on with it, say so and we will withhold it. - We disclose information where legal process requires it. How to serve legal process is at https://as21990.net/policies/ - We do not apply Traffic Light Protocol markings to outbound mail. We will honour TLP:AMBER or stricter markings you apply; do not assume any marking on something you did not mark yourself. 4.3 Communication and Authentication Unencrypted email is acceptable for most traffic, including routing and abuse reports. No PGP key is published (2.8), so encrypted mail cannot be received without arranging a channel first. Where you need to be certain you are talking to us rather than to somebody claiming to be us, telephone the number in 2.4 and ask. That number is registered with ARIN and can be checked there without reference to this document. 5. Services 5.1 Incident Response Within the constituency in 3.2: Triage Acknowledge the report, establish whether the resource is ours, and identify who is responsible for it. Coordination Notify the customer or upstream concerned, and keep the reporter informed while the matter is open. Resolution Act directly on our own infrastructure. For customer systems, work with the customer; where a report is serious and goes unaddressed, act under the terms of that customer's service agreement, up to and including suspending connectivity. Published response commitments exist for vulnerability reports, in the policy referenced in 2.10. For abuse and routing reports we do not publish a numerical response time, and would rather say so than publish a figure we have not measured. 5.2 Proactive Activities - RPKI: a Route Origin Authorisation for 206.109.108.0/23 is published under the ARIN trust anchor and is valid. - IRR: route objects are registered for the prefix. - Filtering: we apply RPKI origin validation and prefix filtering on BGP sessions, and neither accept nor announce bogons. - Geolocation: an RFC 8805 geofeed is published at https://as21990.net/geofeed.csv All of this is checkable without asking us, at bgp.tools, RIPEstat and ARIN. 6. Incident Reporting Forms None. Send plain email to the appropriate address in 2.7. For abuse reports please include the offending address within 206.109.108.0/23, timestamps with the time zone stated explicitly, and enough log detail to identify the traffic. Logs with no time zone are the most common reason a report cannot be acted on at all. 7. Disclaimers This document describes intent and current practice. It is not a contract and creates no obligation. Liberty Security Services, LLC accepts no liability for errors or omissions in it, or for damage arising from acting on it. Where this document and a signed agreement disagree, the signed agreement governs.