Re: [spring] Poll for adoption: draft-kumar-spring-sr-oam-requirement

["Nagendra Kumar Nainar (naikumar)" <[e-mail]>]

Hi,

We have submitted the draft as WG document.

https://datatracker.ietf.org/doc/draft-ietf-spring-sr-oam-requirement/

Thanks,
Nagendra

From: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date: Monday, June 29, 2015 at 1:13 PM
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: Re: [spring] Poll for adoption: draft-kumar-spring-sr-oam-requirement

Hello,

The poll has ended and there is sufficient support to make this a working group document.

Authors, please re-submit as draft-ietf-spring-sr-oam-requirement-00 with the same technical content.

Thank you,
Bruno & John

From: spring [mailto:[e-mail]] On Behalf Of [e-mail]<mailto:[e-mail]>
Sent: Wednesday, June 10, 2015 5:06 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [spring] Poll for adoption: draft-kumar-spring-sr-oam-requirement

Hello working group,

This email starts a two-week poll on adopting draft-kumar-spring-sr-oam-requirement as a working group item.
“OAM Requirements for Segment Routing Network“
https://tools.ietf.org/html/draft-kumar-spring-sr-oam-requirement-03

Please send comments to the list and state if you support adoption or not (in the latter case, please also state the reasons).

This poll runs until 25/06/2015.


*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 and indicate 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 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
Bruno & John



_________________________________________________________________________________________________________________________



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.