Re: [Netconf] LC on subscribed-notifications-10

"Eric Voit (evoit)" <evoit@cisco.com> Fri, 16 March 2018 22:11 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 DE0A11267BB for <netconf@ietfa.amsl.com>; Fri, 16 Mar 2018 15:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 tX7O9LDeSIjf for <netconf@ietfa.amsl.com>; Fri, 16 Mar 2018 15:11:27 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 976E21201FA for <netconf@ietf.org>; Fri, 16 Mar 2018 15:11:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3374; q=dns/txt; s=iport; t=1521238287; x=1522447887; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=hL/HRXWPf5Us0MbQCkReEPQF2g3gRoFEhOInP0q7JnI=; b=EslbFzX5BzPZmPhqzWyZ9zKB5xiBad0U+znC1DL8oJtbXLr+CRvOkMot X3Z3ru/Y85eF5890qMpc9S4p1xgWZD0EyoieHxOBUiLFZGFRp7KIbyF4z WG0SOWz43aa6J4cmQge8bvBpqYrJvk/HdmvgkxZDh7FZyEFhe1BhAuvoy Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DvAAAMQKxa/4kNJK1VCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDUGZyKAqNbY17ggOBFpN7ghIKGAuEIE0CgzUhNBgBAgEBAQE?= =?us-ascii?q?BAQJrKIUlAQEBAwEBATg0CQcHBAIBCA4DBAEBDhEJBycLFAkIAQEEARIIhQgID?= =?us-ascii?q?7MRiF2CCQWFMYIUgVSEdIMeAQEDgTmGEwOMKot/CQKGBIkegVeDfIdjiS+GWgI?= =?us-ascii?q?REwGBKQEeOIFScBU6gkOCMxyOHnSOHYEYAQEB?=
X-IronPort-AV: E=Sophos;i="5.48,317,1517875200"; d="scan'208";a="85234009"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Mar 2018 22:11:26 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w2GMBQLb008101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 16 Mar 2018 22:11:26 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 16 Mar 2018 18:11:25 -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; Fri, 16 Mar 2018 18:11:25 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Qin Wu <bill.wu@huawei.com>, Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] LC on subscribed-notifications-10
Thread-Index: AdO9XMGSP4UPxNeFY0CSJ8tCCoPN1QAFFjCA
Date: Fri, 16 Mar 2018 22:11:25 +0000
Message-ID: <3959a5714da3431bbbd3bfb4c00a5c01@XCH-RTP-013.cisco.com>
References: <B8F9A780D330094D99AF023C5877DABA9AD88B6C@nkgeml513-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AD88B6C@nkgeml513-mbs.china.huawei.com>
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.229]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/hkWo5ERbqRD4y1Mm8U9FEStdIHA>
Subject: Re: [Netconf] LC on subscribed-notifications-10
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 16 Mar 2018 22:11:30 -0000

Hi Qin,

>  Qin Wu, March 16, 2018 3:34 PM
>  
> I have two comments on subscribed-notifications-10:
> 1.Why protocol parameter is defined in RPC while it is not defined in
> notification?

I think you are asking why it is *not* defined in the RPC, but it is within the notification.

The reason is that the protocol used for establishing the subscription via RPC is already part of the RPC, so it is known/implicit.

However for the notification (below), we choose to send over *all* parameters which have been configured to maximize visibility.  As protocol has been configured, it is sent.

+---n subscription-started {configured}?
   +--ro identifier               subscription-id
   +--ro protocol                 transport {configured}? ....

> Is protocol parameter can be extended to support other transport protocol?

Yes.   To do this add new identities of base "transport"

> Is there any dependency between protocol and DSCP?

No.

> 2.Section 2.7.6 said
> "   The tree structure of "subscription-completed" is almost identical to
>    "subscription-resumed", with only the name of the notification
>    changing.
> "
> Is there any key difference between "subscription-completed" and
> "subscription-resumed", it looks replay-completed is used to push All event
> record before stop time expires, would it be great to clarify this in section
> 2.7.6?

Yes, subscription-completed means that a stop-time has been reached.  Right now I am improving the definition in the YANG model for the identity to say:

This notification is sent to indicate that a subscription has finished passing event records, as the stop-time has been reached.

Thanks,
Eric

> -Qin
> > -----Original Message-----
> > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent
> > Watsen
> > Sent: Wednesday, February 28, 2018 6:09 PM
> > To: netconf@ietf.org
> > Subject: [Netconf] LC on subscribed-notifications-10
> >
> >
> > WG,
> >
> > The authors of netconf-event-notifications have indicated privately
> > that they believe this document is now ready for Last Call.
> >
> > This starts a 2.5-week Last Call on
> > draft-ietf-netconf-subscribed-notifications-10
> > [1] The LC will end on March 17, or when active threads peter out.
> >
> > Please send your comments on this thread. Reviews of the document, and
> > statement of support, are particularly helpful to the authors.  If you
> > have concerns about the document, please state those too.
> >
> > Authors please indicate if you are aware of any IPR on the document.
> >
> >
> > [1]
> > https://tools.ietf.org/html/draft-ietf-netconf-subscribed-notification
> > s-10
> >
> >
> > Kent & Mahesh
> >
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf