Subject: [mile] [Technical Errata Reported] RFC6546 (3455)

From: RFC Errata System <[email-masked]>
Date: Mon, 14 Jan 2013 11:28:43 -0800 (PST)

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=3455

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

Section: 3

Original Text
-------------
If a RID system receives an improper RID message in an HTTP Request, it MUST return an appropriate 4xx Client Error result code to the requesting RID system.

Corrected Text
--------------
If a RID system receives an improper HTTP Request, it MUST return an appropriate 4xx Client Error result code to the requesting RID system.

Notes
-----
There has been some discussion of this issue on the MILE mailing list.  Another possible option for the corrected text is to say nothing at all.  That is, by changing the specification to focus on an improper HTTP request, rather than an improper RID message, the corrected text is simply a restatement of existing HTTP behavior.  (Either way, this still does constitute a technical change since we would no longer be requiring the 400 status code when the error is with the *RID* content).  On this technical point, we had consensus on the MILE mailing list:  we SHOULD NOT require an HTTP 4xx status code when there is an error with the RID content itself (as opposed to the HTTP layer).  HTTP 4xx status is reserved for errors occurring in the HTTP protocol layer.  Errors in the RID content will be reported via the RID Acknowledgement message type, with appropriate choices for the RequestStatus element, and Justification attribute.

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