IETF Logo Mail Archive

Re: [netmod] 答复: pls clarify get operation

Kent Watsen <kent@watsen.net> Sat, 29 June 2019 12:03 UTC

Return-Path: <0100016ba31ec8b0-8a5a2b03-8d83-4bab-9084-5dcba3d2fda6-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4476120186; Sat, 29 Jun 2019 05:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 NmnjdfjNhD1e; Sat, 29 Jun 2019 05:03:54 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA6212009C; Sat, 29 Jun 2019 05:03:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1561809832; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=z6hpuqjiU4nwq5XrBzN+zH6dB31FUH9wMzqVOYDjqtE=; b=h5hZ3KszTr2xoTO14/441ZbXG62A/uga2/cUj4jMzWV0PHZDdZ8rh9cKTiu5SzCo IP4+ZJVjsjzIe5ToPoL5aTA3/H8tPHVgKbj2BEbXSJP3cfW+aPjF9r2wVYQkkA2N383 19TpbfElL07JdfxiE91MRIl/uw+5RjEqqz51qGcQ=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Kent Watsen <kent@watsen.net>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <0100016b9eb005f6-11af1cb0-f3ba-4ad6-9b49-88965e668f56-000000@email.amazonses.com>
Date: Sat, 29 Jun 2019 12:03:52 +0000
Cc: "netmod@ietf.org" <netmod@ietf.org>, "Zhangwei (SS)" <zhangwei70@huawei.com>, Yangang <yangang@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <0100016ba31ec8b0-8a5a2b03-8d83-4bab-9084-5dcba3d2fda6-000000@email.amazonses.com>
References: <5756FB984666AD4BB8E1D63E2E3AA3D001ED5E20@dggemm513-mbx.china.huawei.com> <BYAPR11MB2631D3A01E398ADDBB294588B5FC0@BYAPR11MB2631.namprd11.prod.outlook.com> <20190628085014.ljxh73fcmiu6iqx7@anna.jacobs.jacobs-university.de> <5756FB984666AD4BB8E1D63E2E3AA3D001ED6082@dggemm513-mbx.china.huawei.com> <BYAPR11MB2631B6688BB094D93BACAD6AB5FC0@BYAPR11MB2631.namprd11.prod.outlook.com> <5756FB984666AD4BB8E1D63E2E3AA3D001ED63C8@dggemm513-mbx.china.huawei.com> <0100016b9eb005f6-11af1cb0-f3ba-4ad6-9b49-88965e668f56-000000@email.amazonses.com>
To: "Fengchong (frank)" <frank.fengchong@huawei.com>
X-SES-Outgoing: 2019.06.29-54.240.8.96
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/QvvK2AGlGEqVmVAps4D87nAwUhQ>
Subject: Re: [netmod] 答复: pls clarify get operation
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jun 2019 12:03:56 -0000

An unsolicited follow up to my earlier message. 

I didn’t mean to single out any particular company, rather then trying to encourage all companies to make the bold business decision to embrace NMDA.  The statement was only intended to be one of encouragement. 

Another clarification, the server I’m working on is natively NMDA.  I have a placeholder for an adaptation layer to support non-NMDA clients, but won’t implement it unless requested.  I realize that only supporting NMDA is not officially sanctioned yet but, being a greenfield project without legacy clients, I’m hoping it will be okay from a go-to-market perspective. 

Kent // contributor

v2.28.0 | Report a Bug | By Email | System Status