[OPSAWG] EAP authentication in YANG
Ladislav Lhotka <lhotka@nic.cz> Wed, 05 March 2014 09:01 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 0819A1A0255 for <opsawg@ietfa.amsl.com>; Wed, 5 Mar 2014 01:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level:
X-Spam-Status: No, score=-1.198 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, RP_MATCHES_RCVD=-0.547] 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 gx4VjJpF7fKd for <opsawg@ietfa.amsl.com>; Wed, 5 Mar 2014 01:01:28 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC6F1A0283 for <opsawg@ietf.org>; Wed, 5 Mar 2014 01:01:28 -0800 (PST)
Received: from dhcp-a653.meeting.ietf.org (dhcp-a653.meeting.ietf.org [31.133.166.83]) by mail.nic.cz (Postfix) with ESMTPSA id 1BE7F13F7D8 for <opsawg@ietf.org>; Wed, 5 Mar 2014 10:01:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1394010084; bh=qfDkiNNsyaiwTz2Ii+D5wWsyNns6U8AQsP0k5fim8P4=; h=From:Content-Type:Content-Transfer-Encoding:Subject:Message-Id: Date:To:Mime-Version; b=aimIjdMOJGeapO3UXGx9FgH1TeSdeqbolj9dis6C8QZ8RKCWj49AlGqfQ7Ohi9Zba OOkP9ofDFRQbM+Yx8cKYHRUW17Hjzg94OKYBlM+aFqjUUhg/0erydGr09wI+tNODDt gmOtAkMK7Y95KcG7YxgFlQEu44hQFzf3FdMfmITo=
From: Ladislav Lhotka <lhotka@nic.cz>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D92BBC1-B64E-4982-AD9B-8B8181851390@nic.cz>
Date: Wed, 05 Mar 2014 09:01:23 +0000
To: opsawg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
X-Virus-Scanned: clamav-milter 0.97.8 at mail
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/opsawg/y1JWsCyyd8RVzrGxDHjYeknt0k4
Subject: [OPSAWG] EAP authentication in YANG
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: Wed, 05 Mar 2014 09:01:30 -0000
Hi, FWIW, here is the data model for EAP auth configuration in YANG: https://gitlab.labs.nic.cz/labs/yang-tools/blob/master/data-models/eap-metadata/ietf-eap-metadata.yang I wrote it based on the XML Schema from draft-winter-opsawg-eap-metadata-00. The second YANG module, acme-eap.yang, is an example of how the basic model can be augmented with vendor specific extensions: https://gitlab.labs.nic.cz/labs/yang-tools/blob/master/data-models/eap-metadata/acme-eap.yang Note that, in contrast to the XML schema, the original data model needn’t take any provisions in order to make vendor extensions possible. Lada -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C
- [OPSAWG] EAP authentication in YANG Ladislav Lhotka