IETF Logo Mail Archive

Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 13 June 2018 15:56 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4B7130F35 for <netconf@ietfa.amsl.com>; Wed, 13 Jun 2018 08:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Pw9DoIfh-2ze for <netconf@ietfa.amsl.com>; Wed, 13 Jun 2018 08:56:16 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70AD7130EA3 for <netconf@ietf.org>; Wed, 13 Jun 2018 08:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2172; q=dns/txt; s=iport; t=1528905376; x=1530114976; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=2h99aGe4Mr3jFREj1CfhB3wbbjXSYgJHI9CVASOQPsY=; b=e9Ii5hDJZ/JHutn3qD3tdJqpKxVp1UQlJXWK5IF8zgp3KCA4MKHNKgtL y5VJ3KWs+IS9rG1PeZVzPwSPTnj2z7gdVflzVusPaEpesCkRTca4rUbjW vgF4H/T+aCrBxFm7oNnxqSCV9ioYhrKwPhala71lMOPcXNZ+0FLRzlss1 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C8AAA9PSFb/4sNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYNIgWEoCoNviASMaYF/lGmBeAuEbAIXgiAhNBgBAgEBAQEBAQJtKIUoAQEBAQIBIxFDAgUHBAIBCA4DBAEBAwImAgICMBUICAIEAQ0FCIUTCKxHghyIR4FogQuHQIFUP4Qbh3SCVQKZCgkCjnGNPJEWAhETAYEkHTiBUnAVgn6QT2+OEIEaAQE
X-IronPort-AV: E=Sophos;i="5.51,219,1526342400"; d="scan'208";a="129149804"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2018 15:56:15 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id w5DFuFt0017144 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jun 2018 15:56:15 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 13 Jun 2018 11:56:14 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Wed, 13 Jun 2018 11:56:14 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Kent Watsen <kwatsen@juniper.net>, Martin Bjorklund <mbj@tail-f.com>, "alex@clemm.org" <alex@clemm.org>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
Thread-Index: AQHT/nTB7wTodISdV0qlE/sux4czBKRU8kawgAFinID///zC4IAAXMiA//++zTCABv5KgP//v8BQAAsePAAAGyL5IA==
Date: Wed, 13 Jun 2018 15:56:14 +0000
Message-ID: <c311c3772cf94db490fdf5251051ab1c@XCH-RTP-013.cisco.com>
References: <381e3937e0054984812ea69de97c7659@XCH-RTP-013.cisco.com> <20180608.110205.217184993423575402.mbj@tail-f.com> <9f987f8f571e4a499c589f4be02c0407@XCH-RTP-013.cisco.com> <20180608.162233.994500338881044294.mbj@tail-f.com> <acfc0df721cb475d9b1c829d1f7f5dd7@XCH-RTP-013.cisco.com> <A58C7A8F-B926-4417-8080-685C0DB5E040@juniper.net> <b44492127969401f8b72f2e3dd67d58e@XCH-RTP-013.cisco.com> <4A685312-E065-4DF6-9BB1-BCC52947F1CA@juniper.net>
In-Reply-To: <4A685312-E065-4DF6-9BB1-BCC52947F1CA@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/b_7Z_C7vVrXPcL8JgxIeVax5czE>
Subject: Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2018 15:56:20 -0000


> -----Original Message-----
> From: Kent Watsen <kwatsen@juniper.net>
> Sent: Tuesday, June 12, 2018 6:45 PM
> To: Eric Voit (evoit) <evoit@cisco.com>; Martin Bjorklund <mbj@tail-f.com>;
> alex@clemm.org
> Cc: netconf@ietf.org
> Subject: Re: [Netconf] comments on draft-ietf-netconf-subscribed-
> notifications-12
> 
> 
> 
> 
> >> Sure, but can YP import the "Event Record" term from SN?
> >>
> >> Sure.  It imports other terms.  Alex, do you want to bring it in?
> >>
> >> Also, I think that the definition could be improved.  It currently reads:
> >>
> >>    Event record: A set of information detailing an event.
> >
> > Yes.  But the word 'event' here is itself defined as:
> >
> >   Event: An occurrence of something that may be of interest.  Examples
> >   include a configuration change, a fault, a change in status, crossing
> >   a threshold, or an external input to the system.
> >
> >Reviewers have liked separation of the event itself from the record about it.
> 
> 
> I'm okay with separation.  On one hand, it seems like common English, but it
> might be good to have it well-defined in this draft.  Still it seems that the
> definition could be improved, maybe by contrasting it to an event?
> One is the what happened, the other a record about what happened...

What I am hearing from you is:

Event record: A set of information detailing an event.  This information is different from the event itself, and provides a recorded history of what happened.

If yes, I am fine with this.

Eric

> Kent // contributor
> 
>

v2.26.15 | Report a Bug | By Email | System Status