[OPSAWG]Re: 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 Descr

Agree with Michael, The essence of this work is test specification limited for IoT devices and the focus is functionalities test within the device. I think it will be more useful to test network device and MUD controller/manager. If SG11 agrees to do this, any outcome of this work item should al

Re: [OPSAWG] WG LC: Attachment circuits work

Hi, These three Attachment Circuits work were factored out from L3SM, L2SM and are important foundation components and reusable building blocks for Network Service automation, can be applied to various different service scenarios such as network slicing, L3VPN, Site to Cloud etc In addition, it

Re: [OPSAWG] IPR POLL: Attachment circuits work

Hi, Joe: No, I'm not aware of any IPR that applies to these drafts -Qin De: OPSAWG mailto:opsawg-boun...@ietf.org>> En nombre de Joe Clarke (jclarke) Enviado el: viernes, 19 de abril de 2024 16:32 Para: opsawg@ietf.org Asunto: [OPSAWG] IPR POLL: Attachment circuits work We

[OPSAWG] Opsdir last call review of draft-ietf-opsawg-mud-tls-13

Reviewer: Qin Wu Review result: Has Issues I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Com

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Hi, Nigel, Joe, and Italo Thanks for valuable input to this draft, see my reply inline below. 发件人: Davis, Nigel [mailto:nda...@ciena.com] 发送时间: 2024年2月20日 21:06 收件人: Italo Busi ; Qin Wu ; Joe Clarke (jclarke) ; Henk Birkholz ; OPSAWG ; n...@ietf.org 主题: RE: [OPSAWG] 🔔 WG Adoption Call for

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Thanks Roland for your support. I have noted down your comment in the github issue tracker https://github.com/billwuqin/network-incident/issues/6 I can see two key differences: 1. draft feng-opsawg- focus on "network as a service" interface while draft-netana-opsawg-nmrg-network-anomaly-semantics

Re: [OPSAWG]  WG Adoption Call for draft-feng-opsawg-incident-management-04

