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

[Guofeng]

I’m not aware of any IPR.

Thanks,
Feng



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

[bess] Last Call: (Framework for EVPN Designated Forwarder Election Extensibility) to Proposed Standard

[The IESG]

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'Framework for EVPN Designated Forwarder
Election Extensibility'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
i...@ietf.org mailing lists by 2018-12-18. Exceptionally, comments may be
sent to i...@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   The Designated Forwarder (DF) in EVPN networks is the Provider Edge
   (PE) router responsible for sending broadcast, unknown unicast and
   multicast (BUM) traffic to a multi-homed Customer Equipment (CE)
   device, on a given VLAN on a particular Ethernet Segment (ES). The DF
   is selected out of a list of candidate PEs that advertise the same
   Ethernet Segment Identifier (ESI) to the EVPN network. By default,
   EVPN uses a DF Election algorithm referred to as "Service Carving"
   and it is based on a modulus function (V mod N) that takes the number
   of PEs in the ES (N) and the VLAN value (V) as input. This default DF
   Election algorithm has some inefficiencies that this document
   addresses by defining a new DF Election algorithm and a capability to
   influence the DF Election result for a VLAN, depending on the state
   of the associated Attachment Circuit (AC). In addition, this document
   creates a registry with IANA, for future DF Election Algorithms and
   Capabilities. It also presents a formal definition and clarification
   of the DF Election Finite State Machine.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/ballot/


No IPR declarations have been submitted directly on this I-D.




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

[bess] Comment on draft-ietf-bess-service-chaining-06

[Andrew G. Malis]

I just read the new revision of draft-ietf-bess-service-chaining. Although
the draft doesn't use the RFC 8300 NSH, it could very easily take advantage
of features provided by the NSH (such as metadata) by adding NSH over MPLS
as defined in draft-ietf-mpls-sfc-encapsulation to the list of
encapsulations listed in section 2.5. And this draft provides an excellent
label distribution mechanism for NSH over MPLS. It would make a lot of
sense to add a reference to draft-ietf-mpls-sfc-encapsulation in the list
of encapsulations in section 2.5.

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

[bess] I-D Action: draft-ietf-bess-service-chaining-06.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   : Service Function Chaining using Virtual Networks with 
BGP VPNs
Authors : Rex Fernando
  Stuart Mackie
  Dhananjaya Rao
  Bruno Rijsman
  Maria Napierala
  Thomas Morin
Filename: draft-ietf-bess-service-chaining-06.txt
Pages   : 41
Date: 2018-12-04

Abstract:
   This document describes how service function chains (SFC) can be
   applied to traffic flows using routing in a virtual (overlay) network
   to steer traffic between service nodes.  Chains can include services
   running in routers, on physical appliances or in virtual machines.
   Service chains have applicability at the subscriber edge, business
   edge and in multi-tenant datacenters.  The routing function into SFCs
   and between service functions within an SFC can be performed by
   physical devices (routers), be virtualized inside hypervisors, or run
   as part of a host OS.

   A BGP control plane for route distribution is used to create virtual
   networks implemented using IP MPLS, VXLAN or other suitable
   encapsulation, where the routes within the virtual networks cause
   traffic to flow through a sequence of service nodes that apply packet
   processing functions to the flows.

   Two techniques are described: in one the service chain is implemented
   as a sequence of distinct VPNs between sets of service nodes that
   apply each service function; in the other, the routes within a VPN
   are modified through the use of special route targets and modified
   next-hop resolution to achieve the desired result.

   In both techniques, service chains can be created by manual
   configuration of routes and route targets in routing systems, or
   through the use of a controller which contains a topological model of
   the desired service chains.

   This document also contains discussion of load balancing between
   network functions, symmetric forward and reverse paths when stateful
   services are involved, and use of classifiers to direct traffic into
   a service chain.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-service-chaining/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-service-chaining-06
https://datatracker.ietf.org/doc/html/draft-ietf-bess-service-chaining-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-service-chaining-06


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] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

[stephane.litkowski]

Done, I have marked the –ietf- document replacing the individual one. The IPR 
is now inherited.

From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Tuesday, December 04, 2018 20:53
To: LITKOWSKI Stephane OBS/OINIS; bess@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-virtual-eth-segment

Hi Stephane,

It seems like the IPR that I was talking about has already been disclosed in 
April of this year. The disclosure is on 
draft-sajassi-bess-evpn-virtual-eth-segment-03.
 Since the history of its WG draft version doesn’t show the individual draft 
revisions, the IPR doesn’t appear for WG draft version. Can you fix it so that 
the history of the individual drafts appear on the WG draft history?

