Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02

2024-01-31 Thread Qin Wu
-邮件原件- 发件人: Evans, John [mailto:jevanamz=40amazon.co...@dmarc.ietf.org] 发送时间: 2024年1月31日 20:25 收件人: Qin Wu ; Evans, John ; Henk Birkholz ; OPSAWG 主题: Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02 Hi Qin, > [Qin Wu] Maybe a new section can be added to clarify

Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02

2024-01-31 Thread Qin Wu
Hi, I have read the latest version of this draft and have the following comments: 1. what is the difference between packet loss and packet discard, it seems this two terms are used interchangeably in the draft, in some places packet discard reporting is used, while in some other places, packet

Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02

2024-01-31 Thread Evans, John
Hi Qin, Thank you for your feedback. > 1. what is the difference between packet loss and packet discard, it seems > this two terms are used interchangeably in the draft, in some places > packet discard reporting is used, while in some other places, packet loss > reporting, which I think lack

Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02

2024-01-31 Thread Qin Wu
Hi, John: > I am wondering whether this draft should update [RFC8343] to address such > limitation. Ultimately, I think we should update the corresponding data models to reflect whatever we agree in this draft, should we progress it. In this specific case, RFC8343 has reflected what is in

Re: [OPSAWG]  WG Adoption Call for draft-opsawg-evans-discardmodel-02

2024-01-31 Thread Evans, John
Hi Qin, > [Qin Wu] Maybe a new section can be added to clarify the relation with > RFC8343. We will explicitly call out the relationship to data models. > the table in section 3 just provides model structure but doesn't specify > parameters details. Yes - agreed - we will expand on that >

[OPSAWG] Publication has been requested for draft-ietf-opsawg-mud-acceptable-urls-09

2024-01-31 Thread Henk Birkholz via Datatracker
Henk Birkholz has requested publication of draft-ietf-opsawg-mud-acceptable-urls-09 as Proposed Standard on behalf of the OPSAWG working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud-acceptable-urls/

Re: [OPSAWG] advancing PCAP drafts

2024-01-31 Thread Michael Richardson
mohamed.boucad...@orange.com wrote: > Hmm...I remember at least the following candidates changes from that > thread, e.g., > * > https://mailarchive.ietf.org/arch/msg/opsawg/u0__66zIpCMHA4syzt8fWtyx98Y/ > * >

Re: [OPSAWG] advancing PCAP drafts

2024-01-31 Thread Eliot Lear
On 31.01.2024 15:10, Michael Richardson wrote: I don't know if ISE documents can create registries: one ISE told me no. See RFC 8726.  DR not permitted unless it's a required sub-registry tied to a requested allocation. Eliot OpenPGP_0x87B66B46D9D27A33.asc Description: OpenPGP public