Re: [Nfvrg] FW: Research Group Preparation (a.k.a. "Last Call") for draft-irtf-nfvrg-gaps-network-virtualization

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

Dear Gino,

Thanks a lot for your review and your comments. We'll include them in
the next revision of the draft.

Thanks!

Carlos

On Tue, 2017-06-13 at 15:32 +0200, Gino Carrozzo wrote:
> Dear authors
> 
> I also think the draft is quite comprehensive in identifying gaps and
> major work areas.
> A possible improvement area could be around sec 5 and 6.
> Here it could be interesting if authors propose some priorities for
> the open research areas.
> Also, for the sake of readability of the tables, it'd be not bad to
> better mark rows with lines, in order to make it unambiguous the
> associations between NFVRG WI and research areas.
> 
> my 2 cents
> br
> Gino
> 
> On 9 June 2017 at 15:41, <[e-mail]> wrote:
> > Dear authors, all
> > I have read the 05 version and think the document is nearly ready
> > for publication – provided some nits are corrected and
> > clarifications addressed. In the following I tried to not repeat
> > what has already been said earlier – sorry in case I didn’t succeed
> > ;-/
> >  
> > p.3:
> > load- aware => load-aware
> >  
> > p.7:
> > requires of complex => requires complex
> >  
> > p.10:
> > In addition to the these interactions => In addition to these
> > interactions
> > with each oter? etc. => with each other? etc.
> >  
> > p.15:
> > SR-IOV, NUMA, DPDK, etc : Should the acronyms be explained?
> >  
> > p.18:
> > looked as well. => looked at as well.
> >  
> > p.19:
> >  
> > a battery life thousands of times longer compared to => a battery
> > life time exceeding by a factor of thousands that of
> > if this new market provides performance that are adequate with =>
> > if the new business model enables performance that meets  [?]
> > The widespread of system and network virtualization technologies =>
> > The widespread use/discussion/practice of system and network
> > virtualization technologies
> > is responsible of the reliability => is responsible for the
> > reliability             
> >  
> > p.20:
> > situations in which an VNO requires => situations in which a VNO
> > requires
> > protocol proposed by the WEBPUSH WG => add reference here:
> > [RFC8030] ?
> > to rely on specific adatpation mechanisms => to rely on specific
> > adaptation mechanisms
> > An specific example can be => A specific example can be
> >  
> > p.21:
> > network, not necessary on the direct data path => network, not
> > necessarily on the direct data path
> >  
> > p.23:
> > administrative domain controlled by an operator => administrative
> > domain controlled by (exactly) one operator
> > Especially, if each data center is protected => This holds
> > true/this is the case in particular, if each data center is
> > protected [no complete sentence otherwise IMO]
> >  
> > p.25:
> > IMO most of the text is true in any test case and very general (not
> > VNF specific) as “The only variables in the testing should be those
> > controlling the SUT itself”
> > … the workload type the expected VNF will be => … the workload type
> > the expected VNF will be characterized by [?]
> >  
> > p.26:
> > collection of new functionality / set of functionality =>
> > collection of new functionalities / set of functionalities [?]
> >  
> > Thanks and Best Regards
> > Dirk
> > From: Nfvrg [mailto:[e-mail]] On Behalf Of Diego R.
> > Lopez
> > Sent: 28 April 2017 18:14
> > To: [e-mail]
> > Subject: [Nfvrg] Research Group Preparation (a.k.a. "Last Call")
> > for draft-irtf-nfvrg-gaps-network-virtualization
> >  
> > Hi,
> >  
> > As discussed and agreed in our meeting in Chicago, this message is
> > to open the equivalent of a last-call for our draft on NFV research
> > challenges (https://datatracker.ietf.org/doc/draft-irtf-nfvrg-gaps-
> > network-virtualization/). Note I use the term “equivalent to last-
> > call”, as the IRTF process described in RFC 5743 uses the term
> > “Research Group Preparation”. Let me remind you the summarized IRTF
> > process as described in RFC 5743:
> >     o  The Research Group (RG) performs a thorough technical and
> >       editorial review of the document and agrees it should be
> >       published.
> >  
> >    o  The Internet Research Steering Group (IRSG) reviews the
> > document
> >       and approves it for publication.
> >    o  The Internet Engineering Steering Group (IESG) reviews the
> >       document to assure that there are no conflicts with current
> > or
> >       expected standardization activities.
> >  
> >    o  The document is submitted to the RFC Editor for publication.
> > So we are starting the first step above, and all of you are
> > encouraged to review the document and share your comments and
> > opinions about moving it forward towards publication. Since it is
> > advisable to put a deadline for this kind of process, let’s go for
> > a one month period, that is until the 28th May.
> >  
> > 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
> > 
> 
> 
> 
> -- 
> ==============================================================
>   Dr. Gino Carrozzo
>   Deputy Head of R&D
> 
>   mobile    : [phone]
>   landline  : [phone]                  
>   fax         : [phone]                  
>   e-mail    : [e-mail]               
>   web       : www.nextworks.it               
>   address   : Nextworks s.r.l.
>                   via Livornese, 1027                        
>                   56122 S.Piero a Grado, Pisa, ITALY                
>      
> ==============================================================