Re: Historic to be: draft-spencer-usefor-son-of-1036-01.txt

The IESG <> Mon, 21 December 2009 19:07 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id 93CFC28C162; Mon, 21 Dec 2009 11:07:14 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: RFC Editor <>
Subject: Re: Historic to be: draft-spencer-usefor-son-of-1036-01.txt
Message-Id: <>
Date: Mon, 21 Dec 2009 11:07:14 -0800
Cc:, The IESG <>,
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Dec 2009 19:07:14 -0000

The IESG has no problem with the publication of '"Son of 1036":  News Article Format and Transmission' <draft-spencer-usefor-son-of-1036-01.txt> as a Historic.

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Lisa Dusseault.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Technical Summary

   This draft was circulated to replace RFC1036 and called "son
   of 1036".  Although it was not standardized at the time, it was
   implemented and interoperable. It is being published as historic
   for the record.

Working Group Summary


Document Quality

   The protocol, although historic, is implemented.


   Lisa Dusseault is shepherding the RFC3932 review.

Note to RFC Editor

   The IESG believes it has *no note* to insert in this document,
   and no objection to its publication.