Re: [Nfvrg] Trying to organize the live documents in NFVRG

[이승익 <[e-mail]>]

Ramki and Diego,

I think that your proposal below does make sense and looks quite productive.

As per the drafts listed in https://datatracker.ietf.org/rg/nfvrg/documents/,
I found several {RG, individual} drafts whose main topics are within “Policy based Resource Management” – in my perspective - as follows:

- draft-irtf-nfvrg-nfv-policy-arch-01, Policy Architecture and Framework for NFV Infrastructures
- draft-irtf-nfvrg-resource-management-service-chain-01, Resource Management in Service Chaining
- draft-bernini-nfvrg-vnf-orchestration-01, VNF Pool Orchestration For Automated Resiliency in Service Chains
- draft-krishnan-nfvrg-policy-based-rm-nfviaas-05, NFVIaaS Architectural Framework for Policy Based Resource Placement and Scheduling

As they share the common keywords: “policy and resource management” in the text, they may go a good compromise IMHO.
But they have different objectives and details, and this makes me a little concerned for losing a focus in the merged draft.

Regards,
Seungik.

From: Nfvrg [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Thursday, September 17, 2015 2:15 AM
To: [e-mail]; [e-mail]
Subject: Re: [Nfvrg] Trying to organize the live documents in NFVRG

Dear All,

A gentle reminder, we would love to hear your comments on this topic. We also put down our thoughts on individual drafts and we got several responses from the authors; would like to hear from the authors of the other drafts too.

Thanks,
Ramki

From: Nfvrg [mailto:[e-mail]] On Behalf Of DIEGO LOPEZ GARCIA
Sent: Tuesday, September 08, 2015 3:22 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [Nfvrg] Trying to organize the live documents in NFVRG

Hi,

Ramki and I have been discussing how to organize the live documents we have in the NFVRG, with the idea of maximizing productivity and avoiding the dispersion of efforts by a multiplicity of unrelated documents. Since the RG charter is wide enough to accommodate many different contributions, we have agreed to structure most documents around the following classes, according with the long-term goals:

* Those addressing one of the special interest areas and aimed at becoming a permanent contribution. We propose to keep one document per each area, intended to become an RFC once the work in that area is considered complete. Authors of such documents will be required to merge them with other related documents once they are adopted by the RG. The chairs will identify editors for each of these documents.
Just for you to remember, the four interest areas (identified in the RG wiki) are "Policy based Resource Management", "Analytics for Visibility and Orchestration", "Virtual Network Function (VNF) Performance Modeling to facilitate transition to NFV", and “Security and Service Verification”. The lack of proposals in the area of performance modeling is making us think of changing this area for another one (though this is something we need to discuss on a separate thread)

* Those addressing general issues of interest to the community, but related with a concrete points in time. Typical examples ara gap analysis or challenge reports (live documents per se) or project reports (associated to the project lifecycle) They will be acknowledged by adopting them once the community thinks they are mature enough to provide a clear value.

* General documents (specific findings, updates, etc) presented for information to and assessment by the community

We hope you’ll find this proposal agreeable, so Ramki and I can start structuring the agenda of our coming meetings around it, and begin to prepare a proposal to classify the live documents, and take the other necessary actions to apply the proposal.

Any kind of comments, suggestions and expression of support would be extremely welcome, specially the latter ones…

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: [e-mail]<mailto:[e-mail]>
Tel:    [phone]
Mobile: [phone]
----------------------------------


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição