[Netconf] Do we need <activate> to indicate start of alternate form of encoding? #1 (Was: Re: NETCONF Encoding)
Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 20 March 2018 17:14 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 A28DB12D881; Tue, 20 Mar 2018 10:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 GI1vHLNwLA0O; Tue, 20 Mar 2018 10:14:44 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 A029312D77C; Tue, 20 Mar 2018 10:14:00 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id h76so4925617wme.4; Tue, 20 Mar 2018 10:14:00 -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=aVVyVFZNP5HHjj4TuTYwJEMDw8H671U6VloP6d+tUK4=; b=F8+HyR/AqQ4Abpwj7SdtY8lTakyFNyDsG1rCY/2FvUGOcqb99K9xQ8slR/xJm3Vr7b vfqOtQvwhLONRSSCqSYAGweIOiRo3nSZcndcKANF4oVuFuM/hWptmTN/tmyJGqSsuaOt a677CPmEnREnM8PtX7fe+CbMtrqpV/4GPqyZHDoPlF5gr3t7TY4IlAQ4ERrKSW7C+Yxz c6ckEFMDm1/wxzu/SWtn8yeF53CAMNnEuc8QcaSFuSbOTKHIB7CPHcHDHnjfMo3C6cyD YF7+NoKQPEdhzjglTddDHpYB0bLil4jfKBtUCdw+qpgP4b3qs8R7PGLeBJvUm686UWmK RI9w==
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=aVVyVFZNP5HHjj4TuTYwJEMDw8H671U6VloP6d+tUK4=; b=MPhqVsXwmXnqso/uOqfa8ifu1bvPZ5eNKo4ZqnPnFaxYsQfBnN6Yg4wh8F0ifqKqhG aiTuK1R01miu/qZjTaUt3foZoI/NkC2xpJbp2QFCZDyLp8wpyLd/rX2EMtWlrV9EfE0V WhFPG/qc+qsTzfPJr+MYQD4L1UX0AHxyi7xqdoIT1ff1QlEfmGe/7fR7hSU5zQw6TISn yZ275gyEoAD9IwLlXorU5nBokrpm60KcqDvKFtl0Rp9RhkxRnMwsHz/PczaKJj1HYTMV 6z44GyNrp7v2kXy7xX5seJxRDPYJjGkf58Gi/cW2ruQAvNbQEBxoePren06jGB5fuwn0 zaAA==
X-Gm-Message-State: AElRT7Em/ujqMMsqTDRTcWiDhOVt8U5Ny0pJ5+dx/YnpSubpUzX3DOk6 P3aK/gz2++kFRloXP9amIflHkl2kxWM=
X-Google-Smtp-Source: AG47ELt0uG/pH8OzgrKABiJ+huIZoYS6C6tN79DmQZeOM2tmmh5MmaoX0lnVfv9cXxbsNmCVbztJww==
X-Received: by 10.28.105.78 with SMTP id e75mr313226wmc.7.1521566039099; Tue, 20 Mar 2018 10:13:59 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:3579:1dcf:8a1:a8e? ([2001:67c:370:128:3579:1dcf:8a1:a8e]) by smtp.gmail.com with ESMTPSA id v22sm2093232wrd.43.2018.03.20.10.13.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 10:13:58 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <1F6DA912-AB1B-49FA-BAA4-DDBED0416243@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_766FFC64-D916-45B1-98B1-C83562B2ACE7"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 20 Mar 2018 17:14:51 +0000
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AD92FD6@nkgeml513-mbs.china.huawei.com>
Cc: Netconf <netconf@ietf.org>, draft-mahesh-netconf-binary-encoding@ietf.org
To: Qin Wu <bill.wu@huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA9AD92FD6@nkgeml513-mbs.china.huawei.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/SSq29JkyslQbu2pKed-6IDd96XU>
Subject: [Netconf] Do we need <activate> to indicate start of alternate form of encoding? #1 (Was: Re: NETCONF Encoding)
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: Tue, 20 Mar 2018 17:14:54 -0000
Qin, I would like to use this thread that you have started to track this as an issue, and thus the change in subject line. Here is the text of the issue documented here - https://github.com/netconf-wg/binary-encoding/issues/1 <https://github.com/netconf-wg/binary-encoding/issues/1> The -00 version of the draft proposed an explicit operation to indicate when the alternate form of encoding has been initiated. An alternate suggestion (from Martin and previously by Andy) is for the server to advertise the list of encodings it supports, in no particular order, and for the client to advertise its encoding in the order it prefers as part of capabilities. Thereafter, the client picks the first common encoding from the list, and sends the message in the that form of encoding. Unless, there are any objections, we will go ahead and accept the alternate suggestion, and update the draft to reflect it. Cheers. > On Mar 20, 2018, at 3:11 PM, Qin Wu <bill.wu@huawei.com> wrote: > > Hi, Mahesh: > Good to see you drop activate, We have similar idea and share you drafted proposal. We can talk when convenient. > > -Qin > <Netconf encoding.docx> Mahesh Jethanandani mjethanandani@gmail.com
- [Netconf] Do we need <activate> to indicate start… Mahesh Jethanandani