IETF Logo Mail Archive

Re: [netmod] Stephen Farrell's No Objection on draft-ietf-netmod-yang-json-09: (with COMMENT)

Eliot Lear <lear@cisco.com> Mon, 21 March 2016 15:53 UTC

Return-Path: <lear@cisco.com>
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 0FB3912D8EE; Mon, 21 Mar 2016 08:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 cHJ6qvc8GMsl; Mon, 21 Mar 2016 08:53:50 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3279612D8D2; Mon, 21 Mar 2016 08:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2434; q=dns/txt; s=iport; t=1458575629; x=1459785229; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=ajzwX7G7zj6Z1vSgwAtXhw3LawaXqnfkVh4bfGWBzSg=; b=m3GoCZ7CPR12IuLFdkRcBlUxdpqHMOXG5IHIzLc3ivWJ+QcF2ZcSw3ii EQEc6EABlzEMQdTEJjYLNDW6bcrm8GSu2xPzdYp0NiNJDQUku13yv99PV qx/0uCTPDwwj+ws+4qg9IOROE6QODETw6OwAmkxqW4+dKIBZbdHbNYVel A=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B7AgB1GPBW/xbLJq1evQ+CDw6BcIYNAoFfFAEBAQEBAQFkJ4RCAQEDASNVEQshFgsCAgkDAgECAUUGAQwIAQGIGwiwAo8iAQEBAQEBAQMBAQEBAQEBEQiKYoc8glYBBJdXgx6BZokAiTOFVI8GHgFDgjCBNjuKQwEBAQ
X-IronPort-AV: E=Sophos;i="5.24,372,1454976000"; d="asc'?scan'208";a="676193213"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2016 15:53:47 +0000
Received: from [10.61.216.70] ([10.61.216.70]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u2LFrlHa025532; Mon, 21 Mar 2016 15:53:47 GMT
To: Ladislav Lhotka <lhotka@nic.cz>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>, draft-ietf-netmod-yang-json@ietf.org, netmod-chairs@ietf.org, kwatsen@juniper.net, netmod@ietf.org
References: <20160317113347.3650.38937.idtracker@ietfa.amsl.com> <m2d1qnj2ec.fsf@birdie.labs.nic.cz> <20160321151914.GA62880@elstar.local> <56F0137B.3090103@cisco.com> <20160321154322.GA62960@elstar.local>
From: Eliot Lear <lear@cisco.com>
Message-ID: <56F0190A.6000103@cisco.com>
Date: Mon, 21 Mar 2016 16:53:46 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160321154322.GA62960@elstar.local>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="1dPGsmuggh1RF2V2x1TRab0C6J2WoJPsH"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/cgrhlisyrPX7p-dgoclPeZgnbIU>
Subject: Re: [netmod] Stephen Farrell's No Objection on draft-ietf-netmod-yang-json-09: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 21 Mar 2016 15:53:54 -0000

Hi Juergen,

I think there is a miscommunication:

On 3/21/16 4:43 PM, Juergen Schoenwaelder wrote:

>> However this goes, it should be well documented somewhere.  This will
>> not be the first time this comes up (he says, knowingly).
>>
> I am somewhat surprised. Do people really expect that signatures
> computed over a certain encoding of some data can be applied to a
> different encoding of the same data?

Not at all what I meant  (sorry if I was confusing).  I just meant that
we should be explicit as to what architectural component is responsible
for object signature and verification.  And it would be nice if there
were a few examples somewhere.

Eliot

v2.23.0 | Report a Bug | By Email