[I2rs-proto-dt] reducing the error state to "all or nothing"

[I2rs-proto-dt] reducing the error state to "all or nothing" - please reply by 5pm PT today

"Susan Hares" <shares@ndzh.com> Mon, 12 October 2015 15:56 UTC

From: Susan Hares <shares@ndzh.com>
To: i2rs-proto-dt@ietf.org
Date: Mon, 12 Oct 2015 11:56:52 -0400
Message-ID: <004401d10506$9cc2cd90$d64868b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01D104E5.15B2B430"
Thread-Index: AdEFBoRRXAT+iWYiSYqBpEJKjvDxIA==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/WA6IDheoOpprxi_1OSwqsT0xhAc>
Subject: [I2rs-proto-dt] reducing the error state to "all or nothing" - please reply by 5pm PT today
Precedence: list

Currently the I2RS requirements have error handling having three parts: 

1)      "all-or-nothing", 

2)      "continue-on-error", and  

3)      "stop-on-error".

 

For the first implementation of an I2RS protocol, I would like to suggest we
reduce this to "all-or-nothing".  Later versions of the I2RS protocol can
pick up the "continue-on-error" or "stop-on-error" error handling. 

 

Please let me know if you have any problems with this reduction.

 

Sue

[I2rs-proto-dt] reducing the error state to "all … Susan Hares