Re: [OPSAWG] Call for Presentation in Chicago

"lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com> Tue, 07 March 2017 03:20 UTC

Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3A2129AC2 for <opsawg@ietfa.amsl.com>; Mon, 6 Mar 2017 19:20:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level:
X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.741, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 nPAGin8Qs8m6 for <opsawg@ietfa.amsl.com>; Mon, 6 Mar 2017 19:20:14 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id BBA9C129ABF for <opsawg@ietf.org>; Mon, 6 Mar 2017 19:20:13 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app06-12006 (RichMail) with SMTP id 2ee658be26ea1ba-29836; Tue, 07 Mar 2017 11:20:12 +0800 (CST)
X-RM-TRANSID: 2ee658be26ea1ba-29836
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.69.29.83]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee458be26eab2c-c4eaf; Tue, 07 Mar 2017 11:20:11 +0800 (CST)
X-RM-TRANSID: 2ee458be26eab2c-c4eaf
Date: Tue, 07 Mar 2017 11:20:42 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: zhoutianran <zhoutianran@huawei.com>, opsawg <opsawg@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <2017030711203868116514@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart150081003432_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6NcaIx4PKvBbQh4IlUBYQXW0-0g>
Subject: Re: [OPSAWG] Call for Presentation in Chicago
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 07 Mar 2017 03:20:16 -0000

Dear WG Chairs,
A time slot for 5 minutes is requested to report the status of draft-ietf-opsawg-ipfix-bgp-community, which was recently adopted as a working group item. The abstract of this draft is shown below.

This draft specifies an extension to the IPFIX information model
   defined in [RFC7012] to export the BGP community [RFC1997]
   information.  Three information elements, bgpCommunity,
   bgpSourceCommunityList and bgpDestinationCommunityList, are
   introduced in this document to carry the BGP community information.
   bgpCommunity, containing exactly one BGP community value, is used to
   consist the list in bgpSourceCommunityList and
   bgpDestinationCommunityList, which are corresponding to a specific
   flow's source IP and destination IP respectively.

Best Regards,


lizhenqiang@chinamobile.com
--------------------------------------
Tianran Zhou <zhoutianran@huawei.com> Mon, 06 March 2017 05:54 UTCShow header 

Hi WG,
The OPSAWG meeting is scheduled on Thursday, Afternoon Session I 1300-1500, according to the final agenda.
Please send your request to the chairs for your presentation.
Best,
Tianran