to help incident server to understand whether lower level or device level network anomaly has impact on the service, hope this clarifies. -Qin 发件人: li_zhenqi...@hotmail.com [mailto:li_zhenqi...@hotmail.com] 发送时间: 2024年2月20日 16:10 收件人: Qin Wu ; Rob Wilton (rwilton) ; alex.huang-f...@insa-lyon.fr

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Hi, NMOP Chairs: Since this document has been discussed in OPSAWG for a long time, and because it was ready for adoption there, and considering that it is now 'suddenly' in scope for NMOP, could we please consider moving the existing adoption poll to NMOP (perhaps extending it to make up for tim

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

indication of a close relationship with these other SDOs to help drive consistent use of terminology and help their members achieve desired goals. [Qin Wu] Thanks Joe for valuable input and comments, see my clarification in the presentation in IETF 116 (https://datatracker.ietf.org/meeting/116

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

+1, support as coauthor. 发件人： LUIS MIGUEL CONTRERAS MURILLOmailto:luismiguel.contrerasmuri...@telefonica.com>> 收件人： Henk Birkholzmailto:henk.birkholz@ietf.contact>>;OPSAWGmailto:opsawg@ietf.org>> 主题： Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04 时间： 2024-02-11 01:39

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

Hi Chairs: I am not aware of any IPR related to this work. 吴钦 Wu Qin Mobile：+86-13914734360(Mobile Number) Email：bill...@huawei.com 发件人： Henk Birkholzmailto:henk.birkholz@ietf.contact>> 收件人： OPSAWGmailto:opsawg@ietf.org>>;draft-feng-o

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

-邮件原件- 发件人: 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 clar

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

information model could be implemented (i.e., data models), including SNMP [RFC1157], NETCONF [RFC6241] / YANG [RFC7950], and IPFIX [RFC5153], but they are outside of the scope of this document." I will update section 1 to reference RFC8343 in addition to RFC1213. [Qin Wu] Maybe a new section

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

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 lo

Re: [OPSAWG] Network Incident Management Side Meeting Summary

ased on Situation Awareness.¶<https://datatracker.ietf.org/doc/html/draft-feng-opsawg-incident-management#appendix-A-3.4.1> -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Qin Wu 发送时间: 2023年11月10日 15:46 收件人: opsawg@ietf.org 抄送: draft-opsawg-evans-discardmo...@ietf.org; draft-netana-opsawg-nmr

[OPSAWG] Opsdir early review of draft-ietf-opsawg-ipfix-fixes-03

Reviewer: Qin Wu Review result: Has Nits I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Com

Re: [OPSAWG] Network Incident Management Side Meeting Summary

Thanks Adrian for the update, look forward to reviewing the version and happy to set up a meeting when it is ready. -Qin 发件人: Adrian Farrel [mailto:adr...@olddog.co.uk] 发送时间: 2023年12月13日 0:54 收件人: Qin Wu ; opsawg@ietf.org 抄送: draft-opsawg-evans-discardmo...@ietf.org; draft-netana-opsawg-nmrg

Re: [OPSAWG] Time Schedule Side Meeting Update

Good catch, thank Luis for additional points, we keep track these open issues in the github. -Qin 发件人: LUIS MIGUEL CONTRERAS MURILLO [mailto:luismiguel.contrerasmuri...@telefonica.com] 发送时间: 2023年11月10日 11:47 收件人: Qin Wu ; opsawg@ietf.org 抄送: Yingzhen Qu 主题: RE: Time Schedule Side Meeting

[OPSAWG] Time Schedule Side Meeting Update

Hi, Thanks to all folks who participated in the time schedule discussion on Thursday afternoon and provided good inputs; the side meeting spent one-hour discussing common model design for various use cases described in: https://datatracker.ietf.org/doc/draft-ma-opsawg-schedule-yang/ (ACL poli

[OPSAWG] Network Incident Management Side Meeting Summary

Hi, All: Thanks all folks who participated in network incident management discussion on Tuesday afternoon. The side meeting was spent one hour exploring network incident concepts and use cases; three related drafts were discussed. We received a lot of great contributions for the following draft

[OPSAWG] 转发: Network Incident Management Side meeting

;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Joe Clarke (jclarke):MAILTO:jcla...@cisco.com DESCRIPTION;LANGUAGE=zh-CN:FYI.\n-原始约会-\n发件人: Qin Wu\ n发送时间: 2023年11月5日 20:34\n收件人: Qin Wu\; adrian@olddog.c o.uk\; dan...@olddog.co.uk\; luismiguel.contrerasmuri...@telefonica.com

Re: [OPSAWG] AD review of draft-ietf-opsawg-mud-iot-dns-considerations-08

ect. -Qin -邮件原件- 发件人: Michael Richardson [mailto:mcr+i...@sandelman.ca] 发送时间: 2023年11月1日 22:56 收件人: Qin Wu 抄送: Eliot Lear ; Rob Wilton (rwilton) ; opsawg@ietf.org; draft-ietf-opsawg-mud-iot-dns-considerati...@ietf.org 主题: Re: [OPSAWG] AD review of draft-ietf-opsawg-mud-iot-dns-consideration

Re: [OPSAWG] AD review of draft-ietf-opsawg-mud-iot-dns-considerations-08

Hi Michale: If my interpretation is correct, the mapping between IP address and Name is only valid for specific session or connection, when the session or connection is torn down, The mapping is no longer valid even though you cached the them, especially, TTL exceeds the preconfigured period of

[OPSAWG] Review of draft-wang-opsawg-service-information-yang on Computing Information Exposure

Hi, Xuewei: I have read your -v 00 of draft-wang-opsawg-service-information-yang and feel it is an interesting work, since it can be used to exposure computing information. A few quick comments on this draft: 1. For computing information exposure, there are two other relevant drafts https:

[OPSAWG] YANG based Collection and Aggregation Framework//: New Version Notification for draft-opsawg-poweff-00.txt

Hi, Jan, Marisol: I have read the latest version of draft-lindblad-tlm-philatelist and feel it is very interesting draft since it can aggregate data from various different data sources using different telemetry technologies. First

Re: [OPSAWG] I-D Action: draft-feng-opsawg-incident-management-03.txt

-opsawg-incident-management-03.txt is now available. Title: Incident Management for Network Services Authors: Chong Feng Tong Hu Luis Miguel Contreras Murillo Thomas Graf Qin Wu Chaode Yu Nigel Davis Name:draft-feng

Re: [OPSAWG] CALL FOR ADOPTION: Attachment circuits work

Support, AC series breaks down connectivity service into a set of common building block, can be reused in other YANG model work, also establish the correlation with the network topology and SAP model. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2023年10月2日 21:2

Re: [OPSAWG] IPR POLL: Attachment circuits work

; ivan.by...@rbbn.com; Qin Wu ; ke-oog...@kddi.com; luis-angel.mu...@vodafone.com 主题: IPR POLL: Attachment circuits work This is a consolidated poll for the following drafts: ・ draft-boro-opsawg-teas-common-ac ・ draft-boro-opsawg-teas-attachment-circuit ・ draft-boro-opsawg

Re: [OPSAWG] [inventory-yang] poll for network inventory base model

+1, draft-ietf-Ccamp only focuses on hardware inventory while draft-wzwb is more aligned with IVY charter goal and scope and show its completeness. Maybe from each of two drafts, we can pick one leading operator and one leading vendor to work together and document the merged version. Hope this ca

Re: [OPSAWG] IPR poll for draft-ma-opsawg-ucl-acl-03

I am not aware of any IPR related to this draft. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Tianran Zhou 发送时间: 2023年9月1日 15:51 收件人: opsawg@ietf.org 抄送: opsawg-cha...@ietf.org 主题: [OPSAWG] IPR poll for draft-ma-opsawg-ucl-acl-03 Hi WG, According to the decision from IETF117, we are goin

Re: [OPSAWG] WG Adoption call for IPFIX

Support, a few comments below: draft-boucla-opsawg-ipfix-fixes-06 This draft is well written, a few comments below: 1.Section 4.1.2 It is confusing to add section Number to old text and new text. Suggest remove section numbers associated with OLD and NEW, i.e., section 4.1.2.1 and section 4.1.2.2

[OPSAWG] Review of draft-ietf-opsawg-mud-acceptable-urls-05

Hi, authors of draft-ietf-opsawg-mud-acceptable-urls-05: Sorry for late comments. I have read the latest version of draft-ietf-opsawg-mud-acceptable-urls-05 and have a few questions: 1. should Updating of the MUD files lead to updating of MUD URL? why adding capabilities involves new connectio

Re: [OPSAWG] [netmod] How many "digital twins" every single network should have? Who would map between "twins"?

, RFC8795, etc, hope this clarifies. -Qin -邮件原件- 发件人: tom petch [mailto:ie...@btconnect.com] 发送时间: 2022年12月15日 20:30 收件人: Qin Wu ; Vasilenko Eduard ; Jan Lindblad 抄送: opsawg@ietf.org; net...@ietf.org; Paolo Volpato ; Xipengxiao 主题: Re: [netmod] How many "digital twins" ev

Re: [OPSAWG] [netmod] How many "digital twins" every single network should have? Who would map between "twins"?

Hi, Eduard: Thank for bring this issue up, I think digital twins is more related to network topology model, network monitoring model rather than LxSM service delivery model or LxNM network model First, As described in RFC8969 or RFC8309, LxSM service delivery model or LxNM network model focuses

Re: [OPSAWG] 🔔 WG LC: Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)

Hi, All: Thanks authors to write this draft and validate it using Hackathon project. I take some time to review this draft, my general position is to support moving this work toward publication. Here are a few comments and suggestions: 1. Abstract: What is the difference between “the SRv6

Re: [OPSAWG] Enterprise Inventory Management Side meeting Invitation (Tuesday 8:30~9:30 Mezzanine 12 )

Hi, All We got trouble to get access to webex link which require approval. I plan to abandon webex and use Zoom link instead, sorry to bring you inconvenience. Join Zoom Meeting https://us06web.zoom.us/j/84747399084?pwd=cFFWMFB5TVdabUNlaDFrQ2V1UGE0QT09 -Qin

[OPSAWG] Enterprise Inventory Management Side meeting (Tuesday 8:30~9:30am Mezzanine 12 )

Hi, Everyone: We have planned to organize a side meeting on Network Inventory Management on Tuesday Morning 8:30~9:30am, There are several relevant drafts in this space: a. RFC8345 (Network Topology model: maintenance of an inventory of nodes contained in a network. ) b. RFC8348 (Hardware Managem

Re: [OPSAWG] Document Shepherd Review of draft-ietf-opsawg-sbom-access-11

Elliot: The suggested changes all look good, thank for clarification and addressing my comments, I will update document shepherd review to reflect the current implementation status. -Qin 发件人: Eliot Lear [mailto:l...@lear.ch] 发送时间: 2022年10月9日 20:19 收件人: Qin Wu ; opsawg 抄送: Eliot Lear ; draft

[OPSAWG] Document Shepherd Review of draft-ietf-opsawg-sbom-access-11

Hi, authors: I have read the latest version of this draft, it is well written, thank for that. Here is the identified minor issues during document shepherd review of draft-ietf-opsawg-sbom-access-11: 1. Abstract said: " It may optionally be discovered through manufacturer usage description

Re: [OPSAWG] 🔔 CALL FOR ADOPTION: RADIUS Extensions for Encrypted DNS

Thank for clarification, so Diameter protocol doesn't need to define any new attributes with similar functionality as Radius attributes, right? -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Alan DeKok 发送时间: 2022年9月15日 21:42 收件人: Qin Wu 抄送: Joe Clarke (jclarke) ; o

Re: [OPSAWG] 🔔 CALL FOR ADOPTION: RADIUS Extensions for Encrypted DNS

Med: I have read the latest version of draft-boucadair-opsawg-add-encrypted-dns and support adoption of this work with the following comments: 1. Section 1, paragraph 1said: “ The information used to populate DHCP messages and/or IPv6 Router Advertisements relies upon specific Remote Authen

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh

Support this draft, with a few comments and suggestions below: 1. It will be more reasonable to place use section before protocol definition section. 2. Please add reference to RFC defining SRv6 Endpoint Behavior in both abstract and introduction section 3. Please add referen

Re: [OPSAWG] IPR POLL: draft-ietf-opsawg-sap

Hi, Joe: No, I'm not aware of any IPR that applies to this draft. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2022年4月23日 3:01 收件人: opsawg@ietf.org 主题: [OPSAWG] IPR POLL: draft-ietf-opsawg-sap Authors and contributors, please respond on-list as to

Re: [OPSAWG] Poll for IPR: draft-ietf-opsawg-yang-vpn-service-pm

No, I'm not aware of any IPR that applies to this draft -Qin -邮件原件- 发件人: Joe Clarke (jclarke) [mailto:jcla...@cisco.com] 发送时间: 2022年3月1日 7:11 收件人: Wubo (lana) ; Qin Wu ; mohamed.boucad...@orange.com; Oscar González de Dios ; Bin Wen 主题: Poll for IPR: draft-ietf-opsawg-yang-vpn-se

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

Thanks Bo, I believe Dhruv asked the similar question as you raised. Yes, I think interconnection point in end to end connectivity spanning across multiple domains can be saps. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Wubo (lana) 发送时间: 2022年1月19日 22:27 收件人: Tianran Zhou ; opsawg@ietf.

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

I-D and I support its adoption. Few comments - 1) Figure 1 uses the term "Service Network Models" which is not defined and not aligned to RFC 8309. [Qin Wu] I think it is referred to network configuration models since it sits on top of controller described in figure 3 of RFC8309. Bu

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

Support as coauthor, I am not aware of any IPR related to this I-D. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 mohamed.boucad...@orange.com 发送时间: 2022年1月5日 15:32 收件人: Tianran Zhou ; opsawg@ietf.org 抄送: opsawg-cha...@ietf.org 主题: Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

Re: [OPSAWG] CALL FOR ADOPTION: Transport Layer Security Verion 1.3 (TLS 1.3) Transport Model for the Simple Network Management Protocol Version 3 (SNMPv3)

that a more fruitful way forward could be to ask for an early Secdir review (once the work is under way). [Qin Wu] Fully agree, I assume the consultation with MIB doctors have already taken place, since Jurgen has got involved. We did have writable MIB IESG statement (https://www.ietf.org/about

Re: [OPSAWG] New Version Notification for draft-dbwb-opsawg-sap-00.txt

>>; Oscar Gonzalez de Dios mailto:oscar.gonzalezded...@telefonica.com>>; Oscar de Dios mailto:oscar.gonzalezded...@telefonica.com>>; Qin WU mailto:bill...@huawei.com>>; Qin Wu mailto:bill...@huawei.com>>; Samier Barguil mailto:samier.barguilgiraldo@telefonica.com>>;

Re: [OPSAWG] 🔔 WG Adoption Call for draft-gharris-opsawg-pcap-02

-邮件原件- 发件人: Carsten Bormann [mailto:c...@tzi.org] 发送时间: 2021年10月26日 15:18 收件人: Guy Harris 抄送: Qin Wu ; opsawg@ietf.org 主题: Re: [OPSAWG] 🔔 WG Adoption Call for draft-gharris-opsawg-pcap-02 On 26. Oct 2021, at 09:00, Guy Harris wrote: > > I would vote for "both should point

Re: [OPSAWG] 🔔 WG Adoption Call for draft-gharris-opsawg-pcap-02

-邮件原件- 发件人: Carsten Bormann [mailto:c...@tzi.org] 发送时间: 2021年10月26日 14:35 收件人: Qin Wu 抄送: opsawg@ietf.org 主题: Re: [OPSAWG] 🔔 WG Adoption Call for draft-gharris-opsawg-pcap-02 Hi Qin, On 26. Oct 2021, at 03:43, Qin Wu wrote: > > I am not against this draft. I am just thinking w

Re: [OPSAWG] 🔔 WG Adoption Call for draft-gharris-opsawg-pcap-02

/), bisdocument can go through WG submission process, if my understanding is correct. -Qin -邮件原件- 发件人: Michael Richardson [mailto:mcr+i...@sandelman.ca] 发送时间: 2021年10月26日 0:28 收件人: opsawg@ietf.org 抄送: l...@cisco.com; Toerless Eckert ; Qin Wu ; Carsten Bormann ; j.schoenwael...@jacobs

Re: [OPSAWG] Martin Duke's Discuss on draft-ietf-opsawg-l3sm-l3nm-11: (with DISCUSS)

..@hs-esslingen.de] 发送时间: 2021年9月23日 17:42 收件人: Qin Wu ; mohamed.boucad...@orange.com; Martin Duke ; The IESG 抄送: draft-ietf-opsawg-l3sm-l...@ietf.org; opsawg@ietf.org; opsawg-cha...@ietf.org 主题: RE: Martin Duke's Discuss on draft-ietf-opsawg-l3sm-l3nm-11: (with DISCUSS) Hi Qin, I believe t

