IETF Logo Mail Archive

Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02

PJ Aitken <pjaitken@brocade.com> Thu, 16 February 2017 12:28 UTC

Return-Path: <paitken@Brocade.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 5730D129AB8; Thu, 16 Feb 2017 04:28:00 -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, SPF_PASS=-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 6kg5l86nGZXT; Thu, 16 Feb 2017 04:27:59 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::1]) (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 035481294E6; Thu, 16 Feb 2017 04:27:58 -0800 (PST)
Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1GCHcd9002277; Thu, 16 Feb 2017 04:17:38 -0800
Received: from brmwp-exmb12.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 28m20cg1nj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 04:17:38 -0800
Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXMB12.corp.brocade.com (172.16.59.130) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 05:17:35 -0700
Received: from [172.27.212.154] (172.27.212.154) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 13:17:30 +0100
To: 李振强 <13911635816@139.com>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, grow-bounces <grow-bounces@ietf.org>, zhoutianran <zhoutianran@huawei.com>
References: <2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone>
From: PJ Aitken <pjaitken@brocade.com>
Message-ID: <286d611d-32ae-7401-9790-a58f95301410@brocade.com>
Date: Thu, 16 Feb 2017 12:17:25 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone>
Content-Type: multipart/alternative; boundary="------------4FFBB7D44CD467F5C1E090E3"
X-Originating-IP: [172.27.212.154]
X-ClientProxiedBy: hq1wp-excas11.corp.brocade.com (10.70.36.102) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160119
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/maTYTz3soDf2lB7mgpyXCP82Nqs>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-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: Thu, 16 Feb 2017 12:28:00 -0000

If the list would be longer than can be accommodated in a single IPFIX 
message, then some mechanism would need to be defined to allow the list 
to be exported.

Ideally this should be a generic mechanism allowing the export of any 
large IPFIX content. However, it might be simpler to define a mechanism 
that's specific to the export of long lists.

There may be several solutions. eg, it might be a compression mechanism 
allowing the content to fit into a single message. Or the content might 
be carried across multiple messages.

If you feel it's an issue - especially if it would block your current 
work - then please start the discussion in the OPSAWG because the IPFIX 
WG is closed.

Thanks,
P.

On 16/02/17 12:02, 李振强 wrote:
> The length of IPFIX message is sufficient for BGP standard 
> communities, since the length of standard community is 4 octets. But 
> the sizes of extended community, large community and wide community 
> are bigger than the size of standard community. If the working group 
> agrees to cover the above all kinds of communities in this draft, do 
> you think we should open the discussion for IPFIX and basicList 
> message splitting?

v2.23.0 | Report a Bug | By Email