[Nsi-wg] Full paper on NSI for TNC12 conference

[Jerry Sobieski]

Yes I concur.   Which sections would you like me to work on?
J

On 3/23/12 11:00 AM, Radek Krzywania wrote:
>
> Hi Jerry,
>
> Regarding high-level paper I agree, yet the protocol life cycle is 
> quite important in NSI context. I would not go into too much details, 
> that’s why I proposed to do so as an example on success scenario (so 
> we can skip some states or more complex transitions). I support GLIF 
> Automated GOLE efforts to be included. We can put it into demo and 
> lessons learned sections, unless you prefer to make separate section 
> for deployment (well, demos were deployments of prototypes, that’s why 
> I would put it there).
>
> Showing community support is as well good idea. I am not sure, but 
> maybe future work is the right place to put it. What do you think?
>
> Best regards
>
> Radek
>
> ________________________________________________________________________
>
> Radoslaw Krzywania                      Network Research and Development
>
>                                            Poznan Supercomputing and
>
> radek.krzywania at man.poznan.pl 
> <mailto:radek.krzywania at man.poznan.pl>                   Networking Center
>
> +48 61 850 25 26 http://www.man.poznan.pl
>
> ________________________________________________________________________
>
> *From:*Jerry Sobieski [mailto:jerry at nordu.net]
> *Sent:* Friday, March 23, 2012 1:32 PM
> *To:* radek.krzywania at man.poznan.pl
> *Cc:* nsi-wg at ogf.org
> *Subject:* Re: [Nsi-wg] Full paper on NSI for TNC12 conference
>
> Hi Radek-
> I am willing to help on this...  Some thoughts:
>
> In the "current" section (v1.*)...
> I would suggest this be a relatively high level paper - not getting 
> into the specifics of WSDLs or state machines (too much detail)- but 
> keeping to the higher layer inter-domain purpose for NSI, its 
> technology agnostic approach - how that works and what that brings, 
> the connection life cycle, basic primitive functions, the service tree 
> and tree/chain processing, scheduled and on-demand, integrated AAI for 
> every interaction, the NSI topology model, and the strategies (such as 
> security and scalability) that helped define how these features were 
> implemented.  (This paper should entice readers to learn more - not 
> teach them all the dirty details:-)
>
>
> We should put a section in to describe the GLIF Automated GOLE effort 
> that has deployed NSI and has learned a great deal in doing so - where 
> it functions well, where we had problems, etc. The point of this 
> section is to show that NSI is not simply a chalk board exercise, but 
> is being tested in the field and experience feeding back directly into 
> the protocol and standard.
>
> Given that we have some clarity now on version 2.0, we should (IMO) 
> include a brief high level summary of those features and why they are 
> important in the "futures" section.  I would also include the drive in 
> the working groups towards a common topology model (i.e. NML), ongoing 
> work on a common topology distribution process, work going on in GLIF 
> to find a comprehensive NSI conformant performance verification model, 
> etc ... (Jeroen and I will be presenting a paper on topology issues, 
> so we don't need a lot of detail on this topic here - just enough to 
> show that NSI sees a broader picture than simply the CS provisioning 
> protocol.)
>
> I don't know where is best, but it would be useful also to indicate 
> which organizations have expressed a commitment to deploying NSI based 
> services in their networks.   Certainly some have committed to doing 
> so, and other have gone a step further with estimated deployment 
> timelines...  Presenting this commitment is an important aspect to 
> campus or regional CIOs etc that are wondering about future directions.
>
> Finally, I think it is important (especially to the "suits" attending 
> TNC) to emphasize the Open international process for the NSI work and 
> the community consensus building that this engenders - resulting in 
> broader adoption -> which is critical for global functionality in an 
> inter-domain services world.  (We are not just addressing networking 
> organizations, but increasingly IT organizations...)
>
> ...just some ideas...
> Jerry
>
> On 3/23/12 7:34 AM, Radek Krzywania wrote:
>
> Dear all,
> The deadline for TNC12 full paper is 16 April, so we don't have too much time (as usual). In the attachment I've placed a drafted template for this article, based on TERENA template. I would like to follow below schema:
> - ask yourself if you want to contribute to the paper :) - deadline ASAP
> - Browse attached ToC and see what and where you can contribute, please update ToC if you feel there is something missing and you may fill it - deadline - Wed 28.03 (we can finalize that via email on during NSI call)
> - People will be assigned to particular sections based on expressed interest - Thu 28.03
> - Drafted contributions delivered - Fri 06.04
> - Finalization on the paper - by Fri 13.04
> - Paper submission - Mon 16.04
>   
> Comments are more than welcome. I'll take care of merging contributions and take care of formatting and versioning. I suppose we could use NSI forge to place docs in one place.
>   
> Best regards
> Radek
>   
> ________________________________________________________________________
> Radoslaw Krzywania                      Network Research and Development
>                                             Poznan Supercomputing and
> radek.krzywania at man.poznan.pl  <mailto:radek.krzywania at man.poznan.pl>                    Networking Center
> +48 61 850 25 26http://www.man.poznan.pl
> ________________________________________________________________________
>   
>   
>
>
>
>
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org  <mailto:nsi-wg at ogf.org>
> https://www.ogf.org/mailman/listinfo/nsi-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20120323/bd47f1d1/attachment.html>