The document candidly categorizes itself, in Section 1, as “a pedantic network 
protocol description”. As such, I think it might be appropriate for it to 
describe DNS names as appearing in the only form that is unambiguous and 
implementation-agnostic, i.e. dot-terminated FQDN.

Having said that, even RFC 1034 admits that the non-dot-terminated form “is 
often one where the trailing dot has been omitted to save typing”, so if the 
document wants to give a nod to how DNS names are typically represented in 
practice, that would also be fine, albeit slightly less pedantic.

                                                              - Kevin

From: DNSOP <> On Behalf Of Bob Harold
Sent: Monday, April 09, 2018 4:32 PM
To: Mukund Sivaraman <>
Subject: Re: [DNSOP] New Version Notification for 

On Mon, Apr 2, 2018 at 6:26 AM, Mukund Sivaraman 
<<>> wrote:
On Mon, Apr 02, 2018 at 03:20:02AM -0700,<> wrote:
> A new version of I-D, draft-muks-dnsop-dns-squash-01.txt
> has been successfully submitted by Mukund Sivaraman and posted to the
> IETF repository.
> Name:         draft-muks-dnsop-dns-squash
> Revision:     01
> Title:                DNS squash
> Document date:        2018-04-01
> Group:                Individual Submission
> Pages:                6
> URL:            
> Status:
> Htmlized:
> Htmlized:       
> Diff:           
> Abstract:
>    This document attempts to specify current DNS protocol in squashed
>    form in a single document.

You can compare what's in section 3 (Data structure) to what's in RFC
1034 section 3.1. (Name space specifications and terminology).

I'll post revisions weekly. Reviews and participation (preferrably first
in the form of discussion to prepare a list of things to do) are


3. Data Structure

   A DNS name is printed as a concatenation left to right of the

   individual labels on the path from the node to the root, each label

   trailing with an ASCII period '.' character.  Thus a complete printed

   DNS name ends with a period character.
Not exactly.  There is no period after the zero-length root zone.
The last period is actually between the tld and the root zone.
So 'there is a period between each zone' not 'after each zone'
even though it looks like a trailing dot.

Bob Harold

DNSOP mailing list

Reply via email to