IETF Logo Mail Archive

Re: [i2rs] ephemeral requirements - REQ 08 bullet 1

Jeffrey Haas <jhaas@pfrc.org> Thu, 02 June 2016 14:24 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF3C12D140 for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 07:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 pwbqLSvVZxc6 for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 07:24:30 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C60A312D738 for <i2rs@ietf.org>; Thu, 2 Jun 2016 07:16:03 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 055D91E335; Thu, 2 Jun 2016 10:21:39 -0400 (EDT)
Date: Thu, 02 Jun 2016 10:21:38 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Linda Dunbar <linda.dunbar@huawei.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "i2rs@ietf.org" <i2rs@ietf.org>
Message-ID: <20160602142138.GT17462@pfrc.org>
References: <f9dd38f6-8350-ab9e-a880-c27dfd2a610d@joelhalpern.com> <4A95BA014132FF49AE685FAB4B9F17F657EAD7E1@dfweml501-mbb> <bf913585-d4ab-bd94-7c60-6ab292bebcf4@joelhalpern.com> <4A95BA014132FF49AE685FAB4B9F17F657EAD911@dfweml501-mbb> <20160602105028.GB26659@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160602105028.GB26659@elstar.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/LdURvTL3pcnc2M8tOK0MjuIiVkk>
Subject: Re: [i2rs] ephemeral requirements - REQ 08 bullet 1
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 02 Jun 2016 14:24:31 -0000

On Thu, Jun 02, 2016 at 12:50:28PM +0200, Juergen Schoenwaelder wrote:
> I understood the proposed text as 'be able to determine whether the
> protocol implementation supports the mechanisms required by I2RS',
> which is different from 'needing a reliable communication channel'.

+1

Whether this is simply considered a profile of netconf/restconf is fine, in
my opinion.

-- Jeff

v2.23.0 | Report a Bug | By Email