Re: [OPSAWG] [IANA #1267381] expert review for draft-ietf-opsawg-sbom-access (well-known-uris)

2023-02-28 Thread Mark Nottingham
That looks fine to me. Cheers, > On 1 Mar 2023, at 9:38 am, David Dong via RT > wrote: > > Dear Mark (cc: opsawg WG), > > As the designated expert for the Well-Known URIs registry, can you review the > proposed registration in draft-ietf-opsawg-sbom-access for us? Please see > >

Re: [OPSAWG] [IANA #1267380] expert review for draft-ietf-opsawg-sbom-access (xml-registry)

2023-02-28 Thread Martin Thomson
LGTM, thanks. On Wed, Mar 1, 2023, at 09:34, David Dong via RT wrote: > Dear Tim and Martin (cc: opsawg WG), > > As the designated experts for the ns registry, can you review the > proposed registration in draft-ietf-opsawg-sbom-access for us? Please > see > >

[OPSAWG] [IANA #1267381] expert review for draft-ietf-opsawg-sbom-access (well-known-uris)

2023-02-28 Thread David Dong via RT
Dear Mark (cc: opsawg WG), As the designated expert for the Well-Known URIs registry, can you review the proposed registration in draft-ietf-opsawg-sbom-access for us? Please see https://datatracker.ietf.org/doc/draft-ietf-opsawg-sbom-access/ The due date is March 14, 2023. If this is OK,

[OPSAWG] [IANA #1267380] expert review for draft-ietf-opsawg-sbom-access (xml-registry)

2023-02-28 Thread David Dong via RT
Dear Tim and Martin (cc: opsawg WG), As the designated experts for the ns registry, can you review the proposed registration in draft-ietf-opsawg-sbom-access for us? Please see https://datatracker.ietf.org/doc/draft-ietf-opsawg-sbom-access/ The due date is March 14, 2023. If this is OK, when

[OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Zaheduzzaman Sarker via Datatracker
Zaheduzzaman Sarker has entered the following ballot position for draft-ietf-opsawg-tlstm-update-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)

Re: [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Randy Presuhn
Hi - On 2023-02-28 6:39 AM, Joe Clarke (jclarke) wrote: Thanks for the review, Eric (and Lars). There was no formal MIB Doctor review, but we did receive comments from Jürgen and Randy, who are members of MIB Doctors (I believe), during the progress of this draft.  Those comments were

[OPSAWG] John Scudder's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread John Scudder via Datatracker
John Scudder has entered the following ballot position for draft-ietf-opsawg-tlstm-update-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer

Re: [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Jürgen Schönwälder
It may help to point out that the MIB module is mostly unchanged, nothing in the design or structure of the MIB module did change as far as I know. /js On Tue, Feb 28, 2023 at 02:39:47PM +, Joe Clarke (jclarke) wrote: > Thanks for the review, Eric (and Lars). > > There was no formal MIB

Re: [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Joe Clarke (jclarke)
Thanks for the review, Eric (and Lars). There was no formal MIB Doctor review, but we did receive comments from Jürgen and Randy, who are members of MIB Doctors (I believe), during the progress of this draft. Those comments were helpful in deciding on the language changes within the MIB

[OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Éric Vyncke via Datatracker
Éric Vyncke has entered the following ballot position for draft-ietf-opsawg-tlstm-update-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer

Re: [OPSAWG] [Gen-art] Genart last call review of draft-ietf-opsawg-tlstm-update-11

2023-02-28 Thread Lars Eggert
Joel, thank you for your review. I have entered a No Objection ballot for this document. Lars > On Feb 10, 2023, at 01:56, Joel Halpern via Datatracker > wrote: > > Reviewer: Joel Halpern > Review result: Ready > > I am the assigned Gen-ART reviewer for this draft. The General Area >

[OPSAWG] Lars Eggert's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-02-28 Thread Lars Eggert via Datatracker
Lars Eggert has entered the following ballot position for draft-ietf-opsawg-tlstm-update-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer

Re: [OPSAWG] Call for presentation//FW: [116all] IETF 116 Preliminary Agenda

2023-02-28 Thread Benoit Claise
Dear Tianran, I would like to get some time to present an update of draft-claise-opsawg-collected-data-manifest The authors are busy updating the draft. 15 min would be sufficient. Regards, Benoit On 2/27/2023