IETF Logo Mail Archive

[Netconf] Issue SN #4: Can Transport vary across different receivers of a single configured subscription?

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 15 November 2017 03:43 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 AD830126C22 for <netconf@ietfa.amsl.com>; Tue, 14 Nov 2017 19:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 qyNr4t8-ASiR for <netconf@ietfa.amsl.com>; Tue, 14 Nov 2017 19:43:27 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A1CE126B72 for <netconf@ietf.org>; Tue, 14 Nov 2017 19:43:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16767; q=dns/txt; s=iport; t=1510717407; x=1511927007; h=from:to:subject:date:message-id:mime-version; bh=eyX0iN/xAgb/pcWlgXAfN4aXyHb9Hgw0J1UR4QxgBRU=; b=mc1J4GTLW3eSQ+W+CkVYi4EQIwsDHd9pD8FZtt96/IbnUyjwO1eLmSCV WCKcD007xFt4SPTj2mBibOVFv0DwwPFR/Vh+CbyzKaY0vAxGd5QS37yNZ gCqk5MGi24eyUu+tuYn3jxx6VxKnHgNHxZyhcH9CFL1yU7uJYvWIc4eK8 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CpAAAotwta/5tdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYJEcmRuLo4WjzGYVIIRCiOKGz8YAQEBAQEBAQEBax0LhVJeAS1TJgEEG4k3ZBCsf4sYAQEBAQEBBAEBAQEBAQEcBYM0ggeBVZAjBaI0AodrjRCTS4xtiRECERkBgTgBHziBc3oVgy6DEIFOhxorgQiBEQEBAQ
X-IronPort-AV: E=Sophos; i="5.44,398,1505779200"; d="scan'208,217"; a="31037291"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Nov 2017 03:43:26 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id vAF3hQki016016 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <netconf@ietf.org>; Wed, 15 Nov 2017 03:43: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; Tue, 14 Nov 2017 22:43:25 -0500
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; Tue, 14 Nov 2017 22:43:25 -0500
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Issue SN #4: Can Transport vary across different receivers of a single configured subscription?
Thread-Index: AdNdw8aKy+YwdoNoSQ+TUlgDzy0olQ==
Date: Wed, 15 Nov 2017 03:43:25 +0000
Message-ID: <868e65f523c04a38b696649cfaec3666@XCH-RTP-013.cisco.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.68.215.19]
Content-Type: multipart/alternative; boundary="_000_868e65f523c04a38b696649cfaec3666XCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/QnQXqSJeMNy07nYaluCTq-Un6tc>
Subject: [Netconf] Issue SN #4: Can Transport vary across different receivers of a single configured subscription?
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: Wed, 15 Nov 2017 03:43:31 -0000

In the WG session tomorrow, I am hoping to get "hum feedback" on:



draft-ietf-netconf-subscribed-notifications

https://github.com/netconf-wg/rfc5277bis/issues/4



The two choices and their issues exposed during the two week review on "Can Transport vary across different receivers of a single configured subscription?" are:



(1) Yes, Transport can vary by receiver

*        Fewer subscriptions (scale benefit)

*        Can convert transport without requiring an application to learn a multiple subscription ids

*        No duplication of content during transport conversion.

*        (Potential confusion in allowing transport to vary, but encoding not to vary?)



(2) No, only one Transport across all subscriptions

*        Simpler model

*        But applications may need to create and track multiple subscription-ids for the same content.

*        Temporary duplication of content streams during transport change.



The current draft does (1).



Thanks,

Eric

v2.23.0 | Report a Bug | By Email