IETF Logo Mail Archive

Re: [OPSAWG] EAP metadata. YANG to XML and JSON, but which to pick?

Ladislav Lhotka <lhotka@nic.cz> Tue, 20 January 2015 12:55 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 383F81B2DA4 for <opsawg@ietfa.amsl.com>; Tue, 20 Jan 2015 04:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level:
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 9f6HYL0-oeay for <opsawg@ietfa.amsl.com>; Tue, 20 Jan 2015 04:55:26 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B581B2A37 for <opsawg@ietf.org>; Tue, 20 Jan 2015 04:55:26 -0800 (PST)
Received: from [195.113.220.110] (unknown [195.113.220.110]) by mail.nic.cz (Postfix) with ESMTPSA id 75CA613F744; Tue, 20 Jan 2015 13:55:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1421758524; bh=sKckQLQn3pbWclmHXcvnabmrAzV2q9na8l9LP8SwoRE=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=gmSFt6/um8GdJMV1vbmxTmrx9vyrVEVhFQztkmN14fCRLCMfudEFjhJQbkwGv35PN ODHv/972W888YzURHMxjz2UUSNAH+Db3kpl4CQt3azRRdq9PSLU//fpdSqwGZOn5fM upmKWjWWH5yuzOWLftQTGP9nYH2rggBFzBnTi74E=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <54BE4B3F.6050607@arnes.si>
Date: Tue, 20 Jan 2015 13:55:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9020AFCA-9EC1-4F69-BAA4-10B71FF7EED7@nic.cz>
References: <54BE4B3F.6050607@arnes.si>
To: Rok Papež <rok.papez@arnes.si>
X-Mailer: Apple Mail (2.1993)
X-Virus-Scanned: clamav-milter 0.98.1 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/WQbFibXz7pxHqxXR05mXlEoiBBY>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] EAP metadata. YANG to XML and JSON, but which to pick?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 12:55:28 -0000

Hi Rok,

> On 20 Jan 2015, at 13:34, Rok Papež <rok.papez@arnes.si> wrote:
> 
> Hello!
> 
> Arnes (http://www.arnes.si) is developing a Windows EAP plugin wireless
> supplicant for 802.1x and we are very interested in standardised EAP
> metadata:
> https://tools.ietf.org/html/draft-winter-opsawg-eap-metadata-01
> 
> The draft-specification definitions are in YANG and we can derive both
> XML and JSON format files. Which end format is it better to use: XML or
> JSON?
> 
> Supporting (consuming) both would be a duplicate effort we are not going
> to implement. My personal preference is always JSON over XML.

Tough luck, if you want to use RESTCONF: “A [RESTCONF] server MUST support XML encoding and MAY support JSON encoding." (draft-ietf-netconf-restconf-03). See also this juicy thread in the NETCONF mailing list:

http://www.ietf.org/mail-archive/web/netconf/current/msg09218.html

If you don’t plan to use RESTCONF, then choose whichever encoding suits you better.

Lada

> 
> -- 
> regards,
> Rok Papež.
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

v2.23.0 | Report a Bug | By Email