Regards,
Ali

From: BESS  on behalf of Cisco Employee 

Date: Monday, December 3, 2018 at 10:29 PM
To: "stephane.litkow...@orange.com" , 
"bess@ietf.org" 
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-virtual-eth-segment



There is one IPR related to this draft that I thought it was disclosed but it 
wasn’t. I put request  for it to be disclosed ASAP. The term for it is the same 
as any other Cisco IPR disclosure.
Regarding implementation, this draft has been implemented in Cisco products for 
quite some time.

Regards,
Ali

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

Date: Monday, December 3, 2018 at 2:43 AM
To: "bess@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-virtual-eth-segment


Hello Working Group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-virtual-eth-segment [1]



This poll runs until *the 17th of December*.



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.



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-virtual-eth-segment/



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



_



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] The BESS WG has placed draft-sajassi-bess-evpn-virtual-eth-segment in state "Adopted by a WG"

[IETF Secretariat]

The BESS WG has placed draft-sajassi-bess-evpn-virtual-eth-segment in state
Adopted by a WG (entered by Stephane Litkowski)

The document is available at
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-virtual-eth-segment/

___
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-virtual-eth-segment

[Ali Sajassi (sajassi)]

Hi Stephane,

It seems like the IPR that I was talking about has already been disclosed in 
April of this year. The disclosure is on 
draft-sajassi-bess-evpn-virtual-eth-segment-03.
 Since the history of its WG draft version doesn’t show the individual draft 
revisions, the IPR doesn’t appear for WG draft version. Can you fix it so that 
the history of the individual drafts appear on the WG draft history?

Regards,
Ali

From: BESS  on behalf of Cisco Employee 

Date: Monday, December 3, 2018 at 10:29 PM
To: "stephane.litkow...@orange.com" , 
"bess@ietf.org" 
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-virtual-eth-segment



There is one IPR related to this draft that I thought it was disclosed but it 
wasn’t. I put request  for it to be disclosed ASAP. The term for it is the same 
as any other Cisco IPR disclosure.
Regarding implementation, this draft has been implemented in Cisco products for 
quite some time.

Regards,
Ali

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

Date: Monday, December 3, 2018 at 2:43 AM
To: "bess@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-evpn-virtual-eth-segment


Hello Working Group,



This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-virtual-eth-segment [1]



This poll runs until *the 17th of December*.



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.



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-virtual-eth-segment/



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



_



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] PLEASE LOOK: minor change to draft-ietf-bess-evpn-df-election-framework-05 => two weeks poll to get feedback

[Vigoureux, Martin (Nokia - FR/Paris-Saclay)]

WG,

I have asked the authors to submit a new revision with the new text.
I know this is before the end of this additional review period but I 
wanted to have a (thin) chance to get this on the last IESG telechat of 
2018.
The draft is moving to IETF LC so you still have the opportunity to 
express your opinions on the recent change.

-m

