Re: [bess] Slots requests for BESS WG session - IETF 101 - London

[Ali Sajassi (sajassi)]

Hi Stephane,

I’d like to request a 20 min slot to go over the status of the following drafts 
and request for WG LC/WG call:

https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpls-seamless-integ/
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-igmp-mld-proxy/
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-vpws-fxc/
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-virtual-eth-segment/
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-fast-df-recovery/


Regards,
Ali


From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Thursday, February 22, 2018 at 6:43 AM
To: "bess@ietf.org" 
Subject: [bess] Slots requests for BESS WG session - IETF 101 - London


All,



it is time we start building the BESS WG agenda for London.

The IETF agenda (still preliminary) is available at:

https://datatracker.ietf.org/meeting/101/agenda.html



The BESS WG session (2h30) is scheduled on Tuesday, March 20th, 2018 / 
Afternoon session II / 15:50-18:20 (local time)



Please send us your request for a presentation slot, indicating draft name, 
speaker, and desired duration (covering presentation and discussion).



Thank you



Stephane & Matthew


_



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] Call for adoption:draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

[zhang.zheng]

Support the adoption of this draft.







Thanks,


Sandy











原始邮件



发件人：stephane.litkow...@orange.com 
收件人：bess@ietf.org 
日 期 ：2018年02月26日 16:03
主 题 ：[bess] Call for adoption:draft-zzhang-bess-mvpn-msdp-sa-interoperation-01


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

  

Hello working group,


 


This email starts a two-week call for adoption on


draft-zzhang-bess-mvpn-msdp-sa-interoperation-01 [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 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 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), Matthew, Stéphane


bess chairs


 


[1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/


 


_
 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] I-D Action: draft-ietf-bess-mvpn-expl-track-07.txt

[Eric C Rosen]

On 2/22/2018 3:10 AM, stephane.litkow...@orange.com wrote:

Hi Eric,



Thanks a lot for the update.


And thank you for your continued attention to the details.  I have 
posted -08.  Responses in-line.




Couple of more comments:



Section 2:

I still have some concern about these two sentences:

1)"This flag SHOULD NOT be set

unless it is known that all the PEs that are to receive the route

carrying the PTA support the flag."

2)"By setting LIR as well as

LIR-pF, one forces a response to be sent by an egress node that does

not support LIR-pF."



[SLI] As per 1), the situation described in 2) should not happen

Do we agree that this should not happen ?

I think we can make the text more clear about the implications of setting the 
LIR-pf in a partial deployment scenario.

We can add a text like after 1):

"Setting the LIR-pF in a network where only a subset of PEs supports it prevents the 
ingress PE to have a complete view of the receiving PEs."



We may also modify 2) as follows:

OLD

By setting LIR as well as

LIR-pF, one forces a response to be sent by an egress node that does

not support LIR-pF.  It is possible to tell from that response that

the egress node does not support LIR-pF.  This may be an aid to

troubleshooting.

NEW

By setting LIR as well as

LIR-pF, one forces a response to be sent by an egress node that does

not support LIR-pF.  It is possible to tell from that response that

the egress node does not support LIR-pF.  As the support of LIR-pF is 
recommended on all PEs, this situation should not happen.

   However, in case of deployment error, this may be an aid to troubleshooting.


[Eric] In revision -08, I have reworked this text to indicate what will 
happen in the case of deployment errors, and how such errors can be 
detected.  However, I wouldn't necessarily guarantee that there are no 
corner cases in which a deployment error might go undetected.










Section 5.2:

"The encoding of these Leaf A-D routes is similar to the encoding of

the Leaf A-D routes described in section 6.2.2 of [RFC7524], which

were designed for the support of "global table multicast".  However,

that document sets the RD to either 0 or -1; following the procedures

of this document, the RD will never be 0 or -1.  Therefore Leaf A-D

routes constructed according to the procedures of this section can

always be distinguished from the Leaf A-D routes constructed

according to the procedures of section 6.2.2 of [RFC7524].  Also,

Leaf A-D routes constructed according to the procedures of this

section are VPN-specific routes, and will always carry an IP-address-

specific Route Target, as specified in [RFC6514]."



[SLI] I'm wondering if this text is still required as we do not modify the RD 
compared to RFC6514.



[Eric] There are two situations in which an ingress node might receive a 
Leaf A-D route whose route key field is not identical to the NLRI of a 
current x-PMSI A-D route originated by the ingress node.  One situation 
is specified in RFC 7524.  The other is specified in the explicit 
tracking draft.  I think it is useful to point out that the ingress node 
can distinguish between these two cases when it receives such a Leaf A-D 
route.


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

[bess] I-D Action: draft-ietf-bess-mvpn-expl-track-08.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.

Title   : Explicit Tracking with Wild Card Routes in Multicast 
VPN
Authors : Andrew Dolganow
  Jayant Kotalwar
  Eric C. Rosen
  Zhaohui Zhang
Filename: draft-ietf-bess-mvpn-expl-track-08.txt
Pages   : 18
Date: 2018-02-26

Abstract:
   The MVPN specifications provide procedures to allow a multicast
   ingress node to invoke "explicit tracking" for a multicast flow or
   set of flows, thus learning the egress nodes for that flow or set of
   flows.  However, the specifications are not completely clear about
   how the explicit tracking procedures work in certain scenarios.  This
   document provides the necessary clarifications.  It also specifies a
   new, optimized explicit tracking procedure.  This new procedure
   allows an ingress node, by sending a single message, to request
   explicit tracking of each of a set of flows, where the set of flows
   is specified using a wildcard mechanism.  This document updates RFCs
   6514, 6625, and 7524.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-expl-track/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-mvpn-expl-track-08
https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-expl-track-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-expl-track-08


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

Re: [bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

[Leonard Giuliano]

Support as coauthor bc it addresses a practical deployment problem that is 
currently seen with MSDP interacting with MVPN.

I am not aware of any relevant undisclosed IPR.


On Mon, 26 Feb 2018, stephane.litkow...@orange.com wrote:

| 
| Hello working group,
| 
|  
| 
| This email starts a two-week call for adoption on
| 
| draft-zzhang-bess-mvpn-msdp-sa-interoperation-01 [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 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 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), Matthew, Stéphane
| 
| bess chairs
| 
|  
| 
| [1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/
| 
|  
| 
| 
_
| 
| 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] Document Action: 'Usage and applicability of BGP MPLS based Ethernet VPN' to Informational RFC (draft-ietf-bess-evpn-usage-09.txt)

[The IESG]

The IESG has approved the following document:
- 'Usage and applicability of BGP MPLS based Ethernet VPN'
  (draft-ietf-bess-evpn-usage-09.txt) as Informational RFC

This document is the product of the BGP Enabled ServiceS Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/





Technical Summary

   This document discusses the usage and applicability of BGP MPLS based
   Ethernet VPN (EVPN) in a simple and fairly common deployment
   scenario. The different EVPN procedures are explained on the example
   scenario, analyzing the benefits and trade-offs of each option. This
   document is intended to provide a simplified guide for the deployment
   of EVPN networks.

Working Group Summary

  Not much to report, except that there is support from the WG.

Document Quality

  There are multiple implementations of the EVPN technology.
  This Document describes in a clear manner the use of the EVPN 
  technology building blocks and components.

Personnel

  Martin Vigoureux is the Document Shepherd
  Alvaro Retana is the Responsible Area Director

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

Re: [bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

[Jeffrey (Zhaohui) Zhang]

Support as co-author. I am not aware of related IPRs.

This is a simple solution to a practical problem for some MVPN/MSDP deployment 
scenarios.

Thanks.
Jeffrey

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of 
stephane.litkow...@orange.com
Sent: Monday, February 26, 2018 3:01 AM
To: bess@ietf.org
Subject: [bess] Call for adoption: 
draft-zzhang-bess-mvpn-msdp-sa-interoperation-01


Hello working group,



This email starts a two-week call for adoption on

draft-zzhang-bess-mvpn-msdp-sa-interoperation-01 [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 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 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), Matthew, Stéphane

bess chairs



[1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/


_



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] IPR poll on draft-ietf-bess-l2l3-vpn-mcast-mib-13

[Martin Vigoureux]

Dear BESS,

please disregard this e-mail.

Thank you
-m

Le 2018-02-26 à 4:57, Mach Chen a écrit :

Dear BESS,

This email starts an IPR call on draft-ietf-bess-l2l3-vpn-mcast-mib-13, in 
preparation to document advancement.

Are you aware of any IPR that applies to draft-ietf-bess-l2l3-vpn-mcast-mib-13?
If so, has this IPR 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 regardless of whether or not you are aware of any relevant IPR. *The 
response needs to be sent to the BESS WG mailing list.* The document will not 
advance to the next stage until a response has been received from each author 
and contributor.

If you are on the BESS WG email list but 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.

Best regards,
Mach Chen (Shepherd of this document)



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

[bess] The BESS WG has placed draft-zzhang-bess-mvpn-msdp-sa-interoperation in state "Call For Adoption By WG Issued"

[IETF Secretariat]

The BESS WG has placed draft-zzhang-bess-mvpn-msdp-sa-interoperation in state
Call For Adoption By WG Issued (entered by Stephane Litkowski)

The document is available at
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/

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

[bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

[stephane.litkowski]

Hello working group,



This email starts a two-week call for adoption on

draft-zzhang-bess-mvpn-msdp-sa-interoperation-01 [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 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 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), Matthew, Stéphane

bess chairs



[1] 
https://datatracker.ietf.org/doc/draft-zzhang-bess-mvpn-msdp-sa-interoperation/


_

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