NEC's Simple Middlebox Configuration (SIMCO) Protocol Version 3.0
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: RFC Editor <email@example.com> Cc: The IESG <firstname.lastname@example.org>, <email@example.com>, firstname.lastname@example.org Subject: Re: Experimental RFC to be: draft-stiemerling-midcom-simco-09.txt The IESG has no problem with the publication of 'Simple Middlebox Configuration (SIMCO) Protocol Version 3.0' <draft-stiemerling-midcom-simco-09.txt> as an Experimental RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8262&rfc_flag=0) 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 Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-stiemerling-midcom-simco-09.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary Working Group Summary Protocol Quality This document was reviewed under RFC3932 rules by Jon Peterson. Note to RFC Editor Please include the following IESG Note boilerplate from RFC3932: The content of this RFC was at one time considered by the IETF, and therefore it may resemble a current IETF work in progress or a published IETF work. This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this RFC should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information. Also, the IESG would like to note that this specification describes a protocol invented and implemented by the NEC Corporation. At its discretion, the RFC Editor might want to request that the authors reflect that that NEC Corporation is responsible for the protocol in the title of the specification.