Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02

"lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com> Tue, 14 February 2017 07:33 UTC

Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954E31294F7; Mon, 13 Feb 2017 23:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 JWvt9PMzL7yd; Mon, 13 Feb 2017 23:33:18 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7FB12947A; Mon, 13 Feb 2017 23:33:16 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.1]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec58a2b2b1257-8a6c5; Tue, 14 Feb 2017 15:33:05 +0800 (CST)
X-RM-TRANSID: 2eec58a2b2b1257-8a6c5
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.72.55.152]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee158a2b2afdeb-59c94; Tue, 14 Feb 2017 15:33:05 +0800 (CST)
X-RM-TRANSID: 2ee158a2b2afdeb-59c94
Date: Tue, 14 Feb 2017 15:34:38 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: "PJ Aitken" <pjaitken@brocade.com>, Zhoutianran <zhoutianran@huawei.com>, "ipfix@ietf.org" <IPFIX@ietf.org>, opsawg <opsawg@ietf.org>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>, <f2921126-418f-de35-cbec-be1605be4663@brocade.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <201702141534369518773@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart832001274031_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/5owlwMQI1Or7Gi02nNeJK0Iu1M8>
Cc: "draft-li-opsawg-ipfix-bgp-community.authors@ietf.org" <draft-li-opsawg-ipfix-bgp-community.authors@ietf.org>
Subject: Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 07:33:20 -0000

I support the adoption of this draft as a co-author. The requirement comes from the field network.

Best Regards


lizhenqiang@chinamobile.com
 
From: PJ Aitken
Date: 2017-02-13 20:39
To: Tianran Zhou; IPFIX@ietf.org
CC: draft-li-opsawg-ipfix-bgp-community.authors@ietf.org
Subject: Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
Per section 6 of RFC7012, new IPFIX Information Elements can be added by 
direct application to IANA; there's no need for a draft or RFC.
 
However, the introduction and examples may be valuable, especially for 
BGP experts who are less familiar with IPFIX.
 
I've no objection to adopting the draft.
 
P.
 
 
On 13/02/17 03:49, Tianran Zhou wrote:
> Dear IPFIX,
>
> Since the IPFIX WG is concluded, this IE extension draft is processed now in OPSAWG.
> Thanks very much for the previous comments and discussions on this draft in this mailing list.
> Now the OPSAWG is polling for adoption of this I-D. I sincerely appreciate your opinion and review.
>
> Best Regards,
> Tianran Zhou
>
> -----Original Message-----
> From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Tianran Zhou
> Sent: Monday, February 13, 2017 11:37 AM
> To: opsawg@ietf.org
> Cc: opsawg-chairs@ietf.org
> Subject: [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
>
> Dear OPSAWG,
>
> In Seoul, we got enough interest and positive response on this IPFIX IE extension draft.
> By the authors' request, this email starts a formal poll. The chairs would like to know if the WG participants agree that the following document should be adopted as a WG document in OPSAWG.
>
> Export BGP community information in IP Flow Information Export (IPFIX)
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dli-2Dopsawg-2Dipfix-2Dbgp-2Dcommunity-2D02&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=xYsTrrFuD2dlfxdp0X3pcPMw4vuozglfpGLv4A5TKNw&e=
>
> The adoption poll will take two weeks. Please let us know your opinion by Feb 27. It would also be good to hear who is willing to review and/or implement or deploy the extension described in the document.
>
> Since we already found that the majority of the f2f participants at our IETF97 session like this idea, please do speak up now if you do not agree or have serious objections (with explanation of course).
>
> Regards,
> Tianran
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_opsawg&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=lUyPAeQ2BUnIuqL4qUS1w45CNe3JixjYQzYQVN4Y3q4&e=
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipfix&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=lOUrCUQVhsdnIWvSTJycjdy-0V6yZZ9NvjU2N-wZn18&e=
 
_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www.ietf.org/mailman/listinfo/ipfix