Re: [bess] qquestion om draft-mpmz-bess-mup-saf at the bess meeting at IETF 113

[Keyur Patel]

Hi Linda,

To be clear – We are not replacing the UPF. The UPF still remains in the 
network. We are also not changing anything that is defined in 3GPP architecture.

Best Regards,
Keyur

From: BESS  on behalf of Linda Dunbar 

Date: Tuesday, April 5, 2022 at 9:24 AM
To: Jeffrey (Zhaohui) Zhang , Loa Andersson , 
draft-mpmz-bess-mup-s...@ietf.org , 
wim.henderi...@alcatel-lucent.com 
Cc: BESS 
Subject: Re: [bess] qquestion om draft-mpmz-bess-mup-saf at the bess meeting at 
IETF 113
Jeffrey,

You are talking about changing the 3GPP architecture: replacing UPF by MUP and 
MUP GW, enabling BGP signaling, etc. have you discussed this architecture at 
3GPP S2 group?

Linda

-Original Message-
From: Jeffrey (Zhaohui) Zhang 
Sent: Monday, April 4, 2022 6:47 PM
To: Linda Dunbar ; Loa Andersson ; 
draft-mpmz-bess-mup-s...@ietf.org; wim.henderi...@alcatel-lucent.com
Cc: BESS 
Subject: RE: qquestion om draft-mpmz-bess-mup-saf at the bess meeting at IETF 
113

Hi Linda, Loa,

Consider a traditional 5G deployment with all necessary NFs, including a 
central UPF. SMF signals to the UPF on N4 interface. AMF signals to gNBs on N2 
interface. The N3 transport (between gNBs and the UPF) is via an IPVPN over a 
transport infrastructure. There are PEs next to the gNBs and the UPF. The PEs 
are not 3GPP functions.

Now replace that UPF with the following: MUP controller, a group of MUP GWs and 
a MUP PE. The MUP GWs are just the previous PEs next to the gNBs. The MUP PE is 
just the previous PE next to the replaced UPF. The UPF is no longer needed, but 
from SMF and gNB's point of view it is still there.

With this replacement, there is no N2/N4 change. gNBs still send GTP packets to 
the old UPF address; it's just that the GTP packets will be intercepted by the 
GWs as if the UPF address is a local one. They still receive GTP packets as if 
being sent from the previous UPF.

The BGP signaling translates N4 signaling to BGP messages. The N4 signaling 
could include the UE addresses that are managed by the SMF; it could also be 
that the previous central UPF was managing the UE addresses itself. In either 
case, the MUP controller will signal the UE addresses (as host routes) to the 
MUP GWs - whether assigned by the SMF or assigned by the MUP controller (if the 
addresses were managed by the UPF before).

Jeffrey


Juniper Business Use Only

-Original Message-
From: Linda Dunbar 
Sent: Monday, April 4, 2022 12:47 PM
To: Loa Andersson ; draft-mpmz-bess-mup-s...@ietf.org; 
wim.henderi...@alcatel-lucent.com
Cc: BESS 
Subject: RE: qquestion om draft-mpmz-bess-mup-saf at the bess meeting at IETF 
113

[External Email. Be cautious of content]


Thanks to Loa for reminding me of the questions.

Actually my question is more fundamental. The 3GPP Mobility Management Function 
manages the IP address assignments to UEs. Traffic from UEs are tunneled by GTP 
tunnel between the eNB and UPF. Many UPF has NAT, so the IP network might not 
see the UE's actual IP addresses.

Question 1: is draft-mpmz-bess-mup-safi managing the IP address from UPF? Or 
the actual UEs' IP addresses?
Question 2: If it is the IP addresses from the UPF, many flows from different 
UEs are aggregated to one IP. What the BGP extension for Mobile User Plan do?


Thank you very much.
Linda

-Original Message-
From: Loa Andersson 
Sent: Sunday, April 3, 2022 12:58 AM
To: draft-mpmz-bess-mup-s...@ietf.org; Linda Dunbar 
; wim.henderi...@alcatel-lucent.com
Cc: BESS 
Subject: qquestion om draft-mpmz-bess-mup-saf at the bess meeting at IETF 113

Authors,

