Routing Area Yang Architecture Design Team chartered

Alia Atlas <> Thu, 26 March 2015 16:37 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 940CC1A87B8 for <>; Thu, 26 Mar 2015 09:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EdDRuL1KPRnb for <>; Thu, 26 Mar 2015 09:37:23 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EE0741A894F for <>; Thu, 26 Mar 2015 09:37:00 -0700 (PDT)
Received: by obdfc2 with SMTP id fc2so50246476obd.3 for <>; Thu, 26 Mar 2015 09:37:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Dqpqx+OyJ+Upxcgd/OeElxWHUFjPJn6l7IU0oa1FhUE=; b=Qmw6LPMzoxxsIJYb01t1uLc+jy9TjS4Xq1jvSvOnM9r1ECVMqNZJz0o6HublHcf/Ed NXnI+qUElVfMeU6RW2Sgyi8ZxCkq19u+W7nMxoiXpiT8DRwbu7Ve/cqSExhwoTskJkD/ zLIWwO5UInijiMyBzF0wx9zEUnVPfOPsm13RjN+Cd4rzKRMtrnD4x7isdZ+pMVcYGTG+ DhZhSnWWEUKgZo9bgZF39bPm4+v2V2xLDXUE442yiw8XZA25JjnJaUmjEWTFnauL5x+X 7+g8ai8a8xhyubBIWmfgHutl87TPtFkafXXlXUaILyz6QsK0Oe6/9ipXcmHfyCzJz1mM mLKg==
MIME-Version: 1.0
X-Received: by with SMTP id ws9mr12906575oeb.24.1427387820471; Thu, 26 Mar 2015 09:37:00 -0700 (PDT)
Received: by with HTTP; Thu, 26 Mar 2015 09:37:00 -0700 (PDT)
Date: Thu, 26 Mar 2015 12:37:00 -0400
Message-ID: <>
Subject: Routing Area Yang Architecture Design Team chartered
From: Alia Atlas <>
To: "" <>
Content-Type: multipart/alternative; boundary=047d7bd6b7fefefdb40512339f58
Archived-At: <>
Cc: "Deborah Brungard \(\)" <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Mar 2015 16:37:25 -0000

I have chartered a Routing Area Yang Architecture design team as described
The design team has a private mailing list and can be reached at  There is also a wiki page at where the
design team will have interactive work.

Routing Area Yang Architecture Design Team Charter

With the increase of YANG models, it is desirable to have an
architecture that can suggest and articulate common functionality to be
used by multiple models and how the models interconnect.  Some
individual work has been done in this space and the design team is
encouraged to consider such input.  Although this is a concern across
the entire scope of YANG models, this design team is focused on the
question of providing an architecture for the protocols and
functionality contained inside the Routing Area.  This may identify
additional desirable models and common functionality; those suggestions
can be raised in Netmod.

Common conventions and use of YANG functionality in similar ways can
help make the interactions of models easier to understand.  RFC 6087
provides some guidance; an update is underway now in
draft-ietf-netmod-rfc6087bis.  If the design team has recommendations
for how the models should be written, those which are not
routing-specific can be written down and discussed in netmod as part of
a planned update of RFC 6087.

It is also important to consider how future extensibility and features
in Routing Area work will need to be captured in YANG models.  While
the IETF is busy developing YANG models, we are still working on new
routing area features and technology.  The design team should publish
and maintain best current practices for how new features can easily
augment existing YANG models so that authors of those new features and
technologies can understand how to consider YANG modeling in their
manageability considerations.

This design team will write one or more internet-drafts describing the
proposed architecture of the models, the recommended common
conventions, and considerations for how to model new features.  The
architecture is the highest priority.  The design team will address
all the aspects of the routing area modeling: from configuration, to
operational state, notifications, and RPCs.  This design team will
regularly coordinate with the YANG doctors for review and advice.
These drafts will be discussed in RTGWG.  It is possible that some of
the content, such as the details of the architecture, will go to a
wiki to be updated while other content, such as advice for extensions
and common conventions, would be published by IETF consensus.

Design team members
    Acee Lindem <>
    Anees Shaikh <>
    Christian Hopps <>
    Dean Bogdanovic <>
    Lou Berger <>
    Qin Wu <>
    Rob Shakir <>
    Stephane Litkowski <>
    Yan Gang <>