Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)
Paolo Lucente <paolo@ntt.net> Mon, 05 December 2022 19:26 UTC
Return-Path: <paolo@ntt.net>
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 332CDC14F726 for <opsawg@ietfa.amsl.com>; Mon, 5 Dec 2022 11:26:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLu1_bx3g7h1 for <opsawg@ietfa.amsl.com>; Mon, 5 Dec 2022 11:26:22 -0800 (PST)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail4.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::192:26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF39AC14CE21 for <opsawg@ietf.org>; Mon, 5 Dec 2022 11:26:22 -0800 (PST)
Received: from [IPV6:2804:1b3:61c0:8b8a:d16e:ede3:1c60:8237] (unknown [IPv6:2804:1b3:61c0:8b8a:d16e:ede3:1c60:8237]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id 97BECEE0147; Mon, 5 Dec 2022 19:26:20 +0000 (UTC)
Message-ID: <db7e9411-41ea-2340-fe42-19ea84cb2eb7@ntt.net>
Date: Mon, 05 Dec 2022 16:26:18 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <BN9PR11MB537174D17B1613C8F98EC08AB8159@BN9PR11MB5371.namprd11.prod.outlook.com>
Content-Language: en-US
From: Paolo Lucente <paolo@ntt.net>
In-Reply-To: <BN9PR11MB537174D17B1613C8F98EC08AB8159@BN9PR11MB5371.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/0jbBUNV9NQa9U3vKJqv2PLn6nzg>
Subject: Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 05 Dec 2022 19:26:25 -0000
Hi, Speaking with my hat of software developer: I have implemented this in the free open-source flow collector pmacct (*) as part of the IETF 115 hackathon and found no issues. I hence support WGLC of the document. Paolo (*) https://github.com/pmacct/pmacct On 30/11/22 10:53, Joe Clarke (jclarke) wrote: > Hello, WG. As discussed at IETF 115, we want to conduct a WG LC for > draft-ietf-opsawg-ipfix-srv6-srh. The authors believe this work is > stable and moreover used the 115 hackathon to develop a interoperable > implementations (linked in Data Tracker) . Additionally, IANA has > already weighed in on this work and agree with the considerations approach. > > Therefore, we are calling for a two week LC. We will conclude on > December 14. > > https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/ > <https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/> > > Please review the current -04 draft, post your comments and/or your > thoughts on the current text. > > Thanks. > > Joe > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] 🔔 WG LC: Export of Segment Routing over … Joe Clarke (jclarke)
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… mohamed.boucadair
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Thomas.Graf
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Haoyu Song
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Giuseppe Fioccola
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Qin Wu
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Thomas.Graf
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Alex Huang Feng
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Benoit Claise
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Paolo Lucente
- Re: [OPSAWG] WG LC: Export of Segment Routing ove… Chongfeng Xie
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Alex Huang Feng
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Paolo Volpato
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Pablo Camarillo (pcamaril)
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Ahmed Abdelsalam (ahabdels)
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Diego R. Lopez
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Gyan Mishra
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Joe Clarke (jclarke)
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Benoit Claise
- Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing o… Rob Wilton (rwilton)