Le 2018-11-21 à 10:08, stephane.litkow...@orange.com a écrit :
> Hi Ali,
> 
> Thanks a lot for your email.
> 
> Speaking as chair, could you please highlight to the working group the 
> rationale of the change and associated use case ? Just to give the context…
> 
> To WG Folks,
> 
> Please review this change with care. There are two points that I would 
> like to highlight:
> 
> -We need to ensure that there is no current implementation using the 
> value 255. Please raise your voice if you are aware of one.
> 
> -The encoding of the mcast DF election algorithm could now be 
> decorrelated from the base DF alg (applicable to Broadcast and Unknown 
> traffic). The proposed encoding uses 3 bits for the mcast DF alg. We 
> have to ensure that:
> 
> o3 bits is enough
> 
> oThere will “never” (at least not mid term) be a requirement for 
> variable parameters for mcast DF election (like in DF pref draft).
> 
> I will let some time to think about this change and raise your support 
> or concerns.
> 
> The poll starts now and will end on Dec 5^th .
> 
> This DF election framework will be an important component of EVPN and we 
> need to ensure that we are providing the required level of flexibility 
> to address the different use cases.
> 
> Thanks !
> 
> *From:*Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
> *Sent:* Wednesday, November 21, 2018 00:25
> *To:* bess@ietf.org
> *Cc:* bess-cha...@ietf.org
> *Subject:* minor change to draft-ietf-bess-evpn-df-election-framework-05
> 
> Folks,
> 
> The authors of  the above draft are purposing a minor change to the 
> draft and since the draft is currently under review by IESG, the chair 
> has asked to send an email to the WG to solicit inputs and ensuring that 
> there is no objection. The proposed change is as follow:
> 
> Currently, the above draft defines an eight-bit “DF Alg” field as shown 
> in the following figure. The proposed change is to reduce the eight-bit 
> field to a five-bit field.
> 
> *** OLD Text
> 
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 
> 9 0 1
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>   | Type=0x06     | Sub-Type(0x06)|   DF Alg  |
> Bitmap |
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>   | Bitmap    |
> Reserved   |
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>     o DF Alg (1 octet) - Encodes the DF Election algorithm values
> 
>   (between 0 and 255) that the advertising PE desires to use for the
> 
>   ES. This document requests IANA to set up a registry called "DF Alg
> 
>   Registry" and solicits the following values:
> 
>   - Type 0: Default DF Election algorithm, or modulus-based algorithm
> 
>     as in [RFC7432 ].
> 
>   - Type 1: HRW algorithm (explained in this document).
> 
>   - Types 2-254: Unassigned.
> 
>   - Type 255: Reserved for Experimental Use.
> 
> ***NEW Text
> 
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 
> 9 0 1
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>   | Type=0x06     | Sub-Type(0x06)| RSV |  DF Alg  |
> Bitmap    |
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>   | Bitmap    |
> Reserved   |
> 
>   
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>     o DF Alg *(5 bits)* - Encodes the DF Election algorithm values
> 
> *(between 0 and 31)* that the advertising PE desires to use for the
> 
>   ES. This document requests IANA to set up a registry called "DF Alg
> 
>   Registry" and solicits the following values:
> 
>   - Type 0: Default DF Election algorithm, or modulus-based algorithm
> 
>     as in [RFC7432 ].
> 
>   - Type 1: HRW algorithm (explained in this document).
> 
> * - Types 2-30: Unassigned.*
> 
> **
> 
> * - Type 31: Reserved for Experimental Use.*
> 
> **
> 
> **
> 
> The remaining 3-bits of that octet (bits 16, 17, and 18 in the above 
> figure) will be used by per-mcast-flow-df-election and will be expanded 
> and described there and will be discussed in the next IETF as usual at 
> the BESS WG session.
> 
> Regards,
> 
> Ali & other co-authors
> 
> 

[bess] I-D Action: draft-ietf-bess-evpn-df-election-framework-06.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   : Framework for EVPN Designated Forwarder Election 
Extensibility
Authors : Jorge Rabadan
  Satya Mohanty
  Ali Sajassi
  John Drake
  Kiran Nagaraj
  Senthil Sathappan
Filename: draft-ietf-bess-evpn-df-election-framework-06.txt
Pages   : 27
Date: 2018-12-04

Abstract:
   The Designated Forwarder (DF) in EVPN networks is the Provider Edge
   (PE) router responsible for sending broadcast, unknown unicast and
   multicast (BUM) traffic to a multi-homed Customer Equipment (CE)
   device, on a given VLAN on a particular Ethernet Segment (ES). The DF
   is selected out of a list of candidate PEs that advertise the same
   Ethernet Segment Identifier (ESI) to the EVPN network. By default,
   EVPN uses a DF Election algorithm referred to as "Service Carving"
   and it is based on a modulus function (V mod N) that takes the number
   of PEs in the ES (N) and the VLAN value (V) as input. This default DF
   Election algorithm has some inefficiencies that this document
   addresses by defining a new DF Election algorithm and a capability to
   influence the DF Election result for a VLAN, depending on the state
   of the associated Attachment Circuit (AC). In addition, this document
   creates a registry with IANA, for future DF Election Algorithms and
   Capabilities. It also presents a formal definition and clarification
   of the DF Election Finite State Machine.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-df-election-framework/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-framework-06
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-df-election-framework-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-df-election-framework-06


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

[bess] Last Call: ((PBB-)EVPN Seamless Integration with (PBB-)VPLS) to Proposed Standard

[The IESG]

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - '(PBB-)EVPN Seamless Integration with
(PBB-)VPLS'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
i...@ietf.org mailing lists by 2018-12-18. Exceptionally, comments may be
sent to i...@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This draft specifies procedures for backward compatibility of
   Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN (PBB-
   EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider
   Backbone Bridge VPLS (PBB-VPLS) solutions (PBB-)VPLS. It also
   provides mechanisms for seamless integration of these two
   technologies in the same MPLS/IP network on a per-VPN-instance basis.
   Implementation of this draft enables service providers to introduce
   (PBB-)EVPN PEs in their brown-field deployments of (PBB-)VPLS
   networks.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpls-seamless-integ/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpls-seamless-integ/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2472/





___
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

[stephane.litkowski]

I’m not aware of any IPR

From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com]
Sent: Monday, December 03, 2018 15:53
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



_

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