[Netconf] Issue #3 Support for notifications
Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 26 June 2018 01:58 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 7276B130F47; Mon, 25 Jun 2018 18:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_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 Bawy9Bf82ITb; Mon, 25 Jun 2018 18:58:31 -0700 (PDT)
Received: from mail-pl0-x22c.google.com (mail-pl0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (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 ED64A130E7A; Mon, 25 Jun 2018 18:58:30 -0700 (PDT)
Received: by mail-pl0-x22c.google.com with SMTP id c41-v6so7701032plj.10; Mon, 25 Jun 2018 18:58:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:cc:to; bh=oTInJ0kpVGp0kaV2kHEBfINzchrccVoD+fbAM3LY+cY=; b=PZNPwXDomUS0pCcFNhgBE69G5XtJ5uzzI6nCp1j83Vn57bB/knnyMORw8g9tMZ05RC 9kDSvyTOamd/7woIo0CTAOifaGVr9PJtoMnPtok2DdXIByRInFpC8dXz3+kPPhsT1wqB gogsZQxO/h8Dug8SlSPqBfXjXUUCwUoiwe+TRVt04i9D3ORuNSsj8x9UqHVG4ePvNiWV GKIq5H9jjJeQi51YdEOzLCG5PfX1GhlTsueY2eU1lhneg4Qd7qQOadsGt2PZDY73lixM UrLkHgt0NE39TfZG0UXmQgIP8GkKexUXyp4l+zMcSHNWllLawBV6aiqGW1x5qPKI3Vcn Wmfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=oTInJ0kpVGp0kaV2kHEBfINzchrccVoD+fbAM3LY+cY=; b=SALnvvNZlwOVj1997D90oH3h3OXgcxHS3GcTKXnIFpgtj+pPaTr/viIVIUIO0i4Kcf OS+lTqsqyGlK1Q2QOG8l3t6tEyBu0XycXonHAmCfGtPPw8G4y5vqHXYki4R/qP+96sNs oZkHAKPLUuLbEQxEB/VYORXRBKE07U6y57oseiRDfrV3Qxo0H2bgrceSP6O4bTrB5yZB WCy+J0JPuC6TJH6ETtVfMEc0Eh5URVu2lvyps8BiFjJiXseOsnUOtWWmbEeeFuKHkeZn 1nUKAkjHYH5EBt0qPF8pgEiPHI7n5BczvVM3ri+WIjf+f1xJBqKhrWu1SBP06hcmnfVa oEUg==
X-Gm-Message-State: APt69E253iCzBU34EdTqpFdx15OJmblU3aOSSBPc17N2+G8apltaHzj2 BX+QwqVIuTcAQKiZcY4pGwgH5jpl
X-Google-Smtp-Source: ADUXVKLx6m2uJS9YfrlIGXcs6t0rtczOs2Z6CfIps/j4nC3USWxOP8CvNwL/HcNLJE4Ps1duQyD1aA==
X-Received: by 2002:a17:902:8d98:: with SMTP id v24-v6mr14741719plo.250.1529977855668; Mon, 25 Jun 2018 18:50:55 -0700 (PDT)
Received: from ?IPv6:2601:647:4700:1280:993e:3a03:566b:3567? ([2601:647:4700:1280:993e:3a03:566b:3567]) by smtp.gmail.com with ESMTPSA id o88-v6sm437383pfi.110.2018.06.25.18.50.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jun 2018 18:50:55 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D48A68DC-2888-4DA2-9941-A2C27C4A53E3"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Message-Id: <7B277658-344A-42A2-B63C-91B80A0A6150@gmail.com>
Date: Mon, 25 Jun 2018 18:50:53 -0700
Cc: draft-mahesh-netconf-binary-encoding@ietf.org
To: Netconf <netconf@ietf.org>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/JXnS9vQpmqaxqNQ74-ArvuHnvbM>
Subject: [Netconf] Issue #3 Support for notifications
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 26 Jun 2018 01:58:36 -0000
Since a question was raised in IETF 101, about support of binary encoding for notifications, have added an issue in GitHub at https://github.com/netconf-wg/binary-encoding/issues/3 <https://github.com/netconf-wg/binary-encoding/issues/3>, that reads: RFC 5277 defines notifications capability built on top of NETCONF. A notification is created by a request, where, once the subscription is created, it cannot be modified. Since binary encoding is currently suggesting a change in encoding format mid-stream (after the "hello" message), it is not foreseeable how encoding format could be changed for these subscriptions. This might be different in the case of draft-ietf-netconf-subscribed-notifications, where subscribed notifications carry a 'encoding' attribute that can be used to not only specify a specific form of encoding at creation time, but can also be modified using 'subscription-modified'. The identity 'encoding' would have to be extended to support other forms of encoding, including 'cbor+sid’. Comments/questions are welcome. Mahesh Jethanandani mjethanandani@gmail.com
- [Netconf] Issue #3 Support for notifications Mahesh Jethanandani