Hi, I was about to send a reply in the same sense as Joe’s. I’d support a solution based on draft-ietf-ccamp-network-inventory-yang-02 draft, incorporating some (many) valid aspects in draft-wzwb-opsawg-network-inventory-management-03.
I guess this could be considered as a (3), with stronger (1) flavor… Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: [email protected]<mailto:[email protected]> Mobile: +34 682 051 091 --------------------------------- On 29/8/23, 11:58, <[email protected]> wrote: Hi, Joe, WG, As a clarification: For this polling, we’re trying to figure out if there is a consensus to use one of the existing documents as a starting point. If there is, the chairs’ assumption is to ask the authors to move the work to IVY, instead of just referencing it progressed in other places. It may still take some time for the WG (e.g., via design team discussion, interim meeting(s)) to tailor the work to fully fit the IVY charter, that’s why we say “evolve it to become the network inventory base model”. Best Regards, Qiufang From: Joe Clarke (jclarke) [mailto:[email protected]] Sent: Monday, August 28, 2023 10:26 PM To: maqiufang (A) <[email protected]>; [email protected] Cc: [email protected]; opsawg <[email protected]>; [email protected] Subject: Re: [inventory-yang] poll for network inventory base model Since you copied opsawg, I’ll make it clear my reply is as a contributor. As I said at the first IVY meeting, I like the CCAMP work a bit more as a base inventory draft. It feels more data-centric and less use-case centric if that makes sense. That said, it’s adopted work in CCAMP. What would happen to it? Would it move to IVY? Would IVY work just reference it as it progresses through CCAMP? While I like option 1, I think perhaps option 3 might be more viable, but using the model of the CCAMP work where it leverages previous ENTITY-MIB concepts while staying true to common inventory. Joe From: Inventory-yang <[email protected]<mailto:[email protected]>> on behalf of maqiufang (A) <[email protected]<mailto:[email protected]>> Date: Monday, August 28, 2023 at 02:22 To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, opsawg <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [Inventory-yang] [inventory-yang] poll for network inventory base model Hi Working Group, It’s now time to start considering how to move forward with the inventory base model. We have two different documents that could be used as a starting point for our work or, in case the working group believes none of them is “good enough”, we can start a brand new ID. In case the latter option is chosen, Daniele and I will write a -00 version including just the table of content and what we’d like to be covered in each section. The document will then be handed over to a pool of authors which will bring it till the WG adoption. Hence, we will have a 3 weeks polling starting today. We decided to make it a bit longer than usual because this time the working group is requested to review two drafts instead of one. This mail starts a 3 weeks polling, terminating on September 15th, where we would like the working group to express your preference among: 1. Adopt draft-ietf-ccamp-network-inventory-yang-02 in IVY and evolve it to become the network inventory base model 2. Adopt draft-wzwb-opsawg-network-inventory-management-03 in IVY and evolve it to become the network inventory base model 3. Start a brand new document from scratch as described above In the week after the closure of the polling (between September 18 and 25) we will have an IVY interim meeting to discuss the issues/concerns raised during the polling ( A separate mail will be sent). Thank you, Qiufang and Daniele ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição ________________________________ Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telefónica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relación establecida con el destinatario o con la entidad a la que está vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a [email protected]<mailto:[email protected]>. Puede consultar información adicional sobre el tratamiento de sus datos en nuestra Política de Privacidad<https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/>. We inform you that the data controller is the Telefónica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to [email protected]<mailto:[email protected]>. You may consult additional information on the processing of your data in our Privacy Policy<https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>. Informamos que o responsável pelo tratamento dos seus dados é a entidade do Grupo Telefónica vinculada ao remetente, a fim de manter o contato professional e administrar a relação estabelecida com o destinatário ou com a entidade à qual esteja vinculado. Você pode entrar em contato com o responsável do tratamento de dados e exercer os seus direitos escrevendo a [email protected]<mailto:[email protected]>. Você pode consultar informação adicional sobre o tratamento do seus dados na nossa Política de Privacidade<https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/>.
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