When the draft-mpmz-bess-mup-safi were presented at IETF 113, Linda asked a 
question. The audio was bad, but I think Linda asked "VPN 3GPP and and VPN6, 
uses totally different address, how are they inter-worked?" I could not hear 
your answer, can you please repeat here?

Wim asked about the relationship to 3GPP. I think your answer was that since 
you are not changing anything in the 3GPP specifications there is no problem. 
That might be correct, but I think it would be prudent to let 3GPP know what we 
are doing.

/Loa


--
Loa Anderssonemail: l...@pi.nu
Senior MPLS Expert  loa.pi...@gmail.com
Bronze Dragon Consulting phone: +46 739 81 21 64
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG and IPR poll adoption poll for draft-krattiger-evpn-modes-interop

[Keyur Patel]

Support the adoption.

Regards,
Keyur

On Apr 19, 2021, at 11:06 AM, slitkows.i...@gmail.com wrote:


Hello,

This email begins a two-weeks WG adoption poll for 
draft-krattiger-evpn-modes-interop-03 [1].

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 will not  progress 
without answers from all of the authors and contributors.

Currently, there are no IPR disclosures 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 4th May 2021.

Regards,
Matthew and Stephane


[1]  https://datatracker.ietf.org/doc/draft-krattiger-evpn-modes-interop/

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

Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-evpn-irb-extended-mobility-01

[Keyur Patel]

Support to publication of the draft. We also have an implementation of the 
draft and would be happy to fill out any implementation survey.

Regards,
Keyur

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Monday, January 18, 2021 at 12:58 AM
To: "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-evpn-irb-extended-mobility-01


