RFC952

Documentation

Overview

Package rfc952 encompasses portions of:

RFC 952 - "DOD INTERNET HOST TABLE SPECIFICATION"

This subpackage implements relevant methods and checks for Assumptions Section 1 defined in said document.

This package's implementation of this RFC is a work-in-progress and may not necessarily be complete!

To see the actual RFC, visit: https://tools.ietf.org/html/rfc952, or see the documentation for reference on the RFCEntity.URL() method for programmatic URL lookups.

This subpackage is currently maintained by Jesse Coretta (subcon42)

Section 1 (Assumptions)

This module currently focuses solely on Assumptions Section 1 of RFC 952 under the tone of the RFC 2119 Must and Must Not Imperatives. Conditions that are evaluated are as follows:

➡ Label (a.k.a "Name") maximum length is 24 characters, label minimum length is 2 characters

➡ Characters permitted in each label are a-z, A-Z, 0-9 and hyphen

➡ The first character of any label MUST be a-z -OR- A-Z

➡ The last character of any label MUST NOT be a hyphen

➡ Dot (".") characters are only permitted as domain component delimiters, and are not allowed in a canonical label name

Hostname Bytes

Unlike its not-so-distant ancestor RFC 1034, RFC 952 does not make any mention of length-header semantics, nor are any null terminator character requirements indicated. Thus, the spirit of this module is fairly stark in comparison.

Ultimately, a candidate RFC 952 name is in the following form "under the hood":

[][]uint8{
 []uint8{119,119,119},                 // decimal w,w,w
 []uint8{101,120,97,109,112,108,101},  // decimal e,x,a,m,p,l,e
 []uint8{99,111,109},                  // decimal c,o,m
}