Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05

2020-12-06 Thread wangzitao
Support +1

B.R.
Michael

发件人: BESS [mailto:bess-boun...@ietf.org] 代表 Wanghaibo (Rainsword)
发送时间: 2020年12月5日 9:12
收件人: Bocci, Matthew (Nokia - GB) ; 
draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org
主题: Re: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-srv6-services-05

Hi Matthew & Stephane,

Support for publication.

Thanks,
Haibo


From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - 
GB)
Sent: Tuesday, December 1, 2020 1:16 AM
To: 
draft-ietf-bess-srv6-servi...@ietf.org;
 bess@ietf.org
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-srv6-services-05

This email starts a two-week working group last call for 
draft-ietf-bess-srv6-services-05 [1]

Please review the draft and send any comments to the BESS list. Also, please 
indicate if you support publishing the draft as a standards track RFC.

This poll runs until Monday 14th December 2020.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.
There is currently one IPR disclosure.

In addition, we are polling for knowledge of implementations of this draft, per 
the BESS policy in [2].

Thank you,
Matthew & Stephane


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] New Version Notification for draft-www-bess-yang-vpn-service-pm-04.txt

2019-11-01 Thread wangzitao
Dear WG,

We have updated draft-www-bess-yang-vpn-service-pm to allow monitor network 
performance of different tunnel technology type, more details please review the 
draft:
https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm-04
Your comments are suggestions are welcome.

Best Regards!
-Michael

-邮件原件-
发件人: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
发送时间: 2019年11月1日 15:39
收件人: wangzitao ; Qin Wu ; Chang Liu 
; wangzitao ; Honglei Xu 
; Roni Even (A) ; Bin Wen 
; Change Liu ; Qin Wu 

主题: New Version Notification for draft-www-bess-yang-vpn-service-pm-04.txt


A new version of I-D, draft-www-bess-yang-vpn-service-pm-04.txt
has been successfully submitted by Michael Wang and posted to the IETF 
repository.

Name:   draft-www-bess-yang-vpn-service-pm
Revision:   04
Title:  A YANG Model for Network and VPN Service Performance Monitoring
Document date:  2019-10-31
Group:  Individual Submission
Pages:  24
URL:
https://www.ietf.org/internet-drafts/draft-www-bess-yang-vpn-service-pm-04.txt
Status: 
https://datatracker.ietf.org/doc/draft-www-bess-yang-vpn-service-pm/
Htmlized:   
https://tools.ietf.org/html/draft-www-bess-yang-vpn-service-pm-04
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-www-bess-yang-vpn-service-pm-04

Abstract:
   The data model defined in [RFC8345] introduces vertical layering
   relationships between networks that can be augmented to cover
   network/service topologies.  This document defines a YANG model for
   both Network Performance Monitoring and VPN Service Performance
   Monitoring that can be used to monitor and manage network performance
   on the topology at higher layer or the service topology between VPN
   sites.  This model is an augmentation to the network topology YANG
   data model defined in [RFC8345].


  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] Some comments on draft-ietf-bess-l3vpn-yang-04

2019-07-18 Thread wangzitao
Dear Authors,

I have reviewed the draft-ietf-bess-l3vpn-yang-04. And I have the following 
comment:
# First of all, this draft has expired, and L3VPN YANG is a very useful model, 
so please update it as soon as possible.
And for the YANG model,
# Is it necessary to define two branches to distinguish IPv4 and IPv6? Why not 
define a type to distinguish the IPv4 and IPv6?
# Why does the export-to-global not refers to routing-policy?
# Is it necessary to configure routing-table-limit both in network-instance and 
bgp:ipv4-unicast?
# Why the instance attribute within import-from-global does not use the leafref 
to refer to network-instance?

Best Regards!
-Michael


___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] Some comments on draft-ietf-bess-l2vpn-yang-10

2019-07-18 Thread wangzitao
Dear Authors,

I have reviewed this version. And I have the following comment:

# L2VPN base mode has already defined AC and PW two common attributes, 
redundancy-grp is introduced as combination of AC attribute and PW attribute, 
not sure the redundancy-grp is a common attribute for L2VPN.
I would like to argue why not define redundancy-group in the extension model or 
in a separate draft.

# I see pseudowires in ietf-pseudowires have already defined common attributes 
such as MTU, cw-negotiation and tunnel-policy, template within pseudowires 
reference pw-template and pw-template also defines duplicated common attribute 
such as MTU, cw-negotiation and tunnel-policy.
So I think template parameter and pw-template should be removed.

# Not sure group-id ,icb, generalized are common attribute for configured-pw 
case. Suggest to simplify configured-pw attributes and keep the minimum set of 
attributes common to all vendor's implementation.

# The definition of discover-type and signaling-type are very similar. What are 
their differences? Can we keep only one?

# vpws-constraints is an empty container, it seems just like a placeholder, 
suggest to delete it.

# Pbb is an ieee802.1 specific technology, suggest to remove it from base model 
and move it to technology specific model.

Best Regards!
-Michael
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] New Version Notification for draft-www-bess-yang-vpn-service-pm-03.txt

2019-07-08 Thread wangzitao
Dear WG,

This new version changes the text around section 6.1 based on comments from 
IETF 104, and updates the examples in section 7 and 8.
Please review it, suggestions and comments are very welcome! 

Best Regards!
-Michael

-邮件原件-
发件人: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
发送时间: 2019年7月8日 16:47
收件人: wangzitao ; Chang Liu ; 
wangzitao ; Roni Even (A) ; Bin Wen 
; Change Liu ; Qin Wu 

主题: New Version Notification for draft-www-bess-yang-vpn-service-pm-03.txt


A new version of I-D, draft-www-bess-yang-vpn-service-pm-03.txt
has been successfully submitted by Michael Wang and posted to the IETF 
repository.

Name:   draft-www-bess-yang-vpn-service-pm
Revision:   03
Title:  A YANG Model for Network and VPN Service Performance Monitoring
Document date:  2019-07-05
Group:  Individual Submission
Pages:  24
URL:
https://www.ietf.org/internet-drafts/draft-www-bess-yang-vpn-service-pm-03.txt
Status: 
https://datatracker.ietf.org/doc/draft-www-bess-yang-vpn-service-pm/
Htmlized:   
https://tools.ietf.org/html/draft-www-bess-yang-vpn-service-pm-03
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-www-bess-yang-vpn-service-pm-03

Abstract:
   The data model defined in [RFC8345] introduces vertical layering
   relationships between networks that can be augmented to cover
   network/service topologies.  This document defines a YANG model for
   Network and VPN Service Performance Monitoring that can be used to
   monitor and manage network performance on the topology at different
   layer or the overlay topology between VPN sites.  This model is an
   augmentation to the network topology YANG data model defined in
   [RFC8345].


  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] review of draft-www-bess-yang-vpn-service-pm

2019-06-17 Thread wangzitao
Hi Honglei,

Thanks for the review comments. Please find my reply at [MW].

Best Regards!
-Michael

发件人: BESS [mailto:bess-boun...@ietf.org] 代表 Xu honglei
发送时间: 2019年6月17日 16:27
收件人: bess@ietf.org
主题: [bess] review of draft-www-bess-yang-vpn-service-pm

As abstract said:
“
This document defines a YANG model for
   Network and VPN Service Performance Monitoring that can be used to
   monitor and manage network performance on the topology at different
   layer or the overlay topology between VPN sites.
“
I believe YANG model described in this draft can be used to monitor network 
performance or can be used to monitor VPN performance.
  This two performance monitoring are two separate functionalities.
[MW]: Agree.

  Section 4 provide two layered topology which can be used to monitor network 
performance in the overlay topology and monitor in the service topology 
Separately which is good.
[MW]: Thanks.

  Section 6.1 describe network level parameter such as vpn topology, svc topo 
type, I think these network level parameters are not needed when monitoring 
network performance.
[MW]: The section 6.1 introduce how to augment the ietf-network model to 
support VPN performance monitoring.
For monitoring network performance, IMHO,  the section 6.1 can be ignored since 
the network-type and l3-topology-attributes have been defined in RFC8345 and 
RFC8346.

