Support

> -----Original Message-----
> From: Jeffrey (Zhaohui) Zhang [mailto:[email protected]]
> Sent: Friday, October 04, 2013 3:36 PM
> To: Jain, Pradeep G (Pradeep); Sameer Gulrajani; Andy Green; ASIF, 
> SAUD
> Cc: Marco Rodrigues; Pavan Kurapati; Robert Kebler; Kurt Windisch
> Subject: FW: Heads-up [Re: Poll for adoption: draft-zzhang-l2l3-vpn- 
> mcast-mib]
> 
> Please round up some support for the following adoption call.
> 
> The MVPN MIB depends on it - it has some objects pulled out of the 
> MVPN MIB so that they can be used for both MVPN MIB and VPLS MCAST MIB.
> 
> We need it to be adopted before we can move MVPN MIB forward.
> 
> Thanks.
> Jeffrey
> 
> -----Original Message-----
> From: Martin Vigoureux [mailto:[email protected]]
> Sent: Friday, October 04, 2013 5:47 AM
> To: [email protected]
> Subject: Heads-up [Re: Poll for adoption: draft-zzhang-l2l3-vpn-mcast- 
> mib]
> 
> All,
> 
> we have not seen a lot of reaction to this adoption poll. We'd like to 
> give it a second try.
> 
> Please express your opinion (in favour or opposed to).
> 
> Extension of the poll runs until Oct 11th.
> 
> Martin
> (for the L3VPN co-chairs)
> 
> Le 05/09/2013 16:40, [email protected] a écrit :
> > Hello working group,
> >
> > This email starts a two-week poll on possible adoption of
> > draft-zzhang-l2l3-vpn-mcast-mib-00 [1] as a working group item.
> >
> > Please send comments to the list and state if you support adoption 
> > or not (in the later case, please also state the reasons).
> >
> > *** Note that what is proposed is that this document becomes a 
> > common foundation for the already adopted L3VPN multicast MIB
> > (draft-ietf-l3vpn-mvpn-mib) and for an L2VPN multicast MIB. Hence,
> the
> > L2VPN will be noticed and asked for feedback on the adoption of this 
> > document. ***
> >
> > This poll runs until September 20th.
> >
> >
> > *Coincidentally*, we are also polling for knowledge of any IPR that 
> > applies to this draft, 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* please 
> > respond to this email whether or not you are aware of any relevant
> IPR.
> > The draft will not be adopted until a response has been received 
> > from each author and contributor.
> >
> > If you are on the L3VPN WG mailing 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.
> >
> > Thank you,
> >
> > Martin & Thomas
> > l3vpn chairs
> >
> > [1] http://tools.ietf.org/html/draft-zzhang-l2l3-vpn-mcast-mib-00
> >
> ______________________________________________________________________
> _ __________________________________________________
> >
> > 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.
> >

Reply via email to