NTP

NTP (Network Time Protocol) is an implementation of the NTP-related RFCs (and proposed RFCs) and provides an openly redistributable reference implementation of the software, including:

• An NTP server (ntpd, and the proposed NTP4 RFC)
• An SNTP client (sntpd, and RFC 2030, and the proposed SNTPv4 Draft RFC)
• Tools for verifying, monitoring and configuring the proper operation of the NTP server

The ntpd Server is used on a significant number of computers and routers on the Internet, in orbit around the planet, and even in outer space, providing a robust and stable platform on top of which an organization’s timing architecture can be built.

More information on the software, legal issues, security advisories, etc. can be found on the NTP project web site.

The official reference implementation of NTP and its documentation are produced by the Network Time Protocol Project, while the NTP Public Services Project, hosted at ISC, provides distribution, support, and additional development resources. Read about the latest Security information related to NTP.

INN

The InterNetNews package (INN) is a complete Usenet system. It includes innd, an NNTP server, and nnrpd, a newsreading server. INN separates hosts that feed you news from those that have users reading news. INN was originally written by Rich Salz (grab the USENIX paper Rich wrote about it here). ISC took over development of INN in 1996 after Rich was unable to continue supporting it and many variants of the software were forming.

If you are interested in receiving notice of future releases of INN, you can subscribe to the inn-announce mailing list.

At this time, ISC regrets that we do not have the resources to offer support or training on the INN software. As partnerships in this area develop, we will post updated information here.

IRRToolSet

The “Internet Routing Registry Toolset” (IRRToolSet) project at ISC is an activity proposed by the RIPE NCC. This project has been migrated from the USC Information Sciences Institute, where it was developed in 1997-2001 as the “Routing Arbiter ToolSet” (RAToolSet) project. As the RAToolSet is no longer developed by ISI but is used worldwide, the RIPE NCC proposed to migrate this project to the RIPE NCC in order to continue its development and support. The original name of the project was preserved during the transition process, but has been finally changed to IRRToolSet. Currently, the RIPE NCC has transfered maintainance of this toolset to ISC, who will be accepting code from the community and providing code maintainance.

Goals

IRRToolSet is a suite of policy analysis tools to operate with routing policies in RPSL [RFC 2622] format, registered in Internet Routing Registry(IRR). The main goal of the project is to make routing information more convenient and useful for network engineers, by providing tools for automated router configuration, routing policies analysis, and maintenance.

Functionality

The project consists of the following tools:

• RtConfig: analyzes the routing policies registered in the Internet Routing Registry (IRR) and produces router configuration files;

• CIDRAdvisor: suggests safe cidr aggregates (i.e. those that do not violate any policy constraints) that an Autonomous System (AS) can advertise to each of its neighbour ASes;

• peval: low level policy evaluation tool that can be used to write router configuration generators;

• prtraceroute: prints the route and policy information packets take to a network host;

• prpath: enumerates a list of paths between Autonomous System and specified destination;

• aoe: C++/Tcl/Tk program that displays the aut-num object for the specified Autonomous System;

• roe: C++/Tcl/Tk program that lists the routes registered by the specified autonomous system;

• rpslcheck(prcheck): syntax-checks the aut-num object for Autonomous System registered in the Internet Routing Registry (IRR).

Current Status

IRRToolset version 5.0.0 was released by ISC on 16 Jul 2010.

The project is implemented in C++ on a UNIX platform. It has been ported successfully to many platforms including: Sun Sparc stations running SunOS 4.1.3 or Solaris, FreeBSD, DEC Alphas running OSF/1, BSDI, Linux and NetBSD.

Versions starting from 4.7.2 contain aoe as well as a number of bug fixes.

Progress has been made with RPSLng (RPSL with IPv6 and multicast extentions) implementation in IRRToolSet. The prototype release contains peval, rpslcheck and RtConfig tools which already work with the new dictionary. Check the ftp site for the release. Any comments and suggestions about the prototype are appreciated.

Re-implemented peval and RtConfig are also available as a CGI script.

libbind

The libbind functions have been separated from the BIND suite as of BIND 9.6.0. Originally from older versions of BIND, they have been continually maintained and improved but not installed by default with BIND 9. This standard resolver library contains the same historical functions and headers included with many Unix operating systems. In fact, most implementations are based on the same original code.

We encourage anyone with a private copy of these libraries to investigate this modern release and consider merging back into the mainstream. ISC is willing to review code and bugfix submissions, and to accept bug fixes, for libbind. This includes the old BSD gethostbyname() API. Bug reports may be sent to libbind-bugs@isc.org. The public mailing list for discussing libbind development is bind-workers.

ISC’s libbind provides the standard resolver library, along with header files and documentation, for communicating with domain name servers, retrieving network host entries from /etc/hosts or via DNS, converting CIDR network addresses, performing Hesiod information lookups, retrieving network entries from /etc/networks, implementing TSIG transaction/request security of DNS messages, performing name-to-address and address-to-name translations, and utilizing /etc/resolv.conf for resolver configuration.

The C APIs include:

• dn_comp(3)
• dn_expand(3)
• endhostent(3)
• endnetent(3)
• fp_resstat(3)
• freeaddrinfo(3)
• freehostent (3)
• gai_strerror(3)
• getaddrinfo(3)
• gethostbyaddr(3)
• gethostbyname(3)
• gethostent(3)
• getipnodebyaddr(3)
• getipnodebyname(3)
• getnameinfo(3)
• getnetbyaddr(3)
• getnetbyname(3)
• getnetent(3)
• herror(3)
• hesiod(3)
• hesiod_end(3)
• hesiod_free_list(3)
• hesiod_init(3)
• hesiod_resolve(3)
• hesiod_to_bind(3)
• hstrerror(3)
• inet_cidr_ntop(3)
• inet_cidr_pton(3)
• ns_find_tsig(3)
• ns_sign(3)
• ns_sign_tcp(3)
• ns_sign_tcp_init(3)
• ns_verify(3)
• ns_verify_tcp(3)
• ns_verify_tcp_init(3)
• res_findzonecut(3)
• res_getservers(3)
• res_hostalias(3)
• res_nclose(3)
• res_ndestroy(3)
• res_ninit(3)
• res_nmkquery(3)
• res_nmkupdate(3)
• res_nquery(3)
• res_nquerydomain(3)
• res_nsearch(3)
• res_nsend(3)
• res_nsendsigned(3)
• res_nupdate(3)
• res_ourserver_p(3)
• res_pquery(3)
• res_setservers(3)
• sethostent(3)
• setnetent(3)

OpenReg

OpenReg is an implementation of a domain registry, such as might be used by top-level domain operators to manage the delegation of domains in a “shared registry” environment.

OpenReg:

• Supports the Extensible Provisioning Protocol (EPP), the IETF standards-track protocol for interaction between registries and registrars defined in the following RFC’s:
  
  • Extensible Provisioning Protocol (EPP)
  • Extensible Provisioning Protocol (EPP) Domain Name Mapping
  • Extensible Provisioning Protocol (EPP) Contact Mapping
  • Extensible Provisioning Protocol (EPP) Host Mapping
  • Guidelines for Extending the Extensible Provisioning Protocol (EPP)
  • Extensible Provisioning Protocol (EPP) Transport
• Is designed and debugged as a distributed multi-process system;
• Supports PostgreSQL and is designed to accommodate to very large registries;
• Publishes zone files to be served using BIND;
• Gathers comprehensive profiling and load statistics;
• Is published as free software, under a BSD-style license.