Re: [Nfvrg] RG adoption of draft-bernardos-nfvrg-gaps-network-virtualization

[Carlos Jesús Bernardos Cano <[e-mail]>]

Dear Kostas,

Thanks for your review and positive comments. We'll address them in the
next revision of the document. Please find some additional comments
from our side in line below.

On Mon, 2015-12-14 at 10:48 +0100, Kostas Pentikousis wrote:
> Dear Chairs, all,
>  
> Personally, I would have liked to see a bit more of RFC 7426 aspects
> incorporated. RFC 7426 is rather minimally presented now, and I’m not
> sure why the sibling SDNRG work appears so late in the document (sec.
> 4.11). I think that RFC 7426 should be part of the early parts of the
> document, including sec. 2 (Terminology, e.g. CP, MP, and network
> device etc. are very well defined therein) and sec. 3 (Background).
> I’m not convinced why “architectures” from other SDOs have to take
> precedence also in terms of diagrams included in this I-D.

[Carlos] We'll incorporate terms from 7426 into our terminology
section, which I agree now it is mostly NFV-based. We will also move
SDNRG work before in the document, as well as include the architecture
diagram into our section 3.2 (which now is based on ONF).

>  
> With respect to IPPM (sec. 4.9), there’s ongoing effort to define a
> YANG model for the protocol (see
> https://datatracker.ietf.org/doc/draft-cmzrjp-ippm-twamp-yang/). I
> think this fits very well (along with other similar efforts) in the
> automation and orchestration strand of this document and is currently
> not covered.

[Carlos] OK, thanks. We'll add it.

>  
> Editorial comments: First, I think the abstract needs to be reduced
> (remove first 2 paragraphs maybe) to focus on the contribution of
> this document. Second, although I like the current grouping from the 

[Carlos] OK. We'll reduce the abstract in the next revision of the
draft.

> pov of a survey, I think it that it does not address the needs of the
> primary audience in my mind. I propose that instead of making the
> analysis on a per-SDO/WG line of work, the respective sections should
> be edited to address research and standardization topics, which
> admittedly may be covered by different groups. After all, this
> document cannot authoritatively do the gap analysis for the
> respective SDOs/WGs, but it can identify missing elements and future
> work on a per-topic basis. Third, I think a broader coverage of 

[Carlos] We fully agree on this. We were actually thinking of doing a
change of the way we present the content. We are not yet 100% sure on
how we'll do it, but it is aligned with your view.

[Carlos] Related to this, we are also considering giving the document
also a flavor of "research challenges" (similar to what is done
in draft-irtf-icnrg-challenges). This will probably increase the
usefulness of the document and will be very helpful for the RG. What do
you think about this idea?

> research work in this area should be included in an upcoming version
> of the document. Finally, I guess the authors will update the draft
> as there have been a number of developments since September (an
> obvious one is the publication of RFC 7665).

[Carlos] OK. Thanks. We'll do it.

>  
> I commented positively on this draft before, and I think it should be
> adopted by NFVRG . It’s clear that the authors have done a very good
> job so far, but the document will benefit the most if this becomes
> the collective result of the RG. That means that more points of view
> could be integrated as well.

[Carlos] Thanks.

Kind regards,

Carlos

>  
> Best regards,
>  
> Kostas
>  
> From: DIEGO LOPEZ GARCIA [mailto:[e-mail]] 
> Sent: Sonntag, 6. Dezember 2015 01:06
> To: [e-mail]
> Subject: [Nfvrg] RG adoption of draft-bernardos-nfvrg-gaps-network-
> virtualization
>  
> Hi,
>  
> This message is to open a two-week adoption call for draft-bernardos-
> nfvrg-gaps-network-virtualization, as a non-permanet document not
> specifically associated with any of the special interest areas.
>  
> Please indicate in your comments “support” or “no support” and
> discuss how this draft will contribute to a better understanding of
> NFV technologies and their relation with other ongoing work.
>  
> The current draft is available at:
>  
> https://datatracker.ietf.org/doc/draft-bernardos-nfvrg-gaps-network-v
> irtualization/
>  
> 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]
> 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
> _______________________________________________
> Nfvrg mailing list
> [e-mail]
> https://www.irtf.org/mailman/listinfo/nfvrg