Subject: [mile] [Editorial Errata Reported] RFC6546 (3277)

From: RFC Errata System <[email-masked]>
Date: Tue, 3 Jul 2012 08:53:24 -0700 (PDT)

The following errata report has been submitted for RFC6546,
"Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6546&eid=3277

--------------------------------------
Type: Editorial
Reported by: John Field <[email-masked]>

Section: 3

Original Text
-------------
Table 1 lists the allowable RID message types in an HTTP Response for a given RID message type in the Request.  A RID system MUST be prepared to handle an HTTP Response of the given type(s) when sending the corresponding HTTP Request.  A RID system MUST NOT send an HTTP Response containing any RID message other than the one corresponding to the one sent in the HTTP Request.

(table 1 appears here)

The use of stable DNS names to address RID systems is RECOMMENDED; in addition to facilitating connection to RID systems within a consortium, these are to be used as reference identifiers for a RID system's peers.  For security purposes, RID systems SHOULD NOT return 3xx Redirection response codes, and SHOULD NOT follow any 3xx Redirection.  The protocol provides no in-band method for handling a change of address of a RID system.

Corrected Text
--------------
Insert new text just before table 1:

"An X appearing in the Callback column of Table 1 means that the exchange itself IS a callback.  In these cases the HTTP request contains a RID message that is intended to conclude an earlier RID exchange which initially returned 202.   Note that RID Acknowledgment and RID Result messages can only ever appear in an HTTP request when the message is being generated as a Callback.  However, a RID Report message that appears in an HTTP request may represent either a unsolicited Report, or a delayed Callback.  It is important to note that any RID message that is sent as a Callback must be answered with a 200, and so cannot itself generate yet another Callback."

Notes
-----
This is a request to insert some additional text to help clarify the meaning of the "X" that appears in the Callback column of table 1.   I believe this will be of benefit to implementers who must understand the message exchange patterns described in table 1 in order to properly implement the RID protocol.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6546 (draft-ietf-mile-rfc6046-bis-09)
--------------------------------------
Title               : Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
Publication Date    : April 2012
Author(s)           : B. Trammell
Category            : PROPOSED STANDARD
Source              : Managed Incident Lightweight Exchange
Area                : Security
Stream              : IETF
Verifying Party     : IESG