Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

ctets" is not clearly comprehensible. Thomas> Extended to "as series of n octets in IPFIX". Does that makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potential

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

ot be sufficient, please suggest how this could be better expressed. Med> Section 2: remark: "as series of n octets" is not clearly comprehensible. Thomas> Extended to "as series of n octets in IPFIX". Does that makes it clearer? Med> Section 4.11, remark:

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

re?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas From: OPSAWG mailto:opsawg-boun...@ietf.org>> On Behalf Of mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> Sent: Tuesday, September 6, 2022 10:19 AM To: Joe

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas *From:*OPSAWG *On Behalf Of *mohamed.boucad.

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

hat makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas From: OPSAWG mailto:opsawg-boun...@ietf.org>> On B

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

d (and updated) by non IPFIX people. Best wishes Thomas From: OPSAWG mailto:opsawg-boun...@ietf.org>> On Behalf Of mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> Sent: Tuesday, September 6, 2022 10:19 AM To: Joe Clarke (jclarke) mailto:jclarke=40cisco@dmarc.ietf.org>&

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

n IPFIX". Does that makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas *From:*OPSAWG *On Behalf Of *mohamed.boucad...@or

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

mas From: OPSAWG mailto:opsawg-boun...@ietf.org> > On Behalf Of mohamed.boucad...@orange.com <mailto:mohamed.boucad...@orange.com> Sent: Tuesday, September 6, 2022 10:19 AM To: Joe Clarke (jclarke) mailto:jclarke=40cisco@dmarc.ietf.org> >; opsawg@ietf.org <mailto:opsawg

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

g>> De la part de Joe Clarke (jclarke) Envoyé : jeudi 18 août 2022 22:14 À : opsawg@ietf.org<mailto:opsawg@ietf.org> Objet : [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We'd like to begin a two week call for adoption of this work. Even as an individual d

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Just got back from PTO, and I’m closing out this CfA a wee bit late. The WG discussion points to desire to adopt this work. Moreover, there were a few comments for the authors. That said, authors, please resubmit this version of the draft as draft-ietf-opsawg-ipfix-srv6-srh-00 replacing draft

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

-srv6-srh-05-rev%20Med.doc Cheers, Med De : OPSAWG De la part de Joe Clarke (jclarke) Envoyé : jeudi 18 août 2022 22:14 À : opsawg@ietf.org Objet : [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We'd like to begin a two week call for adoption of this work. Even

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hi Joe, Just in case it was not clear, I obviously support the adoption call (as a contributor) Regards, Benoit On 8/18/2022 10:14 PM, Joe Clarke (jclarke) wrote: Hello, WG. We’d like to begin a two week call for adoption of this work.  Even as an individual draft it has already received s

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

18, 2022 10:14 PM To: opsawg@ietf.org Subject: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We'd like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IET

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

I support adoption. -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com Mobile: +34 682 051 091 - On 18/8/22, 22:15, wrote: He

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hi I support the WG adoption of draft-tgraf-opsawg-ipfix-srv6-srh Thanks Ahmed From: OPSAWG On Behalf Of Joe Clarke (jclarke) Sent: Thursday, August 18, 2022 10:14 PM To: opsawg@ietf.org Subject: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We’d like to begin a

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

20:00 *收件人:*opsawg@ietf.org *主题:*Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi, I have read the draft and think it is useful in the area of network operations. Therefore I support its adoption. BR Paolo *From:*OPSAWG *On Behalf Of *Joe Clarke (jclarke

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

...@ietf.org] 代表 Paolo Volpato 发送时间: 2022年8月22日 20:00 收件人: opsawg@ietf.org 主题: Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi, I have read the draft and think it is useful in the area of network operations. Therefore I support its adoption. BR Paolo From: OPSAWG

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

@ietf.org> Subject: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We’d like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IETF 114 there does seem to be

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hi, I have read this draft and support the WG adoption. I think it is very valuable work and believe it improves network visibility in SRv6 networks. Regards, Alex > On 18 Aug 2022, at 22:14, Joe Clarke (jclarke) > wrote: > > Hello, WG. We’d like to begin a two week call for adoption of th

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

f Joe Clarke (jclarke) Sent: Thursday, August 18, 2022 10:14 PM To: opsawg@ietf.org Subject: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We’d like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews a

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hi, Having read the draft, i believe the work is valuable and support its WG adoption. Paolo On 18/8/22 17:14, Joe Clarke (jclarke) wrote: Hello, WG.  We’d like to begin a two week call for adoption of this work.  Even as an individual draft it has already received some reviews and has it

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hi I support WG adoption of the draft Thanks Regards … Zafar From: on behalf of Date: Thursday, August 18, 2022 at 4:14 PM To: Subject: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We’d like to begin a two week call for adoption of this work. Even as an

[OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Hello, WG. We’d like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IETF 114 there does seem to be interest in adopting this in opsawg, but we need a formal adoption poll. Please revi