[i2rs] Call for Input from WG: I2RS error handling simplification for initial I2RS protocol

"Susan Hares" <shares@ndzh.com> Tue, 13 October 2015 08:57 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC691A1B23 for <i2rs@ietfa.amsl.com>; Tue, 13 Oct 2015 01:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Level:
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rcDUsQ8049D for <i2rs@ietfa.amsl.com>; Tue, 13 Oct 2015 01:57:55 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 122541A1B1E for <i2rs@ietf.org>; Tue, 13 Oct 2015 01:57:55 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.139;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
Date: Tue, 13 Oct 2015 04:57:53 -0400
Message-ID: <005901d10595$3f1fce10$bd5f6a30$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005A_01D10573.B80FB4B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdEFlL52fGoodKw9S7qe8w+evsk1tg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/GYolCeovvSS8IK78B6mZJBvPqSE>
Cc: jhaas@pfrc.org, 'Alia Atlas' <akatlas@gmail.com>
Subject: [i2rs] Call for Input from WG: I2RS error handling simplification for initial I2RS protocol
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 08:57:56 -0000

Currently the I2RS requirements have error handling having three parts: 

1)      "all-or-nothing", 

2)      "continue-on-error", and  

3)      "stop-on-error".

 

To provide an easier first step for the I2RS Agent for the first
implementation of an I2RS protocol,  the I2RS protocol design team suggests
reduce this to the "all-or-nothing" for the initial version.  Later versions
of the I2RS protocol can provide the "continue-on-error" or "stop-on-error"
error handling.  The earlier decision in the I2RS architecture was to
support all 3 error handling pieces.  

 

Sue Hares  and Jeff Haas