Re: [OPSAWG] Comments on draft-lopez-opsawg-yang-provenance-01
nded purpose? I mean, the payload is not canonicalized when it comes to whitespace, ordering of elements and many other aspects. Will your purpose still be fulfilled? Canonicalization is an essential mechanism for digital signatures of documents, based on real-life experience. Please bear in mind that we are not talking about canonicalizing the representation that goes on the wire or is stored, but to do so with the document before the signature is generated or verified, so we can be sure the signature mechanisms are being to a unique, canonical, representation of the document. We are now experimenting with a practical implementation and, as far as I can tell, the proposed canonicalization methods work. But always happy to hear any advice or experience realted to them. Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] WG Adoption Call for draft-opsawg-evans-discardmodel-02
Hi, As I think I already had the opportunity to express in past meetings, this proposal is of high interest for service providers. I support adoption. Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 17/1/24, 12:52, wrote: Dear OPSAWG members, this email starts a call for Working Group Adoption of > https://www.ietf.org/archive/id/draft-opsawg-evans-discardmodel-02.html ending on Wednesday, January 31st. As a reminder, this I-D describes an information model in support of automated network mitigation on what and how to report about unintentional packet discards/losses that can have an impact on service level objectives. Implementation of the informational model, which could manifest, e.g., via NETCONF/YANG, SNMP or IPFIX, is out-of-scope. The chairs acknowledge feedback to and interest for the topic during the IETF118 meeting and on the list after afterwards. We would like to gather feedback from the WG if there is interest to further contribute and review. Please reply with your support and especially any substantive comments you may have. For the OPSAWG co-chairs, Henk ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] [inventory-yang] poll for network inventory base model
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: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 29/8/23, 11:58, 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:jcla...@cisco.com] Sent: Monday, August 28, 2023 10:26 PM To: maqiufang (A) ; inventory-y...@ietf.org Cc: ivy-cha...@ietf.org; opsawg ; cc...@ietf.org 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 mailto:inventory-yang-boun...@ietf.org>> on behalf of maqiufang (A) mailto:maqiufang1=40huawei@dmarc.ietf.org>> Date: Monday, August 28, 2023 at 02:22 To: inventory-y...@ietf.org<mailto:inventory-y...@ietf.org> mailto:inventory-y...@ietf.org>> Cc: ivy-cha...@ietf.org<mailto:ivy-cha...@ietf.org> mailto:ivy-cha...@ietf.org>>, opsawg mailto:opsawg@ietf.org>>, cc...@ietf.org<mailto:cc...@ietf.org> mailto:cc...@ietf.org>> 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 er
Re: [OPSAWG] Call for presentation//FW: IETF 117 Preliminary Agenda
Hi Tianran, As part of the development of draft-ietf-opsawg-collected-data-manifest we have been elaborating a proposal for verifying the provenance of YANG data. After some discussion among the authors, we believe it would be better to have it as a separate draft, as there are many potential use cases other than manifests. I am currently working on such a draft (not yet finished, so I cannot share a reference), and would like to ask for some airtime at the coming OPSAWG meeting before we run out of it… Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 25/6/23, 10:40, wrote: Hi WG, The IETF117 preliminary agenda is posted. The OPSAWG meeting is scheduled on WEDNESDAY, July 26, 1300-1500 Session II. We start to accept presentation request. Please send over your request with title, speaker, time slot, and draft name to the chairs. Cheers, Tianran -Original Message- From: WGChairs [mailto:wgchairs-boun...@ietf.org] On Behalf Of IETF Agenda Sent: Saturday, June 24, 2023 5:14 AM To: Working Group Chairs Subject: IETF 117 Preliminary Agenda IETF 117 San Francisco, CA, USA July 22-28, 2023 Hosted By: NOKIA The IETF 117 preliminary agenda has been posted. The final agenda will be published on Friday, June 30, 2023. If you would like to request a change to the preliminary agenda, please send a message to supp...@ietf.org and copy all relevant Area Directors. https://datatracker.ietf.org/meeting/117/agenda.html https://datatracker.ietf.org/meeting/117/agenda.txt The preliminary agenda includes all planned WG, RG, and BoF sessions. Information about side meetings will be available when the final agenda is posted. Thank you! IETF Secretariat ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg 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 privacidad@telefonica.com<mailto:privacidad@telefonica.com>. 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 privacidad@telefonica.com<mailto:privacidad@telefonica.com>. 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 Tel
Re: [OPSAWG] POLL FOR IPR: A Data Manifest for Contextualized Telemetry Data
No, I'm not aware of any IPR that applies to this draft -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 2/5/23, 00:20, wrote: Authors and contributors on the To: line, please respond on-list as to whether or not you are aware of any IPR that pertains to this work. Please state either: "No, I'm not aware of any IPR that applies to this draft" or "Yes, I'm aware of IPR that applies to this draft" If you are aware of IPR, indicate whether or not this has been disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179). Joe 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] IPR Poll on draft-palmero-opsawg-dmlmo-09
I am not aware of any IPR related to this draft. And, as coauthor, I support adoption. This draft not only address a relevant issue in operations, but it has become the base of a wider discussion on related aspects, of strong relevance to operational practices. Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 17/3/23, 02:28, wrote: Hi Authors and Contributors, Accompany with the WG adoption on this draft, I'd like all authors and contributors to confirm on the list. https://datatracker.ietf.org/doc/draft-palmero-opsawg-dmlmo/ Please respond if you are aware of any IPR related to this draft. If you are aware of IPR, please indicate whether or not this has been disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179). Thanks, Tianran 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)
Hi, I support progressing to the next stage with this document. As expressed before, it addresses interesting aspects for IPFIX, already demonstrated in practice. Be goode, -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - Hello, WG. As discussed at IETF 115, we want to conduct a WG LC for draft-ietf-opsawg-ipfix-srv6-srh. The authors believe this work is stable and moreover used the 115 hackathon to develop a interoperable implementations (linked in Data Tracker) . Additionally, IANA has already weighed in on this work and agree with the considerations approach. Therefore, we are calling for a two week LC. We will conclude on December 14. https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-ipfix-srv6-srh%2F=05%7C01%7CThomas.Graf%40swisscom.com%7C36a11155a7944e95206e08dad2da5cd7%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C638054132559465491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=dLCgkB2fT8%2Fy1gjuuG4r9zXoDC4a7FVkgHLX8GuOUkU%3D=0> Please review the current -04 draft, post your comments and/or your thoughts on the current text. Thanks. Joe 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh
I support adoption. -- “Esta vez no fallaremos, Doctor Infierno” Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 - On 18/8/22, 22:15, wrote: Hello, WG. We’d like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IETF 114 there does seem to be interest in adopting this in opsawg, but we need a formal adoption poll. Please review and provide your adoption thoughts no later than September 1, 2022. Thanks. Joe 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] WGLC for draft-ietf-opsawg-service-assurance-yang-05
Hi, I support moving ahead with the document. Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 -- On 22/06/2022, 15:19, "OPSAWG on behalf of IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA" mailto:opsawg-boun...@ietf.org> on behalf of ignacio.dominguezmarti...@telefonica.com<mailto:ignacio.dominguezmarti...@telefonica.com>> wrote: AVISO/WARNING: Este mail se ha originado fuera de la organización y no se pudo verificar al remitente / This mail was originated outside the organization and the sender could not be verified Dear OPSAWG, As companion of the SAIN architecture, I also support this document. The YANG module well captures the health of a service as graph. Best regards, Nacho. From:Tianran Zhou To:opsawg Date:2022-06-08 12:05:04 Subject:[OPSAWG] WGLC for draft-ietf-opsawg-service-assurance-yang-05 Hi WG, This mail we start a two weeks working group last call for draft-ietf-opsawg-service-assurance-yang-05. https://datatracker.ietf.org/doc/draft-ietf-opsawg-service-assurance-yang/ Please send over your comments before June 22. Please also indicate if you think this document is ready to progress. Cheers, Tianran, on behalf of chairs ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg 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 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] IPR poll for draft-ietf-opsawg-service-assurance-yang-05 and draft-ietf-opsawg-service-assurance-architecture-03
No, I'm not aware of any IPR that applies to this draft. Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 -- Dear authors and contributors, As part of the working group last call, please respond on-list as to whether or not you are aware of any IPR that pertains to draft-ietf-opsawg-service-assurance-yang-05 and draft-ietf-opsawg-service-assurance-architecture-03. State either: "No, I'm not aware of any IPR that applies to this draft." or "Yes, I'm aware of IPR that applies to this draft." If you are aware of IPR, indicate whether or not this has been disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179). For the OPAWG co-chairs, Tianran 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] IETF DLMO draft side-meeting
Hi Marisol, Though I was not able to join you yesterday, I am glad to see the work progressing and glad to see you confirmed my interest in joining the draft author list. Thanks! Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Mobile: +34 682 051 091 -- On 02/02/2022, 17:09, "Marisol Palmero Amador (mpalmero)" mailto:mpalm...@cisco.com>> wrote: Just to inform the WG, We have hosted a preparation call in order to start the “DMLMO draft” side meetings next week: **IETF DMLMO side meeting kick-off (Feb/2)** Attendees * Sudhendu * Shwetha * Marisol * Frank ** DMLMO side meetings are bi-weekly, starting Feb/9 - 7am PST ** * meetings notes will be typed from: https://notes.ietf.org/ZOfqY-9CSr2SYVeWFfEFsw?both (to be updated in git repo) * Preparation slides in google docs: https://docs.google.com/presentation/d/143-D3kRFKqqGd2OPUj_kqW7l31TtZjUfVeMYkdzbv7U/edit?usp=sharing Initial list of topics to review & discuss: * "Organizations" in YANG * Licenses linked to Features vs Assets/ License “Catalog” * LifeCycle for (V)NF vs existing YANG modules * Inventory, DMLMO doesnt´t have an objective to focus on inventory management, but the group is open to collaborate and even consumed from other efforts. * Round table Marisol Palmero From: "Joe Clarke (jclarke)" Date: Wednesday, 26 January 2022 at 16:47 To: "opsawg@ietf.org" , Marisol Palmero Cc: Sudhendu Kumar , Shwetha Bhandari Subject: Re: [OPSAWG] IETF DLMO draft side-meeting Marisol, while you work to refine this document ahead of any potential WG adoption, please bring back any relevant discussions to this list so you have a record of interest. Comments from interested parties will help gauge interest should you wish to have opsawg adopt this document. Thanks. Joe On 1/25/22 15:41, Marisol Palmero Amador (mpalmero) wrote: Dear OPSA WG, We would like to extend this invitation to the OPSA WG to participate and collaborate in the open discussions for those interested in DMLMO draft<https://datatracker.ietf.org/doc/html/draft-palmero-opsawg-dmlmo>. Calls are scheduled to start on February 9th Calls will be hosted every two weeks: On Wednesday´s starting at 16:00 CET (initially scheduled for 50 min) Please those who are interested feel free to reach out directly, and I will be happy to include you in the outlook invitation Thanks, Marisol Call invitation: IETF DMLMO review side meeting Hosted by Marisol Palmero Amador https://cisco.webex.com/cisco/j.php?MTID=m1618495147d8245ce945e1e61b5a42b1 Wednesday, 9 Feb, 2022 16:00 | 50 minutes | (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna Occurs every 2 week(s) on Wednesday effective 2/9/2022 until 7/27/2022 from 4:00 PM to 4:50 PM, (UTC+01:00) Brussels, Copenhagen, Madrid, Paris Meeting number: 2578 169 4611 Password: cwBUWiYb526 (29289492 from phones) Join by video system Dial 25781694...@webex.com<mailto:25781694...@webex.com> You can also dial 173.243.2.68 and enter your meeting number. Join by phone +34-91-201-2149 Spain Madrid Toll +34-93-446-6598 Spain Barcelona Toll Access code: 257 816 94611 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 privileged and confidential 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 ___
Re: [OPSAWG] IPR poll for draft-ietf-opsawg-model-automation-framework-03
Hi, I am not aware of any IPR that applies to this document. Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Tel: +34 913 129 041 Mobile: +34 682 051 091 -- On 02/06/2020, 07:25, "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" mailto:mohamed.boucad...@orange.com>> wrote: Hi all, I’m forwarding this request in case you are not on the opsawg mailing list. Please rely to this poll from the chairs. Thank you. Cheers, Med De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Tianran Zhou Envoyé : lundi 1 juin 2020 04:37 À : opsawg@ietf.org Cc : OpsAWG-Chairs Objet : [OPSAWG] IPR poll for draft-ietf-opsawg-model-automation-framework-03 Working Group, Authors, As a part of the WGLC, this email starts the IPR poll. https://datatracker.ietf.org/doc/draft-ietf-opsawg-model-automation-framework/ Are you aware of any IPR that applies to draft-ietf-opsawg-model-automation-framework-03? There are currently no IPR disclosure. If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. If you are on the OPSA WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thanks, Tianran and Joe 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 privileged and confidential 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
[OPSAWG] Substitutes for the term "closed-loop telemetry"
Hi, As you surely recall, I expressed serious concerns about the use of “closed-loop telemetry” in draft-song-opsawg-ifit-framework and related docs. The term seems to me highly misleading, as “closed-loop” is usually applied to network control and orchestration, and it would be difficult to distinguish when we are talking of one “closed-loop” or another. I’d propose to use “just-in-time telemetry” or “reflective telemetry” to indicate how the telemetry is provided according to concrete and present needs (thus just in time), or as a result of an action based on self-knowledge (hence reflective) Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Tel: +34 913 129 041 Mobile: +34 682 051 091 -- 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 privileged and confidential 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 ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] [Netslices] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt
Hi, A colleague in the ETSI NFV has remarked to me the fact that the group has created a quite detailed spec, rooted at the ACTN ideas as well, on the interface to manage transport links among sites. I think this spec (IFA032, https://docbox.etsi.org/ISG/NFV/Open/Publications_pdf/Specs-Reports/NFV-IFA%20032v3.2.1%20-%20GS%20-%20Multi-site%20Intfaces%20and%20InfoModel%20spec.pdf) is a valuable foundation for the goals of this draft. Be goode, -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D https://www.linkedin.com/in/dr2lopez/ e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com> Tel: +34 913 129 041 Mobile: +34 682 051 091 -- On 08/07/2019, 13:08, "Netslices on behalf of Rokui, Reza (Nokia - CA/Ottawa)" mailto:netslices-boun...@ietf.org> on behalf of reza.ro...@nokia.com<mailto:reza.ro...@nokia.com>> wrote: Sure Takuya I will add them to the new version of the draft. Cheers, Reza From: Takuya Miyasaka Date: Sunday, July 7, 2019 at 9:07 PM To: Reza Rokui , "netsli...@ietf.org" , "rt...@ietf.org" , "opsawg@ietf.org" , "t...@ietf.org" , "d...@ietf.org" Subject: Re: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt Hi Reza, Thanks for your response and please see my comments below with [Taku]. Thanks, Takuya On 2019/07/04 23:51, Rokui, Reza (Nokia - CA/Ottawa) wrote: Hi Takuya, Very good question. The response is inline. Reza From: Takuya Miyasaka <mailto:ta-miyas...@kddi-research.jp> Date: Wednesday, July 3, 2019 at 7:54 AM To: Reza Rokui <mailto:reza.ro...@nokia.com>, "netsli...@ietf.org"<mailto:netsli...@ietf.org> <mailto:netsli...@ietf.org>, "rt...@ietf.org"<mailto:rt...@ietf.org> <mailto:rt...@ietf.org>, "opsawg@ietf.org"<mailto:opsawg@ietf.org> <mailto:opsawg@ietf.org>, "t...@ietf.org"<mailto:t...@ietf.org> <mailto:t...@ietf.org>, "d...@ietf.org"<mailto:d...@ietf.org> <mailto:d...@ietf.org> Subject: Re: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt Hi Reza, Thanks for sharing this draft. I'm curious about how to bind/associate 3GPP(RAN/Core) slice instance and Transport slice instance and section 5.2 of this draft describes as follows: o In order to have the connectivity between RAN1 and UPF1, the RAN and Core slices should be associated to Transport slice. This is also a by-product of the Transport slice connectivity interface when all allocated resources for access points (such as allocated VLAN IDs, IP addresses etc) are conveyed to RAN and Core Slices. This will be done by cordiantion between transport slice controller and E2E network slice controller. As for this sentences, could you confirm if following procedures will be conducted between controllers in order to associate independent slice instances or not? - E2E Network Slice Controller sends a request on transport slice creation to Transport Controller (interface 10 of Fig.2) - Transport Controller creates transport slice instance and sends access point information(e.g. VLAN ID) to E2E Network Slice Controller - E2E Network Slice Controller sends a request on access point creation/modification to RAN/Core Controller - RAN/Core Controller create/modify access point on gNB/UPF respectively, which means gNB/UPF starts to attach adequate access point information(e.g. VLAN ID) on their user plane packet [Reza] The above procedure is correct but this is one way to implement the binding (aka association) between RAN-Transport slices and Core-Transport slices. [Taku] OK. If such kinds of procedures are taken at Core/RAN Controller, it might be better to describe such procedures in Section3. We also have to check if these access point information can be conveyed at the 3GPP defined interface between E2E Controller and Core/RAN Controller. There are other ways to implement the binding. For example, the transport slice controller can populate the following two tables dynamically during the transport slice creation, modification or deletion and expose access to this table using open APIs. Then, the RAN/Core network functions or RAN/Core slice controllers can access these APIs to program the VLAN/IP/Labels. · RAN-Transport mapping table: Which maps the RAN VLAN/IP address/MPLS Labels etc to network slice · Core-Transport mapping table: Which maps the Core VLAN/IP address/MPLS Labels etc to network slice [Taku] That sounds good. · Thanks, Takuya Miyasaka KDDI Research On 2019/07/02 23:06, Rokui, Reza (Nokia - CA/Ottawa) wrote: Hi all, This is to inform you that the following new draft has been submitted to ietf. The goal of this draft is to demonstr
Re: [OPSAWG] [sfc] Question regarding Proof of Transit draft
Hi Sashank, (coming back to this as soon as my holidays and the backlog they caused allow me) Thanks! I must confess I attended Frank’s presentation and went directly to my interpretation of Shamir’s polynomials, overlooking some of the optimizations you propose. And coming back to what Frank asked a couple of messages before in the thread I fully agree it is worthwhile to pursue this in SFC. I can think of applications in NFV-space, and in the scenario of the hierarchical SFC some of us are proposing. In fact, I’ve been discussing this with other colleagues at the ETSI NFV meeting I am attending now. Be goode, On 1 Sep 2016, at 15:22 , Sashank Dara (sadara) <sad...@cisco.com<mailto:sad...@cisco.com>> wrote: Hi Diego , Thanks for bringing up an excellent point on the computational complexity. Fortunately the algorithm takes a cumulative approach which is agnostic of the path length. 1. Controller performs few trivial steps like choosing long term secrets, calculating the LPC values for each node and provisioning. 2. Each node only performs 2 additions, 1 multiplication and 1 mod(prime) operation per packet . 3. Verifier also performs step (2) and additionally performs 1 addition, 1 mod(prime) and comparison to verify ! The above steps hold good for any length of nodes. A detailed example is provided for illustrative purposes in our draft<https://tools.ietf.org/html/draft-brockners-proof-of-transit-01#section-3.3> (section 3.3) that explains above operations. Would be happy to discuss more on the above, if needed. Regards, Sashank From: "Diego R. Lopez" <diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com>> Date: Friday, 26 August 2016 at 6:21 PM To: "Frank Brockners (fbrockne)" <fbroc...@cisco.com<mailto:fbroc...@cisco.com>> Cc: Tal Mizrahi <ta...@marvell.com<mailto:ta...@marvell.com>>, sashank dara <sad...@cisco.com<mailto:sad...@cisco.com>>, "draft-brockners-proof-of-tran...@tools.ietf.org<mailto:draft-brockners-proof-of-tran...@tools.ietf.org>" <draft-brockners-proof-of-tran...@tools.ietf.org<mailto:draft-brockners-proof-of-tran...@tools.ietf.org>>, "opsawg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.org>>, "n...@ietf.org<mailto:n...@ietf.org>" <n...@ietf.org<mailto:n...@ietf.org>>, "s...@ietf.org<mailto:s...@ietf.org>" <s...@ietf.org<mailto:s...@ietf.org>> Subject: Re: [sfc] Question regarding Proof of Transit draft Hi Frank, This is a really interesting piece of work, and I must say we have been discussing the PoT issue with some customers (though we used to call it “assured path traversal”) and we have been exploring possible solutions, trying to combine good-enough security with a reasonable amount of computational complexity, and I am glad to see a practical proposal addressing this problem. I had a brief conversation with Carlos while in Berlin, but I am afraid that the IETF week was too hectic for a detailed discussion. Let me add to Tal’s analysis a third issue to consider. My understanding of Shamir’s polynomials is that they can be used to reconstruct a secret from N pieces you need a polynomial of degree N-1, so that implies that the verification is limited to a certain number of SFs (or SFFs), depending on the degree of the applied polynomial. We’d need and assessment on the computational complexity associated with path length and the requirements for adaptation of the PoT nodes (I guess SDN/NFV could play a role there…) Be goode, On 20 Jul 2016, at 09:16 , Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>> wrote: Hi Tal, well... if you could protect the integrity of the data stream between source and destination, you would not be able to swap the content of a packet – which is what your attack is all about. Rather than continue arguing the point, let’s acknowledge that it is a valid attack and let’s look for a solution :-). We’ll need to couple POT to integrity protection of the packet. Hence, I’d like to come back to my question asked below: Do you (and the entire SFC team here) think it is worthwhile to provide a solution for a deployment which is expected to *not* alter the packet payload? Thanks, Frank From: Tal Mizrahi [mailto:ta...@marvell.com] Sent: Dienstag, 19. Juli 2016 18:15 To: Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>; Sashank Dara (sadara) <sad...@cisco.com<mailto:sad...@cisco.com>>; draft-brockners-proof-of-tran...@tools.ietf.org<mailto:draft-brockners-proof-of-tran...@tools.ietf.org> Cc: s...@ietf.org<mailto:s...@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>; n...@ietf.org<mailto:n...@ietf.org> Subject: RE: Question regarding Proof of Transi
