Contact

Reaching the editorial and directory team behind this networking services reference requires a clear, specific message. This page covers what information to include, how quickly responses are typically processed, what alternative channels exist, and how to locate the correct office for different request types. Structured intake improves routing accuracy and reduces the back-and-forth that delays substantive replies.

What to include in your message

Every inbound message that reaches an actionable status does so because it contains enough context for the recipient to act without a clarification round-trip. The following breakdown reflects the minimum viable information set for each major request category.

Directory listing requests should identify:

1. The organization name and primary URL being submitted
2. The service category — drawn from the taxonomy used across this reference, such as Managed Network Services, SD-WAN Services, Network Security Services, or Network-as-a-Service (NaaS)
3. The geographic scope of service delivery (national, regional, or state-specific)
4. A brief factual description of services offered — 50 to 150 words, plain prose, no superlatives

Editorial corrections or factual disputes should identify:

1. The specific page URL where the error appears
2. The exact passage in question, quoted verbatim
3. The corrected fact, with a citation to a named public source — such as an IEEE standard, an IETF RFC number, a published NIST document, or a regulatory body's official publication
4. Contact information sufficient for a follow-up if the correction requires further verification

Partnership and licensing inquiries should identify the requesting organization, the specific asset or data set of interest, and the intended use context. Requests lacking all three components are deprioritized in the intake queue.

The Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF) publish the foundational standards that underpin the technical claims made across this reference. Corrections that cite RFC documents by number or IEEE 802-series standards by designation receive faster editorial review because they reference verifiable, permanent records.

Response expectations

Response timelines differ by request type. Directory listing submissions are reviewed on a rolling basis, with an acknowledgment sent within 5 business days of a complete submission. Incomplete submissions — those missing a service category or primary URL — are not acknowledged until the missing fields are supplied.

Editorial corrections referencing a named public standard (for example, NIST SP 800-series documents or ITU-T recommendations) are prioritized over unattributed claims. Corrections involving Network Compliance and Regulatory Requirements or Zero Trust Network Services may require coordination with the subject-matter review process before a public update is posted, which can extend the timeline to 10 business days.

Partnership and licensing inquiries targeting commercial use of directory data receive a substantive reply within 7 business days.

No response timeline applies to messages that lack a request category, do not include a return email address, or consist solely of promotional language. Those messages are not entered into the review queue.

Additional contact options

Three distinct contact paths exist, each suited to a different inquiry type.

Public editorial feedback — For factual disputes or terminology clarifications involving pages such as the Network Services Glossary or Network Services Industry Standards, the preferred channel is a written message through the standard contact form. This creates a timestamped record useful for editorial tracking.

Directory data corrections — Providers whose listings appear in categories such as Fiber Optic Networking Services, Data Center Networking Services, or IoT Networking Services can submit corrections directly via the listing management process described in the Technology Services Directory Purpose and Scope reference page.

Standards body references — Questions about underlying technical definitions should first be directed to the authoritative source. The IETF maintains a public archive of all RFCs at rfc-editor.org. IEEE standards are accessible through ieee.org. NIST networking-related publications are indexed at csrc.nist.gov. Directing standards questions to those primary sources before submitting them here eliminates one iteration in the resolution process.

How to reach this office

The editorial office for this reference operates under national scope, covering US-based networking service providers and standards applicable within US regulatory frameworks. Physical correspondence is not accepted for routine editorial matters.

By category, route messages as follows:

For inquiries related to Network Services for Healthcare, Network Services for Government, or Network Services for Education, note that listings in those verticals are subject to additional editorial review against sector-specific compliance standards. The relevant regulatory frameworks — including HIPAA for healthcare networking contexts and FISMA for federal government network environments — are detailed on the corresponding reference pages. Messages referencing those verticals should name the applicable regulatory framework in the subject line to accelerate routing to the correct reviewer.

Messages that combine multiple request types — for example, a simultaneous listing request and a factual correction — should be split into separate submissions. Combined messages are logged under the first identifiable category only, which delays resolution of the secondary request.