Hi Tina, Yes, the O in OAM stands for Operations. This does not mean however that all operational requirements are being met by defining and deploying OAM protocols.
Regards, Dan From: [email protected] [mailto:[email protected]] On Behalf Of Tina TSOU Sent: Wednesday, August 28, 2013 8:50 AM To: Romascanu, Dan (Dan) Cc: Bocci, Matthew (Matthew); [email protected] Subject: Re: [nvo3] Poll for WG adoption of draft-ashwood-nvo3-operational-requirement-03 Dear Dan, Thank you for raising your concern. You said "Operations means more than just OAM." However, O of OAM stands for Operations literally. I understand RFC5706, and quote it very often. Thank you, Tina On Aug 25, 2013, at 1:04 AM, "Romascanu, Dan (Dan)" <[email protected]<mailto:[email protected]>> wrote: Hi, I am confused. The charter of the NVO3 WG speaks about writing an Informational document that describes Operational Requirements. The I-D draft-ashwood-nvo3-operational-requirement-03.txt is not such a document, excepting its title. It takes as a model RFC 6136 which is an OAM requirements document. There is a clear difference between Operational Requirements and OAM Requirements. When we talk about Operational Requirements I for a new protocol or for protocol extensions I would expect to find information and derived requirements about operational environments, installation and set-up, migration path from current deployed networks, relation, coexistence and interaction with already deployed protocol, and impact on network operations. Yes, as a result of the operational requirements there may be a need to deploy OAM, and OAM requirements may be part of the solution and be described in the same document or in different documents, but Operations means more than just OAM. I do not believe that in its current form this draft is a good enough basis for the chartered document on operational requirements. Regards, Dan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bocci, Matthew (Matthew) Sent: Friday, August 23, 2013 6:19 PM To: [email protected]<mailto:[email protected]> Subject: [nvo3] Poll for WG adoption of draft-ashwood-nvo3-operational-requirement-03 This email begins a two week poll to help the chairs determine if there is consensus to adopt draft-ashwood-nvo3-operational-requirement-03.txt as an NVO3 working group draft. The draft can be found here: http://tools.ietf.org/id/draft-ashwood-nvo3-operational-requirement-03.txt Please read the draft and indicate to the list if you support adoption, or if you do not support adoption (giving reasons). Please note that this is only a call for adoption. There needs to be consensus that this draft is a good basis for the work, but it does not need to be perfect at this stage. The poll for adoption will close in two weeks time, on Friday 6th September. Best regards, Matthew and Benson
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
