IETF Logo Mail Archive

Re: [netconf] SN and indirection

Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 01 November 2019 01:35 UTC

Return-Path: <mjethanandani@gmail.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 E6F3B120111 for <netconf@ietfa.amsl.com>; Thu, 31 Oct 2019 18:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rIpJIshlln4U for <netconf@ietfa.amsl.com>; Thu, 31 Oct 2019 18:35:07 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D23120071 for <netconf@ietf.org>; Thu, 31 Oct 2019 18:35:07 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id x195so2362396pfd.1 for <netconf@ietf.org>; Thu, 31 Oct 2019 18:35:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=SgG4/tJ+UCf/l1vjGJZQGytQ/RBiy6lCLXzGEX402Lg=; b=GfqqOhdyfw4bwXApDAJQEz1RVBc8vMmI69+68hBv65vT+qL7tT5DZXzQRqpMyuJ4a7 hp6dsv8H2D94AXSjWCnPAUXeCqzXWYlyk5tr9t5Dmxq8csuV0EpcB9e/E8/GrjKORrLO KewaihBkeD/oKoZy3iGKD7SfubUBio3YiXUx0vfA4df/o0p4EI0EclkITIQJqp1i6cpd iDcjBpVQfzwdVxOStrU3Ahi5O7ca7O5gpN3myzg2PZkyD4gIW0bC0qF2saqootFEZFLW VTzecVwir4SqS6KLpS0ECJ/m2o3S+nxedybHpJJ8QGznu0Ssqny/FlMXqrRQqfsozzSC y8Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=SgG4/tJ+UCf/l1vjGJZQGytQ/RBiy6lCLXzGEX402Lg=; b=Bg2pHOhcW+PwpqGyXwYpeH5Q2PRRtZahCQtLijzHIPbcD20PvfvQZ0z1sMvBCUb11p cvnYBP7m7i/0cqxF2hDgMmvAa6mEwNUWDvGBmgqqA5/nJ/PIPwHyFLwuCBqUWScEkU7q CWzHx6uj84IpgeISsEC3ZiDyia1r/L3A+YSGaAuD9TQwEcuIMXlvEee5K045cxWNKJrn oyNL2ssvLRa82emlRyNGG1MRwvZIgQre8Yomy/1uari7ZY/IQ0uEWtFT6i60f97OSRmC XUoam2qS09pLBUCb/FRkuxt+YGafYhJdIQGbHV4eAGk79JCRcNX5Teww8+aPe4yz+Jjt 1KGw==
X-Gm-Message-State: APjAAAUQvOchTtDNPW9p+TaWHAEiZffufyboRzKK3/8vw9w2ee3+AGD6 onr50b1ldS7zwM3lVgOtvdg=
X-Google-Smtp-Source: APXvYqy01DVMlBaxSq8aozrnrb3D7/es3oU0Lie5n/icewFDegA6A6GQ3msliyPzMLzR1k6aKMkkww==
X-Received: by 2002:a63:c74e:: with SMTP id v14mr10510381pgg.334.1572572106585; Thu, 31 Oct 2019 18:35:06 -0700 (PDT)
Received: from [10.33.123.155] ([66.170.99.2]) by smtp.gmail.com with ESMTPSA id c184sm5173912pfc.159.2019.10.31.18.35.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Oct 2019 18:35:05 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <73B7A5FF-BF33-45D6-A020-5FE783AC8144@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_24AA08A1-A8BA-4C03-BC4A-8A342367A158"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 31 Oct 2019 18:35:04 -0700
In-Reply-To: <20190830.170342.347117436400694093.mbj@tail-f.com>
Cc: Kent Watsen <kent+ietf@watsen.net>, netconf@ietf.org
To: Martin Bjorklund <mbj@tail-f.com>
References: <0100016ce21ab15a-16b3c8d4-0722-4ea7-a6c0-081689ae42f4-000000@email.amazonses.com> <20190830.142405.429358952690470664.mbj@tail-f.com> <0100016ce2c0c48e-c11076b5-b119-4509-b83e-4206d9699b72-000000@email.amazonses.com> <20190830.170342.347117436400694093.mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/lfMjUvLbRSpkCnT1xMgADq-lw5A>
Subject: Re: [netconf] SN and indirection
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: Fri, 01 Nov 2019 01:35:09 -0000

[Trimming down the thread to one issue]

Hi Martin,

> On Aug 30, 2019, at 8:03 AM, Martin Bjorklund <mbj@tail-f.com> wrote:
> 
>> My personal opinion is that the indirection introduced in https-notif
>> is likely to be desired by all notif transports for configured
>> subscriptions
> 
> I agree.
> 
>> but it's unclear to me if the leverage to be had by
>> consolidating the pattern into SN is significantly better than the
>> copy/pasting the pattern into each notif draft, especially when
>> considering that we're not likely to ever have more than a few such
>> notif drafts.
> 
> If we don't have a generic indirection, I would like the current
> https-notif solution better if it didn't put 'receivers' at the
> top-level, but instead augmented it into '/sn:subscribers', and
> renamed it to 'https-receivers'.  Further, the 'receiver-ref' should
> probably be called 'https-receiver-ref' or something.

What would be the motivation to rename the receiver-ref to be https-receiver-ref? The receiver-ref is being declared in the 'ietf-https-notif’ namespace, which indicates the type of receiver it is, and prevents any name conflict with other receivers being declared in other namespaces. 

Thanks.

Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email