This email starts a two-week working group last call for 
draft-ietf-bess-evpn-irb-extended-mobility-01 [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 February 1st.







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 no IPR disclosed.


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-evpn-irb-extended-mobility/
[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] IGMP / MLD Proxy Draft update (NLRI change)

[Keyur Patel]

I agree with Jorge and Mankamana. We don’t need leave group sequence number.  I 
would keep it out for now.

Regards,
Keyur

From: "Rabadan, Jorge (Nokia - US/Mountain View)" 
Date: Thursday, April 23, 2020 at 1:18 AM
To: "Mankamana Mishra (mankamis)" , 
"bess@ietf.org" 
Cc: "draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org" 

Subject: Re: [bess] IGMP / MLD Proxy Draft update (NLRI change)
Resent-From: 
Resent-To: , , , 
, 
Resent-Date: Thursday, April 23, 2020 at 1:18 AM

Thank you Mankamana.

From Nokia’s perspective I confirm your reference below. We implemented it 
without a Seq number based on what we thought was that agreement among authors 
pre-IETF106.

Just wanted to mention that there were never any procedures specified for the 
sequence number in the draft. So even if two implementors had attempted to 
implement that sequence number, there is no guarantee they could have 
interoperated with each other. So the Sequence number reference must go from 
the draft anyway. To me, the real discussion is if removing those 4 bytes from 
the NLRI length will cause issues.

My take is that, given the implementations that we have in the field, the 
proposal for the RR to accept both lengths seems like the better practical 
option. And since that field cannot be a sequence number anymore, it should be 
removed from the draft as soon as possible to avoid confusion for future 
implementors.

But I would also like people to share their concerns here.

Thanks.
Jorge


From: BESS  on behalf of "Mankamana Mishra (mankamis)" 

Date: Thursday, April 23, 2020 at 8:32 AM
To: "bess@ietf.org" 
Cc: "draft-ietf-bess-evpn-igmp-mld-pr...@ietf.org" 

Subject: [bess] IGMP / MLD Proxy Draft update (NLRI change)

All,
Post WGLC  before IETF Singapore it came to our notice that there were 
implementation discrepancies of this draft 
(https://tools.ietf.org/html/draft-ietf-bess-evpn-igmp-mld-proxy-04#section-9.3).
 Though draft had NLRI definition as

 +--+
 |  RD (8 octets)   |
 +--+
 | Ethernet Segment Identifier (10 octets)  |
 +--+
 |  Ethernet Tag ID  (4 octets) |
 +--+
 |  Multicast Source Length (1 octet)   |
 +--+
 |  Multicast Source Address (variable) |
 +--+
 |  Multicast Group Length (1 octet)|
 +--+
 |  Multicast Group Address (Variable)  |
 +--+
 |  Originator Router Length (1 octet)  |
 +--+
 |  Originator Router Address (variable)|
 +--+
 |  Leave Group Synchronization  # (4 octets)   |
 +--+
 |  Maximum Response Time (1 octet) |
 +--+
 |  Flags (1 octet) |
 +--+
Where there was Leave Group Synchronization number as part of NLRI. But two 
implementation were

1.  With this field as part of NLRI

2.  Without this field as part of NLRI

Implementation survey As of 2019:
 Since it came to notice that at least there are two implementation which would 
not interop, we did try to take survey of other implementation.  We tried it 
with IETF & Nanog forum. We reached out to some of vendors directly as well. 
And implementation were
Cisco – Without Seq number
Juniper – With Seq number
Arista -  with and without sequence number
Apart from these vendors, we did not get response from any one else who had 
implemented these routes.

Before IETF 106 (Singapore) there were couple of discussion among authors & 
other vendors. And it was evident that there are two implementation which would 
not interop as is.  And Sequence number for IGMP does not have any value or 
need. And majority of vendors were ok to remove this field from NLRI as there 
is no practical use case.  So one of the proposal was to remove the field. And 
to make sure we interop with old version proposal was to

1.  Remove Seq number from NLRI

2.  RR MUST accept both len of NLRI

IETF 106 Update :

These changes were presented in IETF 106 Singapore as well.

Implementation Changes post IETF106, As of Today:

Nokia -  Implemented without Seq number, and RR 

Re: [bess] REMINDER Re: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-datacenter-gateway-04

[Keyur Patel]

Support and not aware of any IPR.

Regards,
Keyur

On Feb 26, 2020, at 11:32 AM, John E Drake  wrote:


Support and not aware of any IPR

Yours Irrespectively,

John



Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB) 
Sent: Wednesday, February 26, 2020 6:29 AM
To: draft-ietf-bess-datacenter-gate...@ietf.org; bess@ietf.org
Subject: REMINDER Re: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-datacenter-gateway-04

WG

I have only seen one IPR responses to this WG last call and no comments. I will 
therefore extend it for another two weeks.

Regards

Matthew

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"Bocci, Matthew (Nokia - GB)" 
mailto:matthew.bo...@nokia.com>>
Date: Monday, 10 February 2020 at 16:17
To: 
"draft-ietf-bess-datacenter-gate...@ietf.org"
 
mailto:draft-ietf-bess-datacenter-gate...@ietf.org>>,
 "bess@ietf.org" mailto:bess@ietf.org>>
Subject: [bess] WG Last Call, IPR and Implementation Poll for 
draft-ietf-bess-datacenter-gateway-04

This email starts a two-week working group last call for 
draft-ietf-bess-datacenter-gateway-04
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 24th February 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 no IPR disclosed.

We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations of the modified protocol described in 
this draft.

 Thank you,

Matthew

[1] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw


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

Re: [bess] WG adoption and IPR poll for draft-zzhang-bess-bgp-multicast-03

[Keyur Patel]

Support as a co-author. Not aware of any undisclosed IPRs related to this draft.

Regards,
Keyur

On Jan 6, 2020, at 6:43 PM, Gulko, Arkadiy (Refinitiv) 
 wrote:


Support as a co-author. I am not aware of any undisclosed IPR related to this 
draft.
Regards,
Arkadiy

From: "slitkows.i...@gmail.com" 
Date: Monday, January 6, 2020 at 9:15 AM
To: "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" , 
"draft-zzhang-bess-bgp-multic...@ietf.org" 

Subject: WG adoption and IPR poll for draft-zzhang-bess-bgp-multicast-03
Resent-From: 
Resent-To: , , , 
, , 
Resent-Date: Monday, January 6, 2020 at 9:14 AM

Hello,

This email begins a two-weeks WG adoption poll for and 
draft-zzhang-bess-bgp-multicast-03 [1] .
For information, it’s companion document 
(draft-zzhang-bess-bgp-multicast-controller-02) is also polled for WG adoption 
in a separate email.

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 are no IPR disclosures 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 *** 20th January 2020 ***

Regards,
Matthew and Stephane

[1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-bgp-multicast

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

Re: [bess] WG Last Call and Implementation Poll for draft-ietf-bess-rfc5549revision-00

[Keyur Patel]

Support!  Arrcus has an implementation as well.

Regards,
Keyur

From: BESS  on behalf of "Bocci, Matthew (Nokia - GB)" 

Date: Monday, January 6, 2020 at 9:54 AM
To: "bess@ietf.org" 
Subject: [bess] WG Last Call and Implementation Poll for 
draft-ietf-bess-rfc5549revision-00

This email starts a two weeks Working Group Last Call on 
draft-ietf-bess-rfc5549revision-00.

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 20th January 2019.

We have only just completed an IPR poll on the draft prior to adoption in 
December 2019, so I will not run another one now.

There is currently no IPR disclosed.

We are also polling for any existing implementation as per [1]. Please indicate 
if you are aware of any implementations of the modified protocol described in 
this draft.

 Thank you,

Matthew

[1] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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

Re: [bess] WG Adoption and IPR Poll for draft-litkowski-bess-rfc5549revision-00

[Keyur Patel]

+1. Support the adoption. I am not aware of any IPR.

Regards,
Keyur

From: BESS  on behalf of "slitkows.i...@gmail.com" 

Date: Wednesday, November 27, 2019 at 4:49 AM
To: "'Bocci, Matthew (Nokia - GB)'" , "bess@ietf.org" 

Cc: "bess-cha...@ietf.org" 
Subject: Re: [bess] WG Adoption and IPR Poll for 
draft-litkowski-bess-rfc5549revision-00

Support,
I’m not aware of any IPR.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
"Bocci, Matthew (Nokia - GB)" 
mailto:matthew.bo...@nokia.com>>
Date: Wednesday, November 27, 2019 at 7:37 AM
To: "bess@ietf.org" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: [bess] WG Adoption and IPR Poll for 
draft-litkowski-bess-rfc5549revision-00

Hello,

This email begins a two-weeks WG adoption poll for 
draft-litkowski-bess-rfc5549revision-00 [1] .

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 are no IPR disclosures 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 Wednesday 11th December 2019.

Regards,
Matthew

[1] https://datatracker.ietf.org/doc/draft-litkowski-bess-rfc5549revision/



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

Re: [bess] WG adoption and IPR poll for draft-keyupate-bess-evpn-virtual-hub-02

[Keyur Patel]

Hi Matthew,

Submitted 00 version. Will address Neeraj’s comments in the follow up draft 
update.

Regards,
Keyur

From: "Bocci, Matthew (Nokia - GB)" 
Date: Monday, September 23, 2019 at 9:26 AM
To: "draft-keyupate-bess-evpn-virtual-...@ietf.org" 
, "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: Re: WG adoption and IPR poll for 
draft-keyupate-bess-evpn-virtual-hub-02
Resent-From: 
Resent-To: , , , 
, 
Resent-Date: Monday, September 23, 2019 at 9:26 AM

This email closes this working group adoption poll.

Authors: please upload a new version of the draft as 
draft-ietf-bess-evpn-virtual-hub-00.

Please also be good to address/respond to the comments from Neeraj.

Best regards

Matthew

From: "Bocci, Matthew (Nokia - GB)" 
Date: Wednesday, 4 September 2019 at 09:36
To: "draft-keyupate-bess-evpn-virtual-...@ietf.org" 
, "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: WG adoption and IPR poll for draft-keyupate-bess-evpn-virtual-hub-02
Resent from: 
Resent to: , , 

Resent date: Wednesday, 4 September 2019 at 09:36

This email begins a two-week poll for adoption for 
draft-keyupate-bess-evpn-virtual-hub-02

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 are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond to the IPR poll 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 Wednesday 18th September 2019.

Regards,
Matthew and Stephane


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

Re: [bess] WG adoption and IPR poll for draft-keyupate-bess-evpn-virtual-hub-02

[Keyur Patel]

Support as a co-author. Not aware of IPRs.

Regards,
Keyur

From: "Jeffrey (Zhaohui) Zhang" 
Date: Thursday, September 5, 2019 at 12:09 AM
To: "Ali Sajassi (sajassi)" , "Bocci, Matthew (Nokia - GB)" 
, "draft-keyupate-bess-evpn-virtual-...@ietf.org" 
, "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: RE: WG adoption and IPR poll for 
draft-keyupate-bess-evpn-virtual-hub-02
Resent-From: 
Resent-To: , , , 
, 
Resent-Date: Thursday, September 5, 2019 at 12:09 AM

Support as co-author. Not aware of IPRs.

Jeffrey

From: Ali Sajassi (sajassi) 
Sent: Wednesday, September 4, 2019 2:25 PM
To: Bocci, Matthew (Nokia - GB) ; 
draft-keyupate-bess-evpn-virtual-...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: WG adoption and IPR poll for 
draft-keyupate-bess-evpn-virtual-hub-02


Support as a co-author. I am not aware of any undisclosed IPR.

Cheers,
Ali

From: "Bocci, Matthew (Nokia - GB)" 
mailto:matthew.bo...@nokia.com>>
Date: Wednesday, September 4, 2019 at 1:36 AM
To: 
"draft-keyupate-bess-evpn-virtual-...@ietf.org"
 
mailto:draft-keyupate-bess-evpn-virtual-...@ietf.org>>,
 "bess@ietf.org" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: WG adoption and IPR poll for draft-keyupate-bess-evpn-virtual-hub-02
Resent-From: mailto:alias-boun...@ietf.org>>
Resent-To: mailto:ke...@arrcus.com>>, Cisco Employee 
mailto:saja...@cisco.com>>, 
mailto:jdr...@juniper.net>>, 
mailto:zzh...@juniper.net>>, 
mailto:wim.henderi...@nokia.com>>
Resent-Date: Wednesday, September 4, 2019 at 1:36 AM

This email begins a two-week poll for adoption for 
draft-keyupate-bess-evpn-virtual-hub-02

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 are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly 
respond to the IPR poll 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 Wednesday 18th September 2019.

Regards,
Matthew and Stephane


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

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-igmp-mld-proxy

[Keyur Patel]

Support. Not aware of any IPR.

Regards,
Keyur

On Jun 17, 2019, at 6:03 PM, Mankamana Mishra (mankamis) 
mailto:manka...@cisco.com>> wrote:

Support.  Not aware of undisclosed IPR.

Thanks
Mankamana


From: "stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>>
Date: Monday, June 17, 2019 at 1:54 AM
To: "bess@ietf.org" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org" 
mailto:bess-cha...@ietf.org>>
Subject: WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-igmp-mld-proxy
Resent-From: mailto:alias-boun...@ietf.org>>
Resent-To: mailto:matthew.bo...@nokia.com>>, 
mailto:stephane.litkow...@orange.com>>, 
mailto:manka...@cisco.com>>
Resent-Date: Monday, June 17, 2019 at 1:53 AM


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-evpn-igmp-mld-proxy [1].



This poll runs until *the 28th of June*.



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.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-igmp-mld-proxy/

[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw





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

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

[Keyur Patel]

Support the adoption.
Regards,
Keyur

Sent from my iPhone

On Mar 20, 2019, at 5:51 AM, 
"stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>> wrote:

Hi WG,

Apart from the authors, we haven’t received a lot of feedback for this draft 
(positive or negative).
I would like to expand the poll to an additional week (ends at 26th March) to 
see if we can get more support on the list.

Brgds,

From: stephane..litkow...@orange.com 
[mailto:stephane.litkow...@orange.com]
Sent: Tuesday, March 05, 2019 09:43
To: bess@ietf.org; 
draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Hi,


This email begins a two-week poll for adoption of 
draft-malhotra-bess-evpn-irb-extended-mobility-04
[1]

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 are no IPR disclosures 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 19th March 2019.

Regards,
Stephane and Matthew

[1] 
https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/



_



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

Re: [bess] Call for adoption: draft-drake-bess-datacenter-gateway

[Keyur Patel]

I am unaware of any undisclosed IPR that applies to this draft.

Regards,
Keyur

On 10/27/17, 6:47 AM, "Eric C Rosen"  wrote:

I am unaware of any undisclosed IPR that applies to this draft.


On 9/25/2017 5:42 AM, Martin Vigoureux wrote:
> Hello working group,
>
> This email starts a two-week call for adoption on 
> draft-drake-bess-datacenter-gateway-05 [1] as a BESS Working Group 
> Document.
>
> Please state on the list if you support the adoption or not (in both 
> cases, please also state the reasons).
>
> This poll runs until *the 2nd of October*.
>
> 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.
>
> Currently no IPR has been disclosed 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.
>
> Thank you
>
> Martin & Thomas
> bess chairs
>
> [1] 
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Ddrake-2Dbess-2Ddatacenter-2Dgateway_=DwIC-g=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo=PH0tABqMXcA-TgEvraUZC2HrDAmgmPxVx36tE1gUWSw=GSHLcpm8n5C1KatiovmQUcLTxxzJS2YOrLtZMCuFrLY=
 




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

Re: [bess] WG Last Call for draft-ietf-bess-fat-pw-bgp

[Keyur Patel]

I support publication of this document. I am not aware of any IPR related to 
this doc that hasn’t already been disclosed.

Regards,
Keyur


On 6/12/17, 9:27 AM, "BESS on behalf of Martin Vigoureux" 
 wrote:

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-fat-pw-bgp-02 [1] which is considered mature and ready 
for a final working group review.

¤ Please read this document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*26th of June*.
Note that this is *not only* a call for comments on the document; it is 
also a call for support (or not) to publish this document as a Proposed 
Standard RFC.

¤ *Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-fat-pw-bgp, 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 a document Author or Contributor of
draft-ietf-bess-fat-pw-bgp-02 please respond to this email and indicate 
whether or not you are aware of any relevant IPR.

Note that, as of today, no IPR has been disclosed against this document 
or its earlier versions.

¤ We are also polling for knowledge of implementations of part or all of 
what this document specifies. This information is expected as per [2]. 
Please inform the mailing list, or the chairs, or only one of the chairs.


Thank you,
M

[1] https://datatracker.ietf.org/doc/draft-ietf-bess-fat-pw-bgp/
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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


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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

[Keyur Patel]

I support publication of this document. I am not aware of any IPR related to 
this doc that hasn’t already been disclosed.

Regards,
Keyur


On 6/12/17, 9:27 AM, "BESS on behalf of Martin Vigoureux" 
 wrote:

WG, Authors/Contributors, this is a reminder.
Thank you
-m


Le 06/06/2017 à 16:11, Martin Vigoureux a écrit :
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-usage-04 [1] which is considered mature and ready
> for a final working group review.
>
> Please read this document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *20th of June*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as an
> Informational RFC.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-usage, 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 a document Author or Contributor of
> draft-ietf-bess-evpn-usage-04 please respond to this email and indicate
> whether or not you are aware of any relevant IPR.
>
> Note that, as of today, no IPR has been disclosed against this document
> or its earlier versions.
>
> As opposed to the policy [2], we are not polling for knowledge of
> implementations as it does not seem to make sense in that case. If you
> feel otherwise, please let us know.
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>

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


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

Re: [bess] Call for adoption: draft-mackie-bess-nsh-bgp-control-plane

[Keyur Patel]

Support. Not aware of any IPR that applies to this document.

On 3/23/17, 12:39 PM, "BESS on behalf of Eric C Rosen"  wrote:

Support.

I am not aware of any undisclosed IPR that applies to this document.


On 3/6/2017 6:55 AM, Martin Vigoureux wrote:
> Hello working group,
>
> This email starts a two-week call for adoption on 
> draft-mackie-bess-nsh-bgp-control-plane-04 [1] as a Working Group 
> Document.
>
> Please state on the list if you support the adoption or not (in both 
> cases, please also state the reasons).
>
> This poll runs until *the 19th of March*.
>
> 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 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.
>
> IPR has been disclosed against this Document [2].
>
> If you 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.
>
> Thank you
>
> Martin & Thomas
> bess chairs
>
> [1] 
> https://datatracker.ietf.org/doc/draft-mackie-bess-nsh-bgp-control-plane/
> [2] 
> 
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-mackie-bess-nsh-bgp-control-plane

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


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

Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

[Keyur Patel]

Support as a co-author. I am not aware of any IPR related to this draft.

Regards,
Keyur

On 1/31/17, 1:30 PM, "Ali Sajassi (sajassi)"  wrote:


Support as a co-author. I am not aware of any IPR related to this draft
that hasn¹t already been disclosed.

Regards,
Ali

On 1/31/17, 6:58 AM, "Thomas Morin"  wrote:

>Hello working group,
>
>This email starts a two-week poll on adopting
>draft-sajassi-bess-evpn-igmp-mld-proxy-01 [1] as a working group item.
>
>Please send comments to the list and state if you support adoption or
>not (in the later case, please also state the reasons).
>
>This poll runs until **February 14th**.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to this draft, 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 a document author or contributor please
>respond to this email and indicate whether or not you are aware of any
>relevant IPR.
>
>The draft will not be adopted until a response has been received from
>each author and contributor.
>
>If you 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.
>
>Thank you,
>
>Martin & Thomas
>bess chairs
>
>[1] 
>https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01



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

Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03

[Keyur Patel]

I am not aware of any IPRs related to the draft.


Apologies for the delayed response.


Best Regards,

Keyur


> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Tuesday, August 16, 2016 8:37 AM
> To: bess@ietf.org
> Cc: draft-zzhang-bess-evpn-bum-procedure-upda...@ietf.org
> Subject: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-
> updates-03
>
> Hello working group,
>
> This email starts a two-week poll on adopting
> draft-zzhang-bess-evpn-bum-procedure-updates-03 [1] as a Working Group
> Document.
>
> Please state on the list if you support adoption or not (in both cases,
> please also state the reasons).
>
> This poll runs until *the 30th of August*.
>
> 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 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.
> No IPR has been disclosed against this Document
>
> If you 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.
>
> Thank you
>
> Martin & Thomas
> bess chairs
>
> [1]
> https://datatracker.ietf.org/doc/draft-zzhang-bess-evpn-bum-procedure-
> updates/
>
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] RTG Dir QA review: draft-ietf-bess-evpn-overlay-04.txt

[Keyur Patel]

Hello,

I have been selected as the Routing Directorate QA reviewer for 
draft-ietf-bess-evpn-overlay-04.txt.


The Routing Directorate QA reviews are intended to be a support to improve the 
quality of RTG Area documents as they pass through the IETF process. This is 
the QA review at the time of the WG document adoption poll.


Summary:


This document describes how Ethernet VPN (EVPN) [RFC7432] can be used as a 
Network Virtualization Overlay (NVO) solution and explores the various tunnel 
encapsulation options over IP and their impact on the EVPN control-plane and 
procedures. In particular, the following encapsulation options are analyzed: 
VXLAN, NVGRE, and MPLS over GRE.



The document is well written, easy to read and follow. Some minor comments are 
listed below:


Comments:


1) Introduction section suggests xmpp based approach as an alternative to the 
BGP as a control plane. It is unclear how the draft sections 8-10 and the 
security section 12 relate to the alternative solution. My suggestion would be 
to remove the reference if possible considering the draft is specific to BGP as 
a control plane.


2) Section 5.1.2.1 defines Autoderivation RT which suggests the use of 2 byte 
AS number. Do we need to consider 4 byte AS number as well? []