Re: [OPSAWG] Martin Duke's Discuss on draft-ietf-opsawg-l3sm-l3nm-11: (with DISCUSS)

Hi, Michael, Med and all: I tend to agree with Med we should have a clear distinction between device level configuration and network level abstraction. Device level configuration will provide complete set of TCP AO properties configuration to make TCP AO functionality work while network level abs

Re: [OPSAWG] IPR Poll: draft-ietf-opsawg-l2nm

No, I am not aware of any IPR that applies to draft-ietf-opsawg-l2nm. -Qin (as contributor) -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2021年9月17日 0:03 收件人: opsawg@ietf.org 主题: [OPSAWG] IPR Poll: draft-ietf-opsawg-l2nm Working Group, Authors, As a pa

[OPSAWG] Opsdir last call review of draft-ietf-opsawg-l3sm-l3nm-10

Reviewer: Qin Wu Review result: Has Nits I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Com

Re: [OPSAWG] WG Last call for draft-ietf-opsawg-ipfix-mpls-sr-label-type-01

Yes, thanks for addressing my comments. -Qin 发件人: thomas.g...@swisscom.com [mailto:thomas.g...@swisscom.com] 发送时间: 2021年6月18日 23:58 收件人: Qin Wu ; Tianran Zhou ; opsawg@ietf.org 主题: RE: WG Last call for draft-ietf-opsawg-ipfix-mpls-sr-label-type-01 Hi Qin, That would be for TB1, TB2 and TB3 as

Re: [OPSAWG] WG Last call for draft-ietf-opsawg-ipfix-mpls-sr-label-type-01

发件人: thomas.g...@swisscom.com [mailto:thomas.g...@swisscom.com] 发送时间: 2021年6月15日 12:31 收件人: Qin Wu ; Tianran Zhou ; opsawg@ietf.org 主题: RE: WG Last call for draft-ietf-opsawg-ipfix-mpls-sr-label-type-01 Hi Qin, Thanks for the feedback. I will include the comments in the next version. Regarding

Re: [OPSAWG] WG Last call for draft-ietf-opsawg-ipfix-mpls-sr-label-type-01

Support, a few comments for clarity: General comment: 1.Have we considered to request early IANA allocation? 2. Section 2 s/ dynamic BGP labels according to RFC8277 [RFC8277]/ dynamic BGP labels [RFC8277] s/ BGP Prefix-SID according to RFC8669 [RFC8669]/ BGP Prefix-SID [RFC8669] s/ in conte

Re: [OPSAWG] IPR CALL: draft-ietf-opsawg-l3sm-l3nm

Chairs： I am not aware of any IPR that applies to this draft. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2021年3月22日 21:34 收件人: opsawg@ietf.org 主题: [OPSAWG] IPR CALL: draft-ietf-opsawg-l3sm-l3nm Authors, contributors, and WG members, as we are in

