[OPSAWG] IETF DLMO draft side-meeting

2022-01-25 Thread Marisol Palmero Amador (mpalmero)
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.



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
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


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg


Re: [OPSAWG] I-D Action: draft-ietf-opsawg-yang-vpn-service-pm-02.txt

2022-01-25 Thread tom petch
From: Wubo (lana) 
Sent: 25 January 2022 13:16

Hi Tom,

Thanks for the review and we will correct these issues in the next version. 
Please see inline.

< inline twice>

Best regards,
Bo

> -邮件原件-
> 发件人: tom petch [mailto:ie...@btconnect.com]
> 发送时间: 2022年1月21日 20:30
>
> From: OPSAWG  on behalf of Wubo (lana)
> 
> Sent: 20 January 2022 03:24
>
> Hi WG,
>
> Many thanks to the WG for the discussion and valuable comments.
>
> This update mainly reflects the discussion decision of the 112 meeting and 
> also
> the comments of Adrian and Greg on the mailing list.
>
> 
> Some possible glitches for you.
>
> Some of the lines in the YANG module are too long (they were ok in -01)
[Bo Wu] Thanks for catching this, will fix in the next revision.
>
> You use  to refer to two different I-D (this was ok in -01)
[Bo Wu] Thanks. Fixed.
>
> Abbreviations need expanding, perhaps in Terminology e.g. VPLS OWAMP
> L3VPN
[Bo Wu] OK. Thanks.
>
> I want references in the YANG module for OWAMP IPDV P
[Bo Wu] OK.
>
> ITU-T Y.1731 would benefit from a title and needs adding to the I-D References
[Bo Wu] OK.
>
> five fraction digits for a percentile?  I note that the defaults have only two
> digits
[Bo Wu] Fixed.
>
> /http:/https:/
> TLP is out of date
[Bo Wu] Fixed.
>
> percentile definition seems not quite right.  You are using a percentage here
> but there is no requirement to do so - it can be an integer count or any other
> measurement of a proportion
[Bo Wu] We provide two options here, and some providers think percentile is 
also useful. I'm not sure the issue. Could you elaborate a little bit?


Percentile is fine as a way of characterising  a distribution with a single 
value.  My comment is that for any percentile, be it 50-percentile, 
95-percentile or whatever, then there is a value to go with that and that value 
can be anything that is a value - integer, percentage etc.  I think that the 
description here wants it to be a percentage which I think too limiting.

>
[Bo Wu] Fixed.
> 'middle-delay' I think confusing; sounds too much like it is the median or 
> mode;
> perhaps medium?
[Bo Wu] Agree. rfc3393 uses median to indicate 50th percentile. so we change it 
to "median-delay"?


Well no, it is median only when it is a 50-percentile which is only the default 
here and if the user chose 90 instead, wanting the three percentiles to be 60, 
90, 95, then I think median is misleading.

And RFC3393 says (along with defining ipdv:-) that the 50-percentile is the 
median which is correct.  Here you are defining low, something else, high and 
when something else is not 50, then it is not the median.  I am struggling for 
a word that sits between low and high that does not have connotations of being 
the middle!  intermediate?

