Re: [netconf] WGLC: draft-ietf-netconf-https-notif-06

Kent Watsen <kent+ietf@watsen.net> Wed, 03 February 2021 11:14 UTC

Return-Path: <01000177679a1bd4-8b1dd0c5-325a-400e-bda3-ae6e594c7fca-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 63EF33A09B7 for <netconf@ietfa.amsl.com>; Wed, 3 Feb 2021 03:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 VwUXoPqPa4gy for <netconf@ietfa.amsl.com>; Wed, 3 Feb 2021 03:14:50 -0800 (PST)
Received: from a48-90.smtp-out.amazonses.com (a48-90.smtp-out.amazonses.com [54.240.48.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5212E3A09B5 for <netconf@ietf.org>; Wed, 3 Feb 2021 03:14:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1612350889; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=oJIhtJh7lXRsXMJ8XEszDeNYgfVNqAOl0Vj/2gPow3Q=; b=jFn5jthtgSo9CFtAwUM7kLCVxnO60diRnXHF8zwdagdO24AdcapbjGTBjlQYynLw MW01TXDlDyG5MfHd9M9+IrngjxnKQvpfwB3q1aZ+VFHm/ZvHXli9H95hXIKtF0wvniL m7XRCmvWK7blBdIfJ/xzISAIONsbWzbKquRQ/350=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Wed, 3 Feb 2021 11:14:49 +0000
References: <3F58C70C-C0AD-4FBA-9E89-650CC347FEF6.ref@yahoo.com> <3F58C70C-C0AD-4FBA-9E89-650CC347FEF6@yahoo.com> <01000177588220b4-e69a027b-360a-4e2b-af1c-e681d9bd881e-000000@email.amazonses.com> <A979E7E5-1F85-4D6D-8560-1321589800B9@yahoo.com> <0100017764e15a93-b0ee5a7e-cf50-436c-be80-9cc488e5f7e4-000000@email.amazonses.com>
To: "netconf@ietf.org" <netconf@ietf.org>
In-Reply-To: <0100017764e15a93-b0ee5a7e-cf50-436c-be80-9cc488e5f7e4-000000@email.amazonses.com>
Message-ID: <01000177679a1bd4-8b1dd0c5-325a-400e-bda3-ae6e594c7fca-000000@email.amazonses.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2021.02.03-54.240.48.90
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/yftTKCyZrMUBbfPDrSR0OgeonZs>
Subject: Re: [netconf] WGLC: draft-ietf-netconf-https-notif-06
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: Wed, 03 Feb 2021 11:14:51 -0000

Should we abandon legacy RFC 5277 protocol?

Specifically, change the API to something that can be modeled by YANG?   This is desirable to receivers that are themselves an NC/RC "server”.  For instance:

  rpc relay-notification {
    input {
      anydata notification;
    }
  }


OLD:

  POST /some/path/relay-notification HTTP/1.1
  Host: example.com
  Content-Type: application/xml

  <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
    ...
  </notification>


NEW:  (diffs: URL, Content-Type, <input>, and xmlns)

  /restconf/operations/ietf-notif-receiver-https:relay-notification HTTP/1.1
  Host: example.com
  Content-Type: application/yang+data+xml

  <input xmlns="urn:ietf:params:xml:ns:notification-receiver:1.0">
    <notification>
      ...
    </notification>
  </input>


Not shown, but it also normalizes the JSON-encoding to have a YANG-modeled prefix (not a pseudo prefix, e.g., “ietf-restconf:”)


Thoughts?

K.