Re: [bess] Appointment of additional WG Chair

[liuyisong]

Congratulations Jeffrey!

 

Best Regards

Yisong

 

发件人: BESS  代表 Andrew Alston - IETF
发送时间: 2023年8月4日 10:45
收件人: bess@ietf.org
抄送: bess-cha...@ietf.org
主题: [bess] Appointment of additional WG Chair

 

Hi WG,

 

Following consultation with Matt and Stephane I have opted to appoint a
third chair to BESS to provide additional coverage considering the document
working load through the working group.

 

As such, I would like to welcome Jeffery Zhang as the third chair to BESS
and to thank him for his willingness to take up the position.  I believe
Jeffrey will be a solid addition to the team.

 

Thanks

 

Andrew Alston

Routing Area Director

 

 

Internal All Employees

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

Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 for IGMPv3

[Liuyisong]

Hi Mankamana,

 I think more specific description of IGMPv3 for Multicast Join/Leave Synch 
process should be better added in this draft
 Because IGMPv3 is very complicated, As we know, BLOCK, TO_IN, TO_EX can 
make some sources leave or even the group fitermode change.
But the route format definition make me confused about how to express 
TO_IN，TO_EX  by corresponding type 7 or 8 route.
 For example, is there Leave Synch Route(type 8) for the exclude mode 
source? If so , how can I understand the route?

Thanks
Yisong
.

From: Mankamana Mishra (mankamis) [mailto:manka...@cisco.com]
Sent: Saturday, October 26, 2019 5:08 AM
To: Liuyisong 
Subject: Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 
for IGMPv3

Hey,
Wondering if you still have some question about this draft. I would be present 
in coming IETF.

From: "Mankamana Mishra (mankamis)" 
mailto:manka...@cisco.com>>
Date: Thursday, July 12, 2018 at 7:14 PM
To: Liuyisong mailto:liuyis...@huawei.com>>, 
"draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org<mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>"
 
mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>>,
 "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: Zhuangshunwan mailto:zhuangshun...@huawei.com>>, 
"Yangang (Routing Design)" mailto:yang...@huawei.com>>
Subject: Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 
for IGMPv3

Hi Yisong

Would you be present in IETF, we could discuss in person and then update the 
thread?

Thanks
Mankamana


From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Liuyisong mailto:liuyis...@huawei.com>>
Date: Thursday, July 12, 2018 at 4:38 AM
To: 
"draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org<mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>"
 
mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>>,
 "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: Zhuangshunwan mailto:zhuangshun...@huawei.com>>, 
"Yangang (Routing Design)" mailto:yang...@huawei.com>>
Subject: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 for 
IGMPv3

Hi folks,

I have some questions about the draft-ietf-bess-evpn-igmp-mld-proxy-02 for 
IGMPv3 synchronization

In section 7.2 & 7.3, there are IGMP Join and Leave Synch Route definition as 
following:
[cid:image003.jpg@01D419FE.B52B2C00][cid:image006.jpg@01D419FE.B52B2C00]

IGMPv3 is very complicated, and it is not very clear to how to construct the 
IGMP Join/Leave Synch Route in the draft.
Firstly I think only incremental membership information in the IGMP synch 
route, because the route NLRI can only contain one (S,G) or (*,G)
1.for a simple example:
INCLUDE (A)BLOCK (B)INCLUDE (A) Send Q(G,A*B)
We can use include mode, source A*B, group G in IGMP Leave Synch Routes one by 
one to notify the other multi-homed PEs.

2.for a more complicated example:
EXCLUDE (X,Y)  TO_EX (A)EXCLUDE (A-Y,Y*A)   (A-X-Y)=Group Timer
Delete (X-A)
Delete (Y-A)
Send Q(G,A-Y)
Group Timer=GMI
It is more difficult than example 1.There are 5 actions, and should we use both 
Join and Leave Synch routes to notify the other multi-homed PEs?
I think we should use:

1） include mode, source A-X-Y, group G in IGMP Join Synch Routes one by one

2） include mode, source X-A, group G in IGMP Join Synch Routes withdraw one by 
one

3） exclude mode, source Y-A, group G in IGMP Join Synch Routes withdraw one by 
one

4） include mode, source A-Y, group G in IGMP Leave Synch Routes one by one
Is it appropriate for IGMPv3 Synch route construction in the draft?

3.In IGMPv3, only BLOCK, TO_IN, TO_EX can lead to generate last member query.
Is that mean when the PE only receive BLOCK, TO_IN , TO_EX , it should 
advertise the leave synch routes to the other multi-homed PEs?


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

Re: [bess] Wg Adoption and IPR poll for draft-liu-bess-mvpn-yang-07

[Liuyisong]

I support the adoption as a co-author
I am not aware of any IPR.

Thanks
Yisong

From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com]
Sent: Monday, December 03, 2018 10:53 PM
To: bess@ietf.org
Cc: draft-liu-bess-mvpn-y...@ietf.org
Subject: Wg Adoption and IPR poll for draft-liu-bess-mvpn-yang-07

This email begins a two-week poll for adoption of 
draft-liu-bess-mvpn-yang-07.txt

Please review the draft and post any comments to the BESS working group list.

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, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.
Currently there is one IPR declaration against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll for adoption closes on Monday 17th December 2018.

Regards,
Matthew


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

Re: [bess] WG adoption poll for draft-zzhang-bess-mvpn-evpn-aggregation-label-01

[Liuyisong]

I support

Thanks
Yisong

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Tuesday, October 30, 2018 4:22 PM
To: bess@ietf.org
Subject: [bess] WG adoption poll for 
draft-zzhang-bess-mvpn-evpn-aggregation-label-01

Hi WG,

This email begins a two-week poll for BESS working group adoption 
draft-zzhang-bess-mvpn-evpn-aggregation-label-01 [1]

Please review the draft and post any comments to the BESS working group list, 
stating whether or not you support adoption.

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, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

The poll for working group adoption closes on Tue 13th November.

Regards,
Stéphane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-evpn-aggregation-label/





[Orange logo]

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 06 49 83 

  NEW !
mobile: +33 6 71 63 27 50 

  NEW !
stephane.litkow...@orange.com


_



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.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 for IGMPv3

[Liuyisong]

Hi Mankamana

  I’ll go to Montreal in IETF 102. I’ll contact you, so we can discuss the 
question in more detail.

Thanks
Yisong

From: Mankamana Mishra (mankamis) [mailto:manka...@cisco.com]
Sent: Friday, July 13, 2018 10:14 AM
To: Liuyisong ; 
draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org; bess@ietf.org
Cc: Zhuangshunwan ; Yangang (Routing Design) 

Subject: Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 
for IGMPv3

Hi Yisong

Would you be present in IETF, we could discuss in person and then update the 
thread?

Thanks
Mankamana


From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Liuyisong mailto:liuyis...@huawei.com>>
Date: Thursday, July 12, 2018 at 4:38 AM
To: 
"draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org<mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>"
 
mailto:draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org>>,
 "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: Zhuangshunwan mailto:zhuangshun...@huawei.com>>, 
"Yangang (Routing Design)" mailto:yang...@huawei.com>>
Subject: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 for 
IGMPv3

Hi folks,

I have some questions about the draft-ietf-bess-evpn-igmp-mld-proxy-02 for 
IGMPv3 synchronization

In section 7.2 & 7.3, there are IGMP Join and Leave Synch Route definition as 
following:
[cid:image003.jpg@01D419FE.B52B2C00][cid:image006.jpg@01D419FE.B52B2C00]

IGMPv3 is very complicated, and it is not very clear to how to construct the 
IGMP Join/Leave Synch Route in the draft.
Firstly I think only incremental membership information in the IGMP synch 
route, because the route NLRI can only contain one (S,G) or (*,G)
1.for a simple example:
INCLUDE (A)BLOCK (B)INCLUDE (A) Send Q(G,A*B)
We can use include mode, source A*B, group G in IGMP Leave Synch Routes one by 
one to notify the other multi-homed PEs.

2.for a more complicated example:
EXCLUDE (X,Y)  TO_EX (A)EXCLUDE (A-Y,Y*A)   (A-X-Y)=Group Timer
Delete (X-A)
Delete (Y-A)
Send Q(G,A-Y)
Group Timer=GMI
It is more difficult than example 1.There are 5 actions, and should we use both 
Join and Leave Synch routes to notify the other multi-homed PEs?
I think we should use:

1） include mode, source A-X-Y, group G in IGMP Join Synch Routes one by one

2） include mode, source X-A, group G in IGMP Join Synch Routes withdraw one by 
one

3） exclude mode, source Y-A, group G in IGMP Join Synch Routes withdraw one by 
one

4） include mode, source A-Y, group G in IGMP Leave Synch Routes one by one
Is it appropriate for IGMPv3 Synch route construction in the draft?

3.In IGMPv3, only BLOCK, TO_IN, TO_EX can lead to generate last member query.
Is that mean when the PE only receive BLOCK, TO_IN , TO_EX , it should 
advertise the leave synch routes to the other multi-homed PEs?


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

Re: [bess] WG adoption and IPR poll on draft-liu-bess-mvpn-yang-05

[Liuyisong]

Support as a co-author.
Sorry for responding late.

Thanks
Yisong

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Wednesday, April 18, 2018 9:28 PM
To: bess@ietf.org
Subject: Re: [bess] WG adoption and IPR poll on draft-liu-bess-mvpn-yang-05

Hi WG,

This is a gentle reminder that this poll is currently running.
We have not received any feedback yet, while it sounds mandatory for BESS to 
have a YANG model for mVPNs.

Please reply to this poll with support or not support.

Brgds,


From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, April 09, 2018 16:23
To: bess@ietf.org
Subject: [bess] WG adoption and IPR poll on draft-liu-bess-mvpn-yang-05

This email begins a two-week poll for BESS working group adoption of 
draft-liu-bess-mvpn-yang -05 [1].

Please review the draft and post any comments to the BESS working group list, 
stating whether or not you support adoption.

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, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

The poll for working group adoption closes on Monday 23rd April.

Regards,
Stéphane and Matthew

[1] https://datatracker.ietf.org/doc/draft-liu-bess-mvpn-yang/


_



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.

_



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.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess