Person
Ray Bellis
Ray Bellis is listed in public internet-number registry records connected with AS30701. The record is a public registry trail, not a biography: it identifies the person name, the AS number, the organisation appearing in the same resource context, and the date BTW Media last checked the entry. Readers can use it to understand why Ray appears in directory search, how AS30701 relates to an organisation profile, and which public evidence supports the connection before following related directory entries. The evidence basis includes public RDAP and registry records. The page avoids treating registry visibility as proof of current employment, operational control, or private contact details.
What to know first
- Public roleRay Bellis appears in public internet-number registry records with technical contact responsibilities; the record states contact context, not current employment or affiliation.Medium confidence
- Source basisPublic RDAP / registry recordsMedium confidence
- Last verifiedJun 17, 2026High confidence
Basic information
- NameRay BellisHigh confidence
- Public roleRay Bellis appears in public internet-number registry records with technical contact responsibilities; the record states contact context, not current employment or affiliation.Medium confidence
- Last verifiedJun 17, 2026High confidence
Public contact and network details
- Autonomous systemAS30701High confidence
- Autonomous systemAS30511High confidence
- Autonomous systemAS30122High confidence
Related entities, projects, and resources
- Editorial contextRay Bellis and the DNS Connection That Became a Session, A TCP socket can remain open without anyone agreeing what state it carries. RFC 8490 made that distinction explicit for DNS: the connection is transport; the session is a mutually recognized set of rights, timers and obligations. Ray Bellis and his co-authors turned persistence from an optimization into an accountable protocol state.Medium confidence
- Editorial contextRay Bellis and the Proxy That Had to Forward the Unknown, A small gateway often presents itself as a helpful DNS interpreter: one address for the household, one upstream resolver, one place to cache an answer. RFC 5625, authored by Ray Bellis, starts from the more difficult premise. The gateway cannot know what DNS will mean after its firmware stops changing. Its safest authority is therefore narrow: preserve protocol meaning it does not own, expose the limits it does impose and leave the client a way around it.Medium confidence
- Editorial contextRay Bellis and the DNS Work That Turns Silence into a Usable Answer, The Domain Name System often feels instant. A person enters a name, an application learns an address, and the connection begins. Underneath that small exchange, however, a resolver may choose between UDP and TCP, cross a proxy or firewall, retry after truncation, reuse a connection, ask for several kinds of data, or wait for a server that never answers. When nothing comes back, the client cannot automatically tell whether the packet was lost, the request was unsupported, a middlebox interfered, or the server was protecting itself from an attack.Medium confidence