[OPSAWG] EAP metadata. YANG to XML and JSON, but which to pick?
Rok Papež <rok.papez@arnes.si> Tue, 20 January 2015 12:34 UTC
Return-Path: <rok.papez@arnes.si>
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 7B3E11B2A32 for <opsawg@ietfa.amsl.com>; Tue, 20 Jan 2015 04:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 alNOCW-NKkKp for <opsawg@ietfa.amsl.com>; Tue, 20 Jan 2015 04:34:09 -0800 (PST)
Received: from postfix.arnes.si (kanin.arnes.si [193.2.1.87]) by ietfa.amsl.com (Postfix) with ESMTP id 346BD1B2A1A for <opsawg@ietf.org>; Tue, 20 Jan 2015 04:34:09 -0800 (PST)
Received: from avs5-arnes.arnes.si (avs5.arnes.si [193.2.1.126]) by postfix.arnes.si (Postfix) with ESMTP id 0389A148027 for <opsawg@ietf.org>; Tue, 20 Jan 2015 13:34:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=arnes.si; h= content-transfer-encoding:content-type:content-type:subject :subject:mime-version:user-agent:organization:from:from:date :date:message-id:received:received:received; s=primus; t= 1421757247; x=1424349248; bh=n6AyXvT0ruRL+7kJMLpJsEF8C/KXumNy79/ yeNO3RHY=; b=BN78yeLqgPLqrs2k3ioXi7EOXJMjxFYZzhMSWHyyAJu8T4bfO5h mbSZqRBECaow4up638S9LNcJ66A4CqwW5ZP0fdRvpZDnJtqBVh/h5TMnAfcqfbFe WNtSyjUtHXbQHxJLyujeONvxXBQK7qNcSWKobVJnJ5y7HV94n3jMkVA4=
X-Virus-Scanned: amavisd-new at arnes.si
Received: from postfix.arnes.si ([193.2.1.87]) by avs5-arnes.arnes.si (avs5.arnes.si [193.2.1.126]) (amavisd-new, port 10030) with ESMTP id NU8vdNDzflTA for <opsawg@ietf.org>; Tue, 20 Jan 2015 13:34:07 +0100 (CET)
Received: from skala.arnes.si (skala.arnes.si [193.2.1.54]) by postfix.arnes.si (Postfix) with ESMTP id DECE1148003 for <opsawg@ietf.org>; Tue, 20 Jan 2015 13:34:07 +0100 (CET)
Received: from [212.235.168.13] (rok.lemez.arnes.si [212.235.168.13]) by skala.arnes.si (Postfix) with ESMTP id D18F6A40ADA for <opsawg@ietf.org>; Tue, 20 Jan 2015 13:34:07 +0100 (CET)
Message-ID: <54BE4B3F.6050607@arnes.si>
Date: Tue, 20 Jan 2015 13:34:07 +0100
From: Rok Papež <rok.papez@arnes.si>
Organization: ARNES
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: opsawg@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/kFKSOZNmopC5df1PEJWNUYVf7Wk>
Subject: [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:34:11 -0000
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. -- regards, Rok Papež.
- [OPSAWG] EAP metadata. YANG to XML and JSON, but … Rok Papež
- Re: [OPSAWG] EAP metadata. YANG to XML and JSON, … Ladislav Lhotka