IETF Logo Mail Archive

Re: [netconf] configuring multi-channels

Kent Watsen <kent+ietf@watsen.net> Tue, 17 September 2019 14:42 UTC

Return-Path: <0100016d3fac842c-22414d8e-ad04-4e56-b2c9-8f25a246affa-000000@amazonses.watsen.net>
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 BA4831208D4 for <netconf@ietfa.amsl.com>; Tue, 17 Sep 2019 07:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 e7YSeZ2EB8cc for <netconf@ietfa.amsl.com>; Tue, 17 Sep 2019 07:42:22 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB5B1208B7 for <netconf@ietf.org>; Tue, 17 Sep 2019 07:42:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1568731333; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=CSynvAr32dYoO7/XxQ8JwwX/gx09MpvPcfrvLL4W8EU=; b=nT8WURqtKyT1Tbi4CI711aYTnjtV8F0QPoQmLS9Ne9zH+BnZO64D2YYE8fI5KlH8 KFxVxFUvJQZHlSL6S5FfENXNTv/TO30ymzbW+ku7XigrGpPj4/feNQqmZBZ6nR0743u BBYvize8VOegh9MWWVNEfylJE1AwpvA9Vb4MsITo=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016d3fac842c-22414d8e-ad04-4e56-b2c9-8f25a246affa-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_79B36046-637E-4CA0-9741-A907F4294707"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 17 Sep 2019 14:42:13 +0000
In-Reply-To: <20190917.121226.1164447711500530993.mbj@tail-f.com>
Cc: zhoutianran@huawei.com, "netconf@ietf.org" <netconf@ietf.org>
To: Martin Bjorklund <mbj@tail-f.com>
References: <BBA82579FD347748BEADC4C445EA0F21BEFB7101@NKGEML515-MBX.china.huawei.com> <20190917.115808.1894012459057925338.mbj@tail-f.com> <BBA82579FD347748BEADC4C445EA0F21BEFB7138@NKGEML515-MBX.china.huawei.com> <20190917.121226.1164447711500530993.mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.09.17-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Ug1fedd3EvJvy0kaIN3b1fz5wXU>
Subject: Re: [netconf] configuring multi-channels
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG 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: Tue, 17 Sep 2019 14:42:31 -0000

Martin,

As for why there is a need to configure anything on a per-channel basis, here are some possible reasons:

  - different TCP-level parameters (source IP, possibly a VRF)
  - different TLS-level parameters (TA cert, client cert)
  - different HTTP-level parameters (basic auth)

Does any of this matter?  Is the only issue if the receiver can know which line card sent the message?  Or is it needed to enable the networking connection to be established, which can somehow be different amongst the line cards?

If we purposely shun variations, then the need to configure anything per-channel goes away, which would make things much easier all around.  But then we'd have to ask, what remains in the multi-stream-originators draft?

Kent // contributor

v2.23.0 | Report a Bug | By Email