Re: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common

Chairs: I am not aware of any IPR that applies to this draft. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2021年3月22日 21:33 收件人: opsawg@ietf.org 主题: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common Authors, contributors, and WG members, as we are i

[OPSAWG] OpenMetric work

Richard: Thank for bringing up this work, it is interesting. Try to get the whole picture for this open metric work. Can you clarify how this open metric work is related meter API, trace API, context API in the opentelemetry. Also how this open metric is related to Distributed Trace work in W3C?

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

Tiru: I am wondering whether section 4.2 “Encrypted DNS” should reference 7 of draft-richardson-opsawg-mud-iot-dns-considerations-03 for DNS recommendation. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 tirumal reddy 发送时间: 2021年1月18日 12:51 收件人: opsawg 主题: Re: [OPSAWG] I-D Action: draft-ie

Re: [OPSAWG] 🔔 WG Adoption Call on draft-lear-opsawg-sbom-access-00

Hi, authors of draft-lear-opsawg-sbom-access-00: What is key difference between sbom-url and local-uri? I feel a little bit confused when reading the definition of sbom-url and local-uri Based on the definition of local-url, " case local-uri { description "The choice of s

Re: [OPSAWG] 🔔 WG Adoption Call on draft-richardson-opsawg-mud-iot-dns-considerations-03

Support adoption of this document, agree with Eliot. A few quick comments: 1. I want to make sure these recommendation and guidelines of using DNS are not only applicable to home network but also enterprise network as well. 2. Section 4.2 lack examples of non-deterministic CDN content. 3. Section

Re: [OPSAWG] 🔔 WG adoption call on draft-richardson-opsawg-mud-acceptable-urls-03

Hi, authors of draft-richardson-opsawg-mud-acceptable-urls: I have seen most of comments I raised earlier on have been addressed, e.g., 1. provide recommendation to the implementers or developer on when they choose MUD URL updating and when they choose MUD file updating? 2.Clarify the difference b

[OPSAWG] EVPN support in L2NM

Hi, all: We discussed EVPN support for L2NM in past L3NM Design team meetings and tried to identify what are missing parameters for EVPN support in L2NM. First, EVPN have many different flavors, e.g., O MPLS EVPN (RFC7432) o VXLAN EVPN (RFC8365) o PBB EVPN (RFC7623) o VPWs EVPN (RFC8214) Th

Re: [OPSAWG] Feedback on draft-www-opsawg-yang-vpn-service-pm

Good catch, Greg, the difference is the granularity of the percentile, supporting five 9s seems reasonable to me. I am happy to align with the percentile defined in STAMP YANG model. -Qin 发件人: gregory.mir...@ztetx.com [mailto:gregory.mir...@ztetx.com] 发送时间: 2020年12月15日 4:32 收件人: Qin Wu 抄送

Re: [OPSAWG] Feedback on draft-www-opsawg-yang-vpn-service-pm

Thanks Med for clarification, we discussed the downside of using average before, i.e., hide outlier, which is more appropriate for relative even distribution. That is why we introduce percentiles. 3 percentiles value can be 50 percentile,75 percentile,95 percentile which is configured by setting

Re: [OPSAWG] New Version Notification for draft-tuexen-opsawg-pcapng-02.txt

Hi, two Michaels: Can you clarify what functionalities is missed for more modern applications? Since it is enhancement to libpcap, do you expect all the future packet capture tools support the format defined in this draft? -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Micha

Re: [OPSAWG] WGLC for draft-ietf-opsawg-ntf [CORRECT]

Support for publication. A quick comment, regarding event triggered data, I think FSM is just one example of how event is modelled, but not the only way. Suggest to make this clear in the text. -Qin From: Tianran Zhou mailto:zhoutian...@huawei.com>> Sent: Thursday, September 24, 2020 08:39 To: ops

Re: [OPSAWG] Last Call: (A Framework for Automating Service and Network Management with YANG) to Informational RFC

Hi, -邮件原件- 发件人: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com] 发送时间: 2020年9月30日 3:55 收件人: mohamed.boucad...@orange.com; last-c...@ietf.org 抄送: draft-ietf-opsawg-model-automation-framework@ietf.org; opsawg@ietf.org 主题: Re: Last Call: (A Framework for Automating Service and Net

Re: [OPSAWG] AD review for draft-ietf-opsawg-model-automation-framework-04

Thanks Rob for quick checking. Talking with Med, we have agreed to remove that sentence. The change is reflected in v-05 See v-05 https://tools.ietf.org/html/draft-ietf-opsawg-model-automation-framework-05 the diff is: https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-ietf-opsawg-model-a

Re: [OPSAWG] Error discovered during AUTH48 processing of draft-ietf-opsawg-tacacs

I think the updated text removes confusion in the original proposal.. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Warren Kumari 发送时间: 2020年9月15日 4:13 收件人: opsawg ; ops-...@ietf.org; OpsAWG-Chairs 主题: [OPSAWG] Error discovered during AUTH48 processing of draft-ietf-opsawg

Re: [OPSAWG] Henk Birkholz as third OPSAWG chair

Congratulation Henk, welcome. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Rob Wilton (rwilton) 发送时间: 2020年9月12日 0:36 收件人: opsawg 抄送: Henk Birkholz 主题: [OPSAWG] Henk Birkholz as third OPSAWG chair Dear all, I am happy to announce that Henk Birkholz has agreed to serve as

Re: [OPSAWG] CALL FOR ADOPTION: draft-reddy-opsawg-mud-tls

Support adoption of this work. I have a few comments which I would like authors to consider: 1. Module name I strange, should not include surname and WG name in the standard module name, suggest to change it from reddy-opsawg-mud-tls-profile into ietf-mud-tls-profile 2. Can we still see this modu

[OPSAWG] RE CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common

Support, it is important to decouple network layer from service layer and avoid layer violation. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2020年8月13日 20:49 收件人: opsawg 主题: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common Hello, WG mem

Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-ipfix-mpls-sr-label-type

Support, I think this draft fill the missing piece for IPFIX to support SR, it will be useful for this draft to cover SRv6 data plane as well. -Qin -邮件原件- 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2020年8月13日 20:41 收件人: opsawg 主题: [OPSAWG] CALL FOR ADOPTIO

Re: [OPSAWG] L3VPN BGP Threshold and BGP Session parameters (https://github.com/IETF-OPSAWG-WG/l3nm/issues/34 and https://github.com/IETF-OPSAWG-WG/l3nm/issues/35)

Yeah, I think it makes sense to add such knob to provide fine granularity control. Let me know if you have proposal for this. -Qin 发件人: Roque Gagliano (rogaglia) [mailto:rogag...@cisco.com] 发送时间: 2020年7月24日 17:07 收件人: Qin Wu ; opsawg 主题: Re: [OPSAWG] L3VPN BGP Threshold and BGP Session

[OPSAWG] L3VPN BGP Threshold and BGP Session parameters (https://github.com/IETF-OPSAWG-WG/l3nm/issues/34 and https://github.com/IETF-OPSAWG-WG/l3nm/issues/35)

Hi, All: We have been discussion additional BGP parameters such as L3VPN BGP threshold and BGP session parameters, which is corresponding to issue ticket #34 and #35 on L3NM model, And would like to have the following proposed change to L3NM model to resolve pending issue tickets: OLD TEXT: "

Re: [OPSAWG] CALL FOR ADOPTION: draft-barguil-opsawg-l2sm-l2nm

Joe: I support adoption, I think the model proposed in this draft is a good starting point. We need to see how this model can be extended to support various different flavor of L2VPN, EVPN is one of important flavor. I also believe factoring out common model is a good approach. Reviewing the lat

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions

addition, I have been aware, RT auto assign also need to be fixed in L3NM current version. It looks this issue has been slipped out. -Qin 发件人: Roque Gagliano (rogaglia) [mailto:rogag...@cisco.com] 发送时间: 2020年6月2日 3:14 收件人: Qin Wu ; Oscar González de Dios ; opsawg 主题: Re: [OPSAWG] Minutes of

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

Good, thank for clarification. -Qin 发件人: mohamed.boucad...@orange.com [mailto:mohamed.boucad...@orange.com] 发送时间: 2020年6月4日 15:31 收件人: Qin Wu ; Joe Clarke (jclarke) ; SAMIER BARGUIL GIRALDO 抄送: OPSAWG@ietf.org 主题: RE: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020) Hi Qin, I

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

And on that topic, your operational-type is used for both admin and oper status. It seems to me that admin status would either be up or down (or maybe something like testing such as in the ietf-interfaces module). The oper-status may be richer. And in your grouping for service-status, you hav

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

...@orange.com [mailto:mohamed.boucad...@orange.com] 发送时间: 2020年6月4日 13:42 收件人: Qin Wu ; Joe Clarke (jclarke) ; SAMIER BARGUIL GIRALDO 抄送: OPSAWG@ietf.org 主题: RE: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020) Hi Qin, all, The idea is to have a common module listing items that can be

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

published types modules as much as possible, make sure we will not reinvent any new wheels that have been defined somewhere else. -Qin 发件人: Zhenghaomian 发送时间: 2020年6月4日 14:16 收件人: Qin Wu ; Joe Clarke (jclarke) ; SAMIER BARGUIL GIRALDO 抄送: OPSAWG@ietf.org 主题: Re: [OPSAWG] Minutes of L3NM/L2NM module

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Joe Clarke (jclarke) 发送时间: 2020年6月4日 0:16 收件人: SAMIER BARGUIL GIRALDO 抄送: OPSAWG@ietf.org 主题: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020) The module is available in the following PULL REQUEST: https://github.com/IETF-OPSAW

Re: [OPSAWG] Minutes of L3NM/L2NM module discussions

scussions Dear OPSAWG colleagues, Thanks for participating in the call today. Please find bellow the minutes: L3NM and L2NM module discussions * Date: 21-May-2020 Participants - Oscar Gonzalez de Dios (Telefonica) - Samier Barguil (Telefonica) - Anton Snizar (Sedona) - Daniel K

Re: [OPSAWG] WG LC: draft-ietf-opsawg-model-automation-framework-03

Speak as author of this document, support for publication. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Tianran Zhou 发送时间: 2020年6月1日 10:25 收件人: opsawg@ietf.org 抄送: OpsAWG-Chairs 主题: [OPSAWG] WG LC: draft-ietf-opsawg-model-automation-framework-03 Hi WG, The authors requested the WG la

Re: [OPSAWG] IPR poll for draft-ietf-opsawg-model-automation-framework-03

I’m not aware of any IPR that applies to this draft. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Tianran Zhou 发送时间: 2020年6月1日 10:37 收件人: opsawg@ietf.org 抄送: OpsAWG-Chairs 主题: [OPSAWG] IPR poll for draft-ietf-opsawg-model-automation-framework-03 Working Group, Authors, As a part of t

Re: [OPSAWG] L2NM: Layer 2 VPN Network Model: Request for Feedback and Review

+1，support it. -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 mohamed.boucad...@orange.com 发送时间: 2020年4月2日 20:41 收件人: Oscar González de Dios ; opsawg@ietf.org 主题: Re: [OPSAWG] L2NM: Layer 2 VPN Network Model: Request for Feedback and Review Hi Oscar, I agree this is an important piece of

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-model-automation-framework-01.txt

: A Framework for Automating Service and Network Management with YANG Authors : Qin Wu Mohamed Boucadair Diego R. Lopez Chongfeng Xie Liang Geng Filename

Re: [OPSAWG] IETF 106 Discussion about draft-gray-sampled-streaming - room moved

Becos it is running out of time in the session, I haven't got time to comment on this, Good topic, there are two relevant drafts that are proposed recently in netmod, netconf, which focus on self describing data format and advertisement mechanism. https://tools.ietf.org/html/draft-tao-netmod-yan

[OPSAWG] IETF YANG Side meeting on YANG Use Cases

YANG model interact with other model or Mechanisms. How IETF YANG are put together to deliver service. The meeting time is: Wednesday afternoon 4:30~5:30 The meeting room is : Bras Basah Feel free to join the discussion. Thanks! -Qin Wu ___ OPSAWG mailing

Re: [OPSAWG] conclusion//RE: WG adoption call for draft-wu-model-driven-management-virtualization-07

Tom: -邮件原件- 发件人: tom petch [mailto:ie...@btconnect.com] 发送时间: 2019年11月14日 0:38 收件人: Qin Wu ; Brian E Carpenter ; Tianran Zhou ; opsawg@ietf.org 抄送: draft-wu-model-driven-management-virtualization.auth...@ietf.org; opsawg-cha...@ietf.org 主题: Re: [OPSAWG] conclusion//RE: WG adoption call

Re: [OPSAWG] conclusion//RE: WG adoption call for draft-wu-model-driven-management-virtualization-07

How about draft-ietf-opsawg-model-automation-framework if we agree to change the name?:-) -Qin -邮件原件- 发件人: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com] 发送时间: 2019年11月13日 9:56 收件人: Tianran Zhou ; Qin Wu ; tom petch ; opsawg@ietf.org 抄送: draft-wu-model-driven-management

Re: [OPSAWG] conclusion//RE: WG adoption call for draft-wu-model-driven-management-virtualization-07

Hi, Tom and Tianran: It looks the new proposed draft name more reflects what it is, but referencing to IETF standards process, the draft name change rule is nothing more than one mentioned by Tom. I knew in the history, there was some exception about draft name changes, e.g., change draft-fieldi

Re: [OPSAWG] WG adoption call for draft-wu-model-driven-management-virtualization-07

-邮件原件- 发件人: Joe Clarke (jclarke) [mailto:jcla...@cisco.com] 发送时间: 2019年10月31日 1:11 收件人: Tianran Zhou 抄送: opsawg@ietf.org; opsawg-cha...@ietf.org; draft-wu-model-driven-management-virtualization.auth...@ietf.org 主题: Re: WG adoption call for draft-wu-model-driven-management-virtualization-

Re: [OPSAWG] WG adoption call for draft-wu-model-driven-management-virtualization-07

Thanks Aijun. One size can not fit all, similarly one model can not fit all. In multi-layer, multi-domain scenario, you do need network layer model to establish the mapping between service request and underlying network resource. In addition, network topology model and TE tunnel are also seen as

Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm

2.Allow several BGP sessions under the same Network Access. To support several Routing Protocols sessions under the same Network Access we have changed the Key to have an ID to allow several protocols under the same Network Access: | |+--rw routing-protocol* [id]

  1   2   >