3) Section 6: Minor Nit. Consider replacing "statically" with "locally".


4) Section 7.1: Talks about using RD value of 0. RD as a type:value field. Type 
0 RD requires the usage of 2 byte AS number (private values are strongly 
discouraged) which needs to be 0 for RD value to be 0. AS 0 according to IANA 
is reserved. Seems to be like usage of AS 0 is prohibited. Would a reserve RD 
value be more appropriate?


5) section 8.3.1 describes the draft constrain wrt mpls over gre versus 
vxlan/nvgre. Perhaps it would be great to highlight the constrain upfront in 
the introduction section?


6) Do you need to add text to describe ARP/ND suppression in presence of 
default route?


Best Regards,

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

Re: [bess] Poll for adoption: draft-mohanty-bess-evpn-df-election-02

[Keyur Patel (keyupate)]

Not aware of any IPR that hasn¹t already been disclosed.


On 1/12/16, 10:19 AM, "Keyur Patel (keyupate)" <keyup...@cisco.com> wrote:

>Support as a co-author.
>
>Regards,
>Keyur
>
>On 1/12/16, 8:53 AM, "Satya Mohanty (satyamoh)" <satya...@cisco.com>
>wrote:
>
>>Support as co-author.
>>
>>Thanks,
>>‹Satya
>>
>>On 1/11/16, 1:07 AM, "BESS on behalf of Martin Vigoureux"
>><bess-boun...@ietf.org on behalf of martin.vigour...@alcatel-lucent.com>
>>wrote:
>>
>>>Hello working group,
>>>
>>>This email starts a two-week poll on adopting
>>>draft-mohanty-bess-evpn-df-election-02 [1] as a working group item.
>>>
>>>Please state on the list if you support adoption or not (in the both
>>>cases, please also state the reasons).
>>>
>>>This poll runs until *the 25th of January*.
>>>
>>>Currently no IPR has been disclosed against this document.
>>>
>>>*Coincidentally*, we are also polling for knowledge of any IPR that
>>>applies to this draft, 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 a document author or contributor please
>>>respond to this email and indicate whether or not you are aware of any
>>>relevant IPR.
>>>
>>>The draft will not be adopted until a response has been received from
>>>each author and contributor.
>>>
>>>If you 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.
>>>
>>>Thank you,
>>>
>>>Martin & Thomas
>>>bess chairs
>>>
>>>[1] 
>>>https://datatracker.ietf.org/doc/draft-mohanty-bess-evpn-df-election/
>>>
>>>___
>>>BESS mailing list
>>>BESS@ietf.org
>>>https://www.ietf.org/mailman/listinfo/bess
>>
>

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

