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

2017-06-13 Thread Patrice Brissette (pbrisset) 
Support!

Regards,
Patrice Brissette


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


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

Re: [bess] Call for adoption: draft-rabadan-bess-evpn-pref-df

2017-06-13 Thread Shah, Himanshu 
Support.

Thanks,
Himanshu

From: BESS  on behalf of "Thomas com>" 

Organization: Orange
Date: Tuesday, June 6, 2017 at 9:44 AM
To: "bess@ietf.org" 
Cc: "draft-rabadan-bess-evpn-pref...@ietf.org" 

Subject: [bess] Call for adoption: draft-rabadan-bess-evpn-pref-df

Hello working group,

This email starts a two-week call for adoption on
draft-rabadan-bess-evpn-pref-df-02 [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 20th 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 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.

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-rabadan-bess-evpn-pref-df/

_

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

[bess] Protocol Action: 'Virtual Private Wire Service support in Ethernet VPN' to Proposed Standard (draft-ietf-bess-evpn-vpws-14.txt)

2017-06-13 Thread The IESG 
The IESG has approved the following document:
- 'Virtual Private Wire Service support in Ethernet VPN'
  (draft-ietf-bess-evpn-vpws-14.txt) as Proposed Standard

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-vpws/





Technical Summary

   This document describes how EVPN can be used to support Virtual
   Private Wire Service (VPWS) in MPLS/IP networks. EVPN enables the
   following characteristics for VPWS: single-active as well as all-
   active multi-homing with flow-based load-balancing, eliminates the
   need for traditional way of Pseudowire (PW) signaling, and provides
   fast protection convergence upon node or link failure.

Working Group Summary

  This document was processed by the bess WG; nothing
  specific to highlight.

Document Quality

  At least 3 major vendors have implemented this specification.

Personnel

   Document Shepherd: Jeffrey Zhang (zzh...@juniper.net)
   Responsible Area Director: Alvaro Retana (aret...@cisco.com)

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

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

2017-06-13 Thread Jeff Tantsura 
Yes/support 

Regards,
Jeff

> On Jun 12, 2017, at 23:40, 
> On 6/6/17, 10:11 AM, "BESS on behalf of Martin Vigoureux"
>  wrote:
> 
>> 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