Hi Stephane, Matthew:

Is there a process for WG call (or WG LC) call that you are following? I 
thought it is based on maturity of the draft, adoptions of the draft, history 
of the draft (how long it has been around), and a public request for it.

I am a co-author of the above draft and naturally I support WG call for it; 
however, I don’t see any request for it. Furthermore, it is relatively a new 
draft. Whereas, the draft that I requested for a WG call last week is very 
mature and has already been implemented by a number of vendors. So, I’d like to 
better understand the criteria that you use for deciding WG call.


From: BESS <bess-boun...@ietf.org> on behalf of "stephane.litkow...@orange.com" 
Date: Monday, February 19, 2018 at 2:39 AM
To: "bess@ietf.org" <bess@ietf.org>
Cc: "bess-cha...@ietf.org" <bess-cha...@ietf.org>
Subject: [bess] Call for adoption: draft-skr-bess-evpn-pim-proxy

Hello working group,

This email starts a two-week call for adoption on

draft-skr-bess-evpn-pim-proxy-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 5th 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-skr-bess-evpn-pim-proxy/


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

Reply via email to