Re: [bess] Poll for adoption: draft-keyupate-l2vpn-fat-pw-bgp

[Keyur Patel (keyupate)]

I support this document for WG adoption as a co-author.
Not aware of any related IPR.


Regards,
Keyur

On 6/12/15, 8:58 AM, Martin Vigoureux
martin.vigour...@alcatel-lucent.com wrote:

Hello working group,

This email starts a two-week poll on adopting
draft-keyupate-l2vpn-fat-pw-bgp [1] as a working group item.

Please send comments to the list and state if you support adoption or
not (in the later case, please also state the reasons).

This poll runs until **June the 26th**.


*Coincidentally*, we are also polling for knowledge of any IPR that
applies to this draft, 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 a document author or contributor* please respond
to this email and indicate whether or not you are aware of any relevant
IPR.

The draft will not be adopted until a response has been received from
each author and contributor.

If you 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.

Thank you,

Martin  Thomas
bess chairs

[1] https://tools.ietf.org/html/draft-keyupate-l2vpn-fat-pw-bgp

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

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

Re: [bess] Poll for adoption: draft-morin-bess-multicast-damping

[Keyur Patel (keyupate)]

I am not aware of any IPR related to this draft. I support as a co-author.

Regards,
Keyur

On 1/27/15, 10:28 AM, Jeff Tantsura jeff.tants...@ericsson.com wrote:

Yes/support

Cheers,
Jeff




-Original Message-
From: Robert Kebler rkeb...@juniper.net
Date: Tuesday, January 27, 2015 at 9:13 AM
To: Martin Vigoureux martin.vigour...@alcatel-lucent.com,
bess@ietf.org bess@ietf.org
Cc: draft-morin-bess-multicast-damp...@tools.ietf.org
draft-morin-bess-multicast-damp...@tools.ietf.org
Subject: Re: [bess] Poll for adoption: draft-morin-bess-multicast-damping

Hi,

I'm not aware of any IPR related to this draft.  I support adoption as a
co-author.

Thanks,
Bob

 -Original Message-
 From: Martin Vigoureux [mailto:martin.vigour...@alcatel-lucent.com]
 Sent: Monday, January 26, 2015 4:47 AM
 To: bess@ietf.org
 Cc: draft-morin-bess-multicast-damp...@tools.ietf.org
 Subject: Poll for adoption: draft-morin-bess-multicast-damping
 
 Hello working group,
 
 This email starts a two-week poll on adopting draft-morin-bess-
 multicast-damping [1] as a working group item.
 
 Please send comments to the list and state if you support adoption or
 not (in the later case, please also state the reasons).
 
 This poll runs until **February 9th**.
 
 
 *Coincidentally*, we are also polling for knowledge of any IPR that
 applies to this draft, 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 a document author or contributor* please
 respond to this email and indicate whether or not you are aware of any
 relevant IPR.
 
 The draft will not be adopted until a response has been received from
 each author and contributor.
 
 If you 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.
 
 Thank you,
 
 Martin  Thomas
 bess chairs
 
 [1] https://tools.ietf.org/html/draft-morin-bess-multicast-damping

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

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

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