Tom Petch
>
> time when statistics are collected; start time, end time, duration of 
> interval?
[Bo Wu] OK, we will change "reference-time" to "start time" and "end time", but 
we like to keep " measurement-interval".
>
> subnetwork (broadcast, multicast) I find unclear - sub which layer of our 
> current
> network many-layered stacks.
[Bo Wu] OK, we directly use IETF interface YANG description in this version. We 
will make this clearer.
>
> Tom Petch
>
> The detailed changes are the following:
> 1. Adds modeling considerations to the introduction 2. Adds a reference to
> draft-ietf-netmod-node-tags 3. YANG: Replaces the type of "pm-source”:
> string' -> 'identity'
> 4. YANG: Adds "vpn-one-way-pm-statistics* [class-id]" to collect class-based
> VPN underlay tunnel statistics 5. YANG: Adds “vpn-network-access” specific
> counters under " termination-point"
> 6. YANG: Highlights the unidirectional link metrics with "
> one-way-pm-statistics"
> 7. Fixed a lot of editorial issues
>
> Here is the diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-yang-vpn-service-pm-02.
>
> Thanks,
> Bo
>
> > -邮件原件-
> > 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表
> > internet-dra...@ietf.org
> > 发送时间: 2022年1月20日 10:50
> > 收件人: i-d-annou...@ietf.org
> > 抄送: opsawg@ietf.org
> > 主题: [OPSAWG] I-D Action: draft-ietf-opsawg-yang-vpn-service-pm-02.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> > This draft is a work item of the Operations and Management Area
> > Working Group WG of the IETF.
> >
> > Title   : A YANG Model for Network and VPN Service
> > Performance Monitoring
> > Authors : Bo Wu
> >   Qin Wu
> >   Mohamed Boucadair
> >   Oscar Gonzalez de Dios
> >   Bin Wen
> >   Filename: draft-ietf-opsawg-yang-vpn-service-pm-02.txt
> >   Pages   : 35
> >   Date: 2022-01-19
> >
> > Ab
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg


Re: [OPSAWG] I-D Action: draft-ietf-opsawg-yang-vpn-service-pm-02.txt

2022-01-25 Thread Wubo (lana)
Hi Tom,

Thanks for the review and we will correct these issues in the next version. 
Please see inline.

Best regards,
Bo

> -邮件原件-
> 发件人: tom petch [mailto:ie...@btconnect.com]
> 发送时间: 2022年1月21日 20:30
> 收件人: Wubo (lana) ;
> opsawg@ietf.org; draft-ietf-opsawg-yang-vpn-service...@ietf.org
> 主题: Re: [OPSAWG] I-D Action: draft-ietf-opsawg-yang-vpn-service-pm-02.txt
> 
> From: OPSAWG  on behalf of Wubo (lana)
> 
> Sent: 20 January 2022 03:24
> 
> 
> Hi WG,
> 
> Many thanks to the WG for the discussion and valuable comments.
> 
> This update mainly reflects the discussion decision of the 112 meeting and 
> also
> the comments of Adrian and Greg on the mailing list.
> 
> 
> Some possible glitches for you.
> 
> Some of the lines in the YANG module are too long (they were ok in -01)
[Bo Wu] Thanks for catching this, will fix in the next revision.
> 
> You use  to refer to two different I-D (this was ok in -01)
[Bo Wu] Thanks. Fixed.
> 
> Abbreviations need expanding, perhaps in Terminology e.g. VPLS OWAMP
> L3VPN
[Bo Wu] OK. Thanks.
> 
> I want references in the YANG module for OWAMP IPDV P
[Bo Wu] OK.
> 
> ITU-T Y.1731 would benefit from a title and needs adding to the I-D References
[Bo Wu] OK.
> 
> five fraction digits for a percentile?  I note that the defaults have only two
> digits
[Bo Wu] Fixed.
> 
> /http:/https:/
> TLP is out of date
[Bo Wu] Fixed.
> 
> percentile definition seems not quite right.  You are using a percentage here
> but there is no requirement to do so - it can be an integer count or any other
> measurement of a proportion
[Bo Wu] We provide two options here, and some providers think percentile is 
also useful. I'm not sure the issue. Could you elaborate a little bit?
> 
[Bo Wu] Fixed.
> 'middle-delay' I think confusing; sounds too much like it is the median or 
> mode;
> perhaps medium?
[Bo Wu] Agree. rfc3393 uses median to indicate 50th percentile. so we change it 
to "median-delay"?
> 
> time when statistics are collected; start time, end time, duration of 
> interval?
[Bo Wu] OK, we will change "reference-time" to "start time" and "end time", but 
we like to keep " measurement-interval".
> 
> subnetwork (broadcast, multicast) I find unclear - sub which layer of our 
> current
> network many-layered stacks.
[Bo Wu] OK, we directly use IETF interface YANG description in this version. We 
will make this clearer. 
> 
> Tom Petch
> 
> The detailed changes are the following:
> 1. Adds modeling considerations to the introduction 2. Adds a reference to
> draft-ietf-netmod-node-tags 3. YANG: Replaces the type of "pm-source”:
> string' -> 'identity'
> 4. YANG: Adds "vpn-one-way-pm-statistics* [class-id]" to collect class-based
> VPN underlay tunnel statistics 5. YANG: Adds “vpn-network-access” specific
> counters under " termination-point"
> 6. YANG: Highlights the unidirectional link metrics with "
> one-way-pm-statistics"
> 7. Fixed a lot of editorial issues
> 
> Here is the diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-yang-vpn-service-pm-02.
> 
> Thanks,
> Bo
> 
> > -邮件原件-
> > 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表
> > internet-dra...@ietf.org
> > 发送时间: 2022年1月20日 10:50
> > 收件人: i-d-annou...@ietf.org
> > 抄送: opsawg@ietf.org
> > 主题: [OPSAWG] I-D Action: draft-ietf-opsawg-yang-vpn-service-pm-02.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> > This draft is a work item of the Operations and Management Area
> > Working Group WG of the IETF.
> >
> > Title   : A YANG Model for Network and VPN Service
> > Performance Monitoring
> > Authors : Bo Wu
> >   Qin Wu
> >   Mohamed Boucadair
> >   Oscar Gonzalez de Dios
> >   Bin Wen
> >   Filename: draft-ietf-opsawg-yang-vpn-service-pm-02.txt
> >   Pages   : 35
> >   Date: 2022-01-19
> >
> > Ab
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg


Re: [OPSAWG] I-D Action: draft-ietf-opsawg-sap-00.txt

2022-01-25 Thread mohamed.boucadair
Hi all, 

This version does not address any of the comments raised during the call for 
adoption. We are planning to do so in the coming weeks.  

The comments raised by Benoît, Daniel, Dhruv, and Bo are recorded at: 
https://github.com/IETF-OPSAWG-WG/lxnm/issues?q=label%3AI-D.sap 

Please use that repo to flag your issues. Thanks.

Cheers,
Med

> -Message d'origine-
> De : I-D-Announce  De la part de
> internet-dra...@ietf.org
> Envoyé : mardi 25 janvier 2022 13:02
> À : i-d-annou...@ietf.org
> Cc : opsawg@ietf.org
> Objet : I-D Action: draft-ietf-opsawg-sap-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Operations and Management Area Working
> Group WG of the IETF.
> 
> Title   : A Network YANG Model for Service Attachment
> Points
> Authors : Oscar Gonzalez de Dios
>   Samier Barguil
>   Qin Wu
>   Mohamed Boucadair
>   Victor Lopez
>   Filename: draft-ietf-opsawg-sap-00.txt
>   Pages   : 21
>   Date: 2022-01-25
> 
> Abstract:
>This document defines a YANG data model for representing an abstract
>view of the provider network topology containing the points from
>which its services can be attached (e.g., basic connectivity, VPN,
>network slices).  The data model augments the 'ietf-network' data
>model by adding the concept of service attachment points (SAPs).  The
>service attachment points are the points to which network services
>(such as L3VPN or L2VPN) can be attached.  The customer endpoint of
>an attachment circuits are not covered in the SAP network topology.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-sap-00
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
> 
> 
> ___
> I-D-Announce mailing list
> i-d-annou...@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg


[OPSAWG] I-D Action: draft-ietf-opsawg-sap-00.txt

2022-01-25 Thread internet-drafts


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group 
WG of the IETF.

Title   : A Network YANG Model for Service Attachment Points
Authors : Oscar Gonzalez de Dios
  Samier Barguil
  Qin Wu
  Mohamed Boucadair
  Victor Lopez
Filename: draft-ietf-opsawg-sap-00.txt
Pages   : 21
Date: 2022-01-25

Abstract:
   This document defines a YANG data model for representing an abstract
   view of the provider network topology containing the points from
   which its services can be attached (e.g., basic connectivity, VPN,
   network slices).  The data model augments the 'ietf-network' data
   model by adding the concept of service attachment points (SAPs).  The
   service attachment points are the points to which network services
   (such as L3VPN or L2VPN) can be attached.  The customer endpoint of
   an attachment circuits are not covered in the SAP network topology.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-sap-00


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg