Re: [Rtg-yang-coord] multicast protocol YANG model design team
Qin Wu <bill.wu@huawei.com> Tue, 31 March 2015 01:22 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 8665C1A871F
for <rtg-yang-coord@ietfa.amsl.com>; Mon, 30 Mar 2015 18:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level:
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45,
RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 KhAC78K1lLn2 for <rtg-yang-coord@ietfa.amsl.com>;
Mon, 30 Mar 2015 18:22:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id DBF641A00BE
for <rtg-yang-coord@ietf.org>; Mon, 30 Mar 2015 18:22:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com)
([172.18.7.190])
by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id BUH88086; Tue, 31 Mar 2015 01:22:30 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by
lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server
(TLS) id 14.3.158.1; Tue, 31 Mar 2015 02:22:29 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by
nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001;
Tue, 31 Mar 2015 09:22:26 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Stig Venaas <stig@venaas.com>, "Rtg-yang-coord@ietf.org"
<rtg-yang-coord@ietf.org>
Thread-Topic: [Rtg-yang-coord] multicast protocol YANG model design team
Thread-Index: AQHQaxonzt0h8ynLHEOT0lBgimoCy501ytQw
Date: Tue, 31 Mar 2015 01:22:26 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA84715CED@nkgeml501-mbs.china.huawei.com>
References: <551999BD.6050100@venaas.com>
In-Reply-To: <551999BD.6050100@venaas.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.136.138]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/VBXnEzyn9Sq7IY7Toh8KMSqX6oc>
Cc: "david.sinicrope@ericsson.com" <david.sinicrope@ericsson.com>
Subject: Re: [Rtg-yang-coord] multicast protocol YANG model design team
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG
models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 01:22:35 -0000
Hi, Stig: Thanks for update. Would you like to update the following wiki page: http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgYangCoordWGs# for tracking PIM WG YANG model status, drafts and Design team activity easily. Regards! Qin/David -----邮件原件----- 发件人: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] 代表 Stig Venaas 发送时间: 2015年3月31日 2:45 收件人: Rtg-yang-coord@ietf.org 主题: [Rtg-yang-coord] multicast protocol YANG model design team Hi The pim wg is forming a design team to work on YANG multicast models. The work will focus on models related to the pim protocols, but also IGMP/MLD. Please get in touch with me if you're interested in participating. The goal is to come up with models fairly quickly. We will probably be meeting virtually every 2 weeks. So far we have volunteers from quite a few vendors, but few operators. Apart from multicast, we may need input on overall design. I'm hoping that models for routing protocols can have a common design. Like protocol or VRF centric, whether to extend the interface model etc. Stig _______________________________________________ Rtg-yang-coord mailing list Rtg-yang-coord@ietf.org https://www.ietf.org/mailman/listinfo/rtg-yang-coord