Please make this clear in the text.
[MW]: I’d like to add some text to introduce how to support network performance 
monitoring.


H.Xu
+86-010-5090-2313
+86-133-0116-8970
xuhl@chinatelecom.cn
--
China Telecom Corporation Limited Beijing Research Institute
Southern Zone of Future Science City,
Beiqijia Town, Changping District,
Beijing, China
102209


___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] some comments on evpn yang data model

2019-06-10 Thread wangzitao
Dear Authors,

I have read the -07 version draft. And there are some comments.

#1 ietf-pseudowires model expired.
I ran this model on yangcatalog but received an unexpected error:
ietf-ethernet-segm...@2019-03-09.yang:21: error: module "ietf-pseudowires" not 
found in search path
It seems that the "draft-ietf-bess-l2vpn-yang" which define the 
"ietf-pseudowires" expired. I noticed that some authors are also the authors of 
"draft-ietf-bess-l2vpn-yang" so please revive the l2vpn yang model draft.

#2 The tree structure does not match the code. When I review the tree structure 
blocks, I wonder why there is only one route-target leaf under the "rd-rt" 
list. However, when I review the yang codes, this list is defined as:
   leaf route-distinguisher {
 type rt-types:route-distinguisher;
 description "Route distinguisher";
   }
   uses rt-types:vpn-route-targets;
   description "A list of route distinguishers and " +
   "corresponding VPN route targets";
 }
The vpn-route-targets grouping defined in rt-types contains a vpn-target list. 
It seems that the schema tree is not updated synchronously.

#3 Many lists are lack of key nodes, for example ethernet-auto-discovery-route 
list, mac-ip-advertisement-route list, inclusive-multicast-ethernet-tag-route 
list, etc.
How do I retrieve these status data without a key value?

Best Regards!
-Michael
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] New Version Notification for draft-www-bess-yang-vpn-service-pm-02.txt

2019-03-08 Thread wangzitao
Dear WG,

We upload the 02 version of draft-www-bess-yang-vpn-service-pm to address some 
comments since last meeting.
https://tools.ietf.org/html/draft-www-bess-yang-vpn-service-pm-02
Changes in this version:
- Polish the document to improve the readability;
- Add termination point related attributes to report the interface level 
statistic parameters;
- New co-author (Chang Liu, China Unicom).

Please review the document, comments and suggestions are welcome!

Best Regards!
-Michael


The changes include:
-邮件原件-
发件人: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
发送时间: 2019年3月8日 17:46
收件人: wangzitao ; Chang Liu ; 
wangzitao ; Roni Even (A) ; Bin Wen 
; Change Liu ; Qin Wu 

主题: New Version Notification for draft-www-bess-yang-vpn-service-pm-02.txt


A new version of I-D, draft-www-bess-yang-vpn-service-pm-02.txt
has been successfully submitted by Michael Wang and posted to the IETF 
repository.

Name:   draft-www-bess-yang-vpn-service-pm
Revision:   02
Title:  A YANG Model for Network and VPN Service Performance Monitoring
Document date:  2019-03-08
Group:  Individual Submission
Pages:  24
URL:
https://www.ietf.org/internet-drafts/draft-www-bess-yang-vpn-service-pm-02.txt
Status: 
https://datatracker.ietf.org/doc/draft-www-bess-yang-vpn-service-pm/
Htmlized:   
https://tools.ietf.org/html/draft-www-bess-yang-vpn-service-pm-02
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-www-bess-yang-vpn-service-pm-02

Abstract:
   The data model defined in [RFC8345] introduces vertical layering
   relationships between networks that can be augmented to cover
   network/service topologies.  This document defines a YANG model for
   Network and VPN Service Performance Monitoring that can be used to
   monitor and manage network performance on the topology at different
   layer or the overlay topology between VPN sites.  This model is an
   augmentation to the network topology YANG data model defined in
   [RFC8345].


  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess