[PWE3] Fwd: New Non-WG Mailing List: Rtg-yang-coord

"Andrew G. Malis" <agmalis@gmail.com> Tue, 07 October 2014 15:39 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D24421A6F9C for <pwe3@ietfa.amsl.com>; Tue, 7 Oct 2014 08:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.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] 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 ggeu7Qv4hiig for <pwe3@ietfa.amsl.com>; Tue, 7 Oct 2014 08:39:53 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD44A1A6FAA for <pwe3@ietf.org>; Tue, 7 Oct 2014 08:39:52 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id d1so8359506wiv.6 for <pwe3@ietf.org>; Tue, 07 Oct 2014 08:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=YE0TC5HFQnToBJC2NUmXJVH+yQcfsDgkNQCBhphZJCQ=; b=JI6+OFKU0kHPVgvxLsDCJJl+aWgD3ApcZLvfy1ZSj2GEhD2xcY/Sk0tjkjy1pH3sbb BLvR5UTE683VDh0wFqX6oYnqoUCCWiZGRzRgA9EsRQtRiSRmz93KhrLGvlo8DKe/TDtB nLd5wrIdyIuItOLpa4WnDcy4ikhBHPRuUt/CCZc2Wg7Lb9dNnjoYCw7arkiYXUlv6CR0 aUyUb5hDPIDeM9ilu0YSQI3VuJL3U3dTJkq8yKbVu3QJyZNx4bpzV4ZDt0aTDdOzJyy/ +7fAsJXs49gfMYPL7iO/TQ9v8heFcwdwF6byQVWoAehLwNrxC6E1cTJfSL4HKmjnNza8 9cyA==
X-Received: by 10.180.36.98 with SMTP id p2mr9198786wij.3.1412696391357; Tue, 07 Oct 2014 08:39:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.208.12 with HTTP; Tue, 7 Oct 2014 08:39:31 -0700 (PDT)
In-Reply-To: <20141006223256.19159.32181.idtracker@ietfa.amsl.com>
References: <20141006223256.19159.32181.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 7 Oct 2014 11:39:31 -0400
Message-ID: <CAA=duU14VptCca9+=ZUJqOoSU_y13pzvnt=gygaKVk6Q-m=0mA@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f50291a951bf80504d70260
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/PvgCKAr7UwBQjDBENZwSOlOHhvM
Subject: [PWE3] Fwd: New Non-WG Mailing List: Rtg-yang-coord
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Oct 2014 15:39:55 -0000

PWE3ers,

FYI.

Cheers,
Andy

---------- Forwarded message ----------
From: IETF Secretariat <ietf-secretariat@ietf.org>;
Date: Mon, Oct 6, 2014 at 6:32 PM
Subject: New Non-WG Mailing List: Rtg-yang-coord
To: IETF Announcement List <ietf-announce@ietf.org>;
Cc: jhaas@juniper.net, jeff.tantsura@ericsson.com, rtg-yang-coord@ietf.org


A new IETF non-working group email list has been created.

List address: rtg-yang-coord@ietf.org
Archive: http://www.ietf.org/mail-archive/web/rtg-yang-coord/
To subscribe: https://www.ietf.org/mailman/listinfo/rtg-yang-coord

Purpose:

The rtg-yang-coord mailing list will provide a forum for coordination of
the development of YANG models being worked on for Routing, in order to
provide a consistent view to the NMS. The intended participants are people
active in Routing working groups and interested in the associated YANG
models, and YANG experts assisting with Routing YANG models. While this
list will help with the synchronization, WGs with responsibility for core
routing protocols are expected to also be responsible for the development
of YANG models for those
protocols.


For additional information, please contact the list administrators.