[bess] Question on symmetric IRB procedures in draft-ietf-bess-evpn-inter-subnet-forwarding

2019-03-19 Thread Muthu Arul Mozhi Perumal 
draft-ietf-bess-evpn-inter-subnet-forwarding says the following in section
3.2.2:


   If the receiving PE receives this route with both the MAC-VRF and IP-
   VRF route targets but the MAC/IP Advertisement route does not include
   MPLS label2 field and if the receiving PE supports asymmetric IRB
   mode, then the receiving PE installs the MAC address in the
   corresponding MAC-VRF and  association in the ARP table for
   that tenant (identified by the corresponding IP-VRF route target).


Further below it says:


   If the receiving PE receives this route with both the MAC-VRF and IP-
   VRF route targets but the MAC/IP Advertisement route does not include
   MPLS label2 field and if the receiving PE does not support either
   asymmetric or symmetric IRB modes, then if it has the corresponding
   MAC-VRF, it only imports the MAC address


How should "does not support either asymmetric or symmetric IRB" be
interpreted? Should it be interpreted as "supports neither asymmetric nor
symmetric"? Or should it be interpreted as "does not support one of them"?

If it is the former, then the case where the receiving PE supports only
symmetric (but not asymmetric) IRB isn't described. It it is the later then
it includes the case where the receiving PE supports only asymmetric (but
not symmetric) IRB and what is described in that paragraph conflicts with
the first paragraph mentioned above.

Regards,
Muthu
___
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

2019-03-19 Thread LINGALA, AVINASH 
Support as a co-author. Not aware of any undisclosed IPR.

-Avinash

From: "mitesh kanjariya" 
mailto:mitesh.kanjar...@gmail.com>>
Date: Monday, March 18, 2019 at 4:50:04 PM
To: "bess@ietf.org" mailto:bess@ietf.org>>, 
"draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" 
mailto:draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org>>,
 "stephane.litkow...@orange.com" 
mailto:stephane.litkow...@orange.com>>
Cc: "bess-cha...@ietf.org" mailto:bess-cha...@ietf.org>>
Subject: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04


Support.


-Mitesh



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.





--

Regards,

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

2019-03-19 Thread Ali Sajassi (sajassi) 
Support as co-author. Not aware of any undisclosed IPR.

Cheers,
Ali

From: mitesh kanjariya 
Date: Monday, March 18, 2019 at 1:50 PM
To: "bess@ietf.org" , 
"draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" 
, 
"stephane.litkow...@orange.com" 
Cc: "bess-cha...@ietf.org" 
Subject: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04
Resent-From: 
Resent-To: , Cisco Employee , 
, , , 

Resent-Date: Monday, March 18, 2019 at 1:49 PM


Support.



-Mitesh





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.









--

Regards,

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

2019-03-19 Thread UTTARO, JAMES 
Support..

Thanks,
  Jim Uttaro

From: BESS  On Behalf Of John E Drake
Sent: Monday, March 18, 2019 5:23 PM
To: mitesh kanjariya ; bess@ietf.org; 
draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org; 
stephane.litkow...@orange.com
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04

Support

Yours Irrespectively,

John

From: mitesh kanjariya 
mailto:mitesh.kanjar...@gmail.com>>
Sent: Monday, March 18, 2019 4:49 PM
To: bess@ietf.org; 
draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org;
 stephane.litkow...@orange.com
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for 
draft-malhotra-bess-evpn-irb-extended-mobility-04


Support.



-Mitesh





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.









--

Regards,

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

[bess] Question on IRB MAC in draft-ietf-bess-evpn-inter-subnet-forwarding

2019-03-19 Thread Muthu Arul Mozhi Perumal 
draft-ietf-bess-evpn-inter-subnet-forwarding describes two ways of
provisioning the default gateway MAC and IP addresses on the IRB interface
associated with the corresponding subnet:


   1. All the PEs for a given tenant subnet use the same anycast default
   gateway IP and MAC addresses . On each PE, this default gateway IP
   and MAC addresses correspond to the IRB interface connecting the BT
   associated with the tenant's VLAN to the corresponding tenant's IP-
   VRF.

   2. Each PE for a given tenant subnet uses the same anycast default
   gateway IP address but its own MAC address. These MAC addresses are
   aliased to the same anycast default gateway IP address through the
   use of the Default Gateway extended community as specified in
   [RFC7432], which is carried in the EVPN MAC/IP Advertisement routes.


Further below it says:


   Irrespective of using only the anycast address or both anycast and
   non-anycast addresses on the same IRB, when a TS sends an ARP request
   or ND Neighbor Solicitation (NS) to the PE that is attached to, the
   request is sent for the anycast IP address of the IRB interface
   associated with the TS's subnet and the reply will use anycast MAC
   address (in both Source MAC in the Ethernet header and Sender
   hardware address in the payload).


In the above, it says the ARP response or NS will use the anycast MAC
address. The question is, how is this feasible if the second option of
provisioning
the default gateway MAC and IP addresses on the IRB interface are chosen,
where each PE for a given tenant subnet uses the same anycast default
gateway IP address but its own MAC address?

Should it instead say:
  the request is sent for the anycast IP address of the IRB interface
   associated with the TS's subnet and the reply will use *configured*
   MAC address?

i.e. s/anycast MAC/configured MAC?

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