IETF Logo Mail Archive

Re: [OPSAWG] Mirja Kühlewind's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 06 December 2018 07:43 UTC

Return-Path: <jie.dong@huawei.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 89B01131109; Wed, 5 Dec 2018 23:43:21 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 1XICg-rSlL18; Wed, 5 Dec 2018 23:43:16 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7445131111; Wed, 5 Dec 2018 23:43:13 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 982CAE5059583; Thu, 6 Dec 2018 07:43:08 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 6 Dec 2018 07:43:09 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Thu, 6 Dec 2018 15:43:02 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-opsawg-ipfix-bgp-community@ietf.org" <draft-ietf-opsawg-ipfix-bgp-community@ietf.org>, Tianran Zhou <zhoutianran@huawei.com>, "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, Tianran Zhou <zhoutianran@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Mirja Kühlewind's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)
Thread-Index: AQHUiMeHILwVwMiNXEO0NE4RYOwbqaVv2DjA
Date: Thu, 06 Dec 2018 07:43:01 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927C2EC547E@NKGEML515-MBX.china.huawei.com>
References: <154359435795.27526.8666145722848127355.idtracker@ietfa.amsl.com>
In-Reply-To: <154359435795.27526.8666145722848127355.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Rh0Hl0YaTz5v-XLcvW3-q_QTuzI>
Subject: Re: [OPSAWG] Mirja Kühlewind's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Dec 2018 07:43:22 -0000

Hi Mirja, 

Thanks a lot for your review and comments. 

How about we replace that sentence with something like:

"For example, the collected information could be used for traffic monitoring, and could optionally be used for traffic optimization according to operator's policy."

Best regards,
Jie

> -----Original Message-----
> From: Mirja Kühlewind [mailto:ietf@kuehlewind.net]
> Sent: Saturday, December 01, 2018 12:13 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-opsawg-ipfix-bgp-community@ietf.org; Tianran Zhou
> <zhoutianran@huawei.com>; opsawg-chairs@ietf.org; Tianran Zhou
> <zhoutianran@huawei.com>; opsawg@ietf.org
> Subject: Mirja Kühlewind's No Objection on
> draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)
> 
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-opsawg-ipfix-bgp-community-11: No Objection
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> One comment on section 1:
> "For example, they can shift some flows
>   from congested links to low utilized links through an SDN controller
>    or PCE [RFC4655]."
> I'm not aware that ipfix information is commonly used for dynamic traffic
> adaptation and I'm not sure that is recommendable. Can you maybe choose a
> different example. E.g use of IPFIX for troubleshooting or more generally
> network monitoring? Thanks!
>

v2.23.0 | Report a Bug | By Email