Reviewer: Russ Housley
Review result: Not Ready
I reviewed this document as part of the Security Directorate's ongoing
effort to review all IETF documents being processed by the IESG. These
comments were written primarily for the benefit of the Security Area
Directors. Document authors, document
On Apr 25, 2024, at 1:02 AM, mohamed.boucad...@orange.com wrote:
>> -Message d'origine-
>> De : Guy Harris
>> Envoyé : jeudi 25 avril 2024 09:53
...
>> The changes I see from that link are:
>>
>> 1) an unreadable table becomes readable, which is presumably
>> what "fixing a bug
Thanks Med, for quick clarification! I am fine with your resolution!
Thanks and best regards
Dirk
On Thu, Apr 25, 2024 at 6:29 PM wrote:
> Hi Dirk,
>
> Thank you for the review.
>
> Please see inline.
>
> Cheers,
> Med
>
> > -Message d'origine-
> > De : Dirk Von Hugo via Datatracker
> >
Hi Dirk,
Thank you for the review.
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Dirk Von Hugo via Datatracker
> Envoyé : jeudi 25 avril 2024 17:05
> À : int-...@ietf.org
> Cc : draft-ietf-opsawg-ipfix-tcpo-v6eh@ietf.org; last-
> c...@ietf.org; opsawg@ietf.org
> Obj
Reviewer: Dirk Von Hugo
Review result: Ready
Dear authors, intarea community,
as assigned INT directorate reviewer for draft-ietf-opsawg-ipfix-tcpo-v6eh my
comments were written primarily for the benefit of the Internet Area Directors.
Document editors and shepherd(s) should treat these comments j
Hi Joe,
No, I'm not aware of any IPR that applies to these drafts.
Ivan Bykov
On Apr 19, 2024, at 09:32, Joe Clarke (jclarke)
wrote:
CAUTION : This email originated outside the company. Do not click on any links
or open attachments unless you are expecting them from the sender.
ATTENTION :
Thank you Loa for reviewing this document again! Much appreciated.
Please find some follow-ups inline below
On Sun, Apr 21, 2024 at 3:46 AM Loa Andersson wrote:
> Working Group, Carlos, and Adrian,
>
> The way I understood draft-pignataro-opsawg-oam-whaaat-question-mark, is
> that
> while it up
Hi all,
No, I'm not aware of any IPR that applies to these drafts
Regards
Richard Roberts
Juniper Business Use Only
From: OPSAWG On Behalf Of Joe Clarke (jclarke)
Sent: Friday, April 19, 2024 4:32 PM
To: opsawg@ietf.org
Subject: [OPSAWG] IPR POLL: Attachment circuits work
CAUTION : This emai
Hi Everyone
IANA has assigned the IE numbers for the fields captured in our draft (related
to the GTP header fields). Here below is the latest ‘-06’ version uploaded to
datatracker which is reflecting IANA assigned IPFIX IE# for GTP fields.
https://www.ietf.org/archive/id/draft-voyersriram-opsa
Dear, Authors et al.,
thank you for your continued work on the Alternate Marking method. In my
opinion, draft-gfz-opsawg-ipfix-alt-mark provides an essential IEs making
the use of IPFIX operationally viable option for the Alternate Marking
method. While I've read the document, it seems that its cur
Hi Guy,
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Guy Harris
> Envoyé : jeudi 25 avril 2024 09:53
> À : BOUCADAIR Mohamed INNOV/NET
> Cc : Michael Richardson ; opsawg@ietf.org
> Objet : Re: [OPSAWG] advancing PCAP drafts
>
>
> On Apr 25, 2024, at 12:04 AM, mohamed
On Apr 25, 2024, at 12:04 AM, mohamed.boucad...@orange.com wrote:
> Other than fixing a bug in Table 3.1, I thought that we were close to the
> WGLC.
>
> However, I checked
> https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-pcaplinktype&url_2=https://IETF-OPSAWG-WG.github.io/dra
Hi Michael,
Any update about this draft?
Other than fixing a bug in Table 3.1, I thought that we were close to the WGLC.
However, I checked
https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-pcaplinktype&url_2=https://IETF-OPSAWG-WG.github.io/draft-ietf-opsawg-pcap/draft-ietf-ops
13 matches
Mail list logo
