Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread Michael Richardson
> OPSAWG on behalf of Henk Birkholz > writes: > Not Ready That wasn't the question Tom. This is not a WGLC. This is a WG adoption call. by replying, I think you have indicated that you are interested in the WG taking on this work? > The linktype I-D is defective with its

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread Michael Tuexen
> On 29. Dec 2022, at 17:45, tom petch wrote: > > From: Carsten Bormann > Sent: 29 December 2022 13:20 > > On 2022-12-29, at 12:55, tom petch wrote: >> >> The linktype I-D is defective with its documentary references so the >> website is going to be as well. The number of references for

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread tom petch
From: Carsten Bormann Sent: 29 December 2022 13:20 On 2022-12-29, at 12:55, tom petch wrote: > > The linktype I-D is defective with its documentary references so the > website is going to be as well. The number of references for links is > considerable in the I-D although none appear as

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread Carsten Bormann
On 2022-12-29, at 12:55, tom petch wrote: > > The linktype I-D is defective with its documentary references so the > website is going to be as well. The number of references for links is > considerable in the I-D although none appear as references of the I-D as > anyone familiar with the

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread tom petch
From: OPSAWG on behalf of Henk Birkholz Sent: 08 December 2022 20:34 Dear OPSAWG members, this starts a Working Group Adoption call for a bundle of two documents: > https://www.ietf.org/archive/id/draft-tuexen-opsawg-pcapng-05.html >

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread Michael Tuexen
> On 29. Dec 2022, at 12:18, Henk Birkholz > wrote: > > Hi Tom, > Hi Michael, > hi all, > > thanks for your help! > > As I am continuously challenged by reading my own calendar properly, replies > for this Working Group Call for Adoption may drizzle in until Monday (and > then some, as I am

Re: [OPSAWG]  WG Adoption Call for draft-tuexen-opsawg-pcapng-05 and draft-richardson-opsawg-pcaplinktype-01

2022-12-29 Thread Henk Birkholz
Hi Tom, Hi Michael, hi all, thanks for your help! As I am continuously challenged by reading my own calendar properly, replies for this Working Group Call for Adoption may drizzle in until Monday (and then some, as I am not sure how many folks will look at this on Jan 1st). In essence, we

Re: [OPSAWG] IPR Poll on draft-tgraf-opsawg-ipfix-on-path-telemetry

2022-12-29 Thread Benoit Claise
Dear OPSAWG, I am not aware of any IPR related to this draft. Regards, Benoit On 12/22/2022 3:55 AM, Tianran Zhou wrote: Hi Authors and Contributors, Accompany with the WG adoption on this draft, I'd like all authors and contributors to confirm on the list. Please respond if you are