[OPSAWG]Re: REQUEST FOR PRESENTATIONS: Opsawg 120 session

2024-07-07 Thread Mahesh Jethanandani
lleviate them. It would be very beneficial to get > IETF's participants feedback and suggestions on what is the better next step > to take for BBF or its members towards IETF to get an IETF solution for the > scalability issue identified. > An IETF response liaison to BBF w

[OPSAWG]Re: process forward for draft-ietf-opsawg-mud-iot-dns-considerations

2024-07-03 Thread Mahesh Jethanandani
S and DNSSD”, another WG LC, albeit shorter (1 >> week), would be in order. > > Works for me. Mahesh Jethanandani mjethanand...@gmail.com ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org

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

2024-07-02 Thread Mahesh Jethanandani
e what order they should be read in. Time for me to write my own set of Cliff notes for the drafts that Warren so good about.  Mahesh Jethanandani mjethanand...@gmail.com ___ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org

[OPSAWG]Re: process forward for draft-ietf-opsawg-mud-iot-dns-considerations

2024-06-24 Thread Mahesh Jethanandani
Mahesh will decide to skip that or not. > > -- > Michael Richardson. o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > Mahesh Jethanandani mjethanand...@gmail.com ___ OP

[OPSAWG]AD review of draft-ietf-opsawg-ac-lxsm-lxnm-glue

2024-06-08 Thread Mahesh Jethanandani
references draft-ietf-opsawg-teas-attachment-circuit-09, but -13 is the latest available revision. Document references draft-ietf-opsawg-ntw-attachment-circuit-07, but -11 is the latest available revision. Document references draft-ietf-netmod-rfc8407bis-09, but -11 is the latest available revisio

[OPSAWG]Fwd: New Liaison Statement, "LS on the new work item ITU-T Q.MUD_IoT “Framework for testing and monitoring IoT devices & networks using technical Requirements from Manufacturer Usage Descripti

2024-05-22 Thread Mahesh Jethanandani
itu-t-sg-11-ietf-ls-on-the-new-work-item-itu-t-qmud_iot-framework-for-testing-and-monitoring-iot-devices-networks-using-technica-attachment-1.pdf > >LS196 > > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2024-05-22-itu-t-sg-11-ietf-ls-on-the-new-work-item-itu-t-qm

[OPSAWG] AD review of draft-ietf-opsawg-tsvwg-udp-ipfix

2024-04-16 Thread Mahesh Jethanandani
al K but other times it is used with a small k. Document references draft-ietf-tsvwg-udp-options-28, but -32 is the latest available revision. Document references draft-ietf-opsawg-ipfix-tcpo-v6eh-08, but -10 is the latest available revision. Mahesh Jethanandani mjethanand...@gmail.com ___

Re: [OPSAWG] AD review of draft-ietf-opsawg-ipfix-tcpo-v6eh

2024-04-15 Thread Mahesh Jethanandani
etf-opsawg-ipfix-tcpo-v6eh.txt>. > > Please see more context inline. > > Cheers, > Med > > De : Mahesh Jethanandani <mailto:mjethanand...@gmail.com>> > Envoyé : dimanche 14 avril 2024 21:42 > À : draft-ietf-opsawg-ipfix-tcpo-v...@ietf.org > <mailto:draft-

Re: [OPSAWG] AD review of draft-ietf-opsawg-ipfix-fixes

2024-04-15 Thread Mahesh Jethanandani
e for more context. > > Cheers, > Med > > De : Mahesh Jethanandani <mailto:mjethanand...@gmail.com>> > Envoyé : dimanche 14 avril 2024 05:21 > À : draft-ietf-opsawg-ipfix-fi...@ietf.org > <mailto:draft-ietf-opsawg-ipfix-fi...@ietf.org> > Cc : opsawg@ietf.

[OPSAWG] AD review of draft-ietf-opsawg-ipfix-tcpo-v6eh

2024-04-14 Thread Mahesh Jethanandani
identifying root causes of performance degra > ^^^ The verb "help" is used with an infinitive. Section 4.2, paragraph 6 > [RFC8883] for a behavior of an intermediate nodes that encounters an unknown > ^ The plural noun "nodes" cannot be used with the article "an". Did you mean "an intermediate node" or "intermediate nodes"? Mahesh Jethanandani mjethanand...@gmail.com ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] AD review of draft-ietf-opsawg-ipfix-fixes

2024-04-13 Thread Mahesh Jethanandani
eshold event. Values for t > ^ If "type" is a classification term, "a" is not necessary. Use "type of". (The phrases "kind of" and "sort of" are informal if they mean "to some extent".). Section 6.23.1, paragraph 4 > | | | table below, and section Section 5.1. | | 2 | PmA | Pe > ^^^ Possible typo: you repeated a word. Section 6.24.2, paragraph 1 > SHOULD have this flag set, and vice-versa.) | ++--+- >^^ The expression "vice versa" is spelled without hyphens. Section 7.2.1, paragraph 1 > SHOULD have this flag set, and vice-versa.) | ++--+- >^^ The expression "vice versa" is spelled without hyphens. Mahesh Jethanandani mjethanand...@gmail.com ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] Paul Wouters' Abstain on draft-ietf-opsawg-mud-acceptable-urls-11: (with COMMENT) [Was Re: Your abstain on draft-ietf-opsawg-mud-acceptable-urls]

2024-04-13 Thread Mahesh Jethanandani
le from the manufacturor. In a way, >> one could see this as a firmware that has a bit of external firmware hosted >> elsewhere. And these two can get out of sync. To me that just seems like >> broken firmware and building a protocol mechanism to resolve thi

Re: [OPSAWG] Rtgdir early review of draft-ietf-opsawg-ac-lxsm-lxnm-glue-06

2024-04-02 Thread Mahesh Jethanandani
] Added a new section. > >> Is there any way to merge some of these drafts together or do they all >> have to be separate. It makes it difficult for the reader to follow >> the solution. >> >> Nits: >> Remove all the bold of lines within the draft. AFAIK it makes it >> difficult for the user to read. >> > > [Med] Done > >> ! Additional drafts reviewed >> draft-ietf-opsawg-teas-common-ac-05 >> >> Major Issues: >> None >> >> Minor Issues: >> >> Is the goal of this draft to take items that are common between all >> ACs for the L2NM & L2SM modules. Why not make this part of one of the >> other drafts like the ac-glue or even the ACAAS draft. >> >> I would recommend showing how all 4 drafts work together in each of >> the 4 drafts as they all work together to provide the overall AC >> solution. >> >> draft-ietf-opsawg-ac-lxsm-lxnm-glue-06 >> draft-ietf-opsawg-ntw-attachment-circuit-05 >> draft-ietf-opsawg-teas-attachment-circuit-06 >> draft-ietf-opsawg-teas-common-ac-05 >> > > [Med] Done. > >> Is there any way to merge some of these drafts together or do they all >> have to be separate. It makes it difficult for the reader to follow >> the solution. >> >> Nits: >> None >> >> > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. Mahesh Jethanandani mjethanand...@gmail.com ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] Mahesh Jethanandani's No Objection on draft-ietf-opsawg-mud-iot-dns-considerations-13: (with COMMENT)

2024-03-29 Thread Mahesh Jethanandani via Datatracker
Mahesh Jethanandani has entered the following ballot position for draft-ietf-opsawg-mud-iot-dns-considerations-13: 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

[OPSAWG] Review comments on draft-ietf-opsawg-mud-iot-dns-considerations-10

2024-02-08 Thread Mahesh Jethanandani
much later in the document. Please define in a Terminology Section or somewhere before first use. > IoT Devices SHOULD prefer doing DNS to with the DHCP provided DNS servers. Grammar? > The ADD WG has written [I-D.ietf-add-dnr] and [I-D.ietf-add-ddr] to provided. Same here. Mahesh Jet

[OPSAWG] Fwd: Network Modeling (netmod) WG Interim Meeting: 2023-06-05

2023-06-02 Thread Mahesh Jethanandani
And here is some background on the talk on Monday. Begin forwarded message:From: Jeffrey Haas Date: June 2, 2023 at 10:15:49 AM PDTTo: RTGWG Cc: Mahesh Jethanandani Subject: Fwd: Network Modeling (netmod) WG Interim Meeting: 2023-06-05Sorry for the late forward.  This coming Monday, Mahesh and I

[OPSAWG] Fwd: [netmod] June 5 Virtual Interim: YANG Modelling in IETF WGs – Sharing Lessons Learned

2023-06-02 Thread Mahesh Jethanandani
ation: >> Virtual, >> >> >> Agenda: >> Title: YANG Modelling in IETF WGs – Sharing Lessons Learned >> >> Description: Expanding on the IETF116 presentation “Lessons from Working >> on BGP YANG” from Jeffrey Haas and Mahesh Jethanandani.

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-mud-14.txt

2018-01-24 Thread Mahesh Jethanandani
url2=draft-ietf-opsawg-mud-14> >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by

Re: [OPSAWG] draft-ietf-opsawg-mud: YANG validation

2017-09-21 Thread Mahesh Jethanandani
I have fixed these warning. Eliot, I am including the updated ACL models. Can you verify?These changes will be uploaded as part of the next update that Sonal is planning to post on Oct. 2. ietf-access-control-list@2017-09-21.yang Description: Binary data ietf-packet-fields@2017-09-21.yang