[Sdnp] updated SDN problem statement draft

[Thomas D Nadeau]

On Mar 22, 2012, at 4:05 AM, zhang.fei3 at zte.com.cn wrote:

> 
> Hi Ping 
> 
> This version is much clear compared to verion 01 from my side, thanks for the efforts. 
> 
> Would you like to consider my comments listed below? 
> 
> In section 3.1 
> 
> The draft said "Network Topology Database: This is a part of the inventory management that service/application providers maintain." 
> 
> According to my understanding, the Network Topology Database can include LSDB(coming from ospf and/or BGP) and TED (coming from BGP-TE, OSPF-TE, ISIS-TE,NMS, or manual configuration), even the policy and location information, but all these information should be maintained by the serrice providers. What is the information that application 
> providers maintain? 
> 
> Can you make it clear? 
> 
> The title of section 4.3. is "Virtual Data Center", should it be "L3 virtualization"? 

while you want to include topology information i dont think we want to replicate all of the ospf, isis, bgp, etc... information inside of the orchestrator.  topology to me, is a list of nodes, their links' addresses, and what other nodes they are connected to.  Basically the idea is to include sufficient information to navigate through the tree of nodes at that network layer, but detailed information is had by talking to those hosts directly (or their ems/nms). 

tom

> 
> 
> Best 
> 
> Fei 
> 
> 
> Ken Gray <kgray at juniper.net> 
> 发件人:  sdnp-bounces at lucidvision.com
> 2012-03-14 23:22
> 
> 收件人
> Ping Pan <ping at pingpan.org>, sdnp <sdnp at lucidvision.com>
> 抄送
> 主题
> Re: [Sdnp] updated SDN problem statement draft
> 
> 
> 
> 
> 
> In section 3.1, will the architecture define:
> 
> A plug-in/modular architecture to accommodate multiple topology sources (BGP-TE, ALTO, etc)?
> A plug-in/modular architecture to accommodate the multiple provisioning tools available (PCE, OF, your-brand-of-IP-tunnel, etc)?
> 
> I'm just looking for the value statement here, and one of the problems (to me) is the proliferation of options on these "interfaces" (as far as building the perfect application beast goes).  So, for topology, for example … would the Service Mediator define some sort of topology abstraction at ingest that normalizes the formats of the example topology providers above …or maps provisioning capabilities per object managed to hide the syntactical/semantic differences between cross-connecting a flow with OF vs some-other-config-semantic?
> 
> Other than a platform to tie together all the elements, what will the value add be …
> 
> From: Ping Pan <ping at pingpan.org<mailto:ping at pingpan.org>>
> Date: Tue, 13 Mar 2012 07:08:15 -0700
> To: sdnp <sdnp at lucidvision.com<mailto:sdnp at lucidvision.com>>
> Subject: Re: [Sdnp] updated SDN problem statement draft
> 
> The new draft is trying to outline:
> 
> 1. What is it? An overlay architecture that presents the underlying network to the applications for monitoring and provisioning at abstraction level.
> 
> 2. Architecture outline: after speaking to many and tried out quite a few solutions, here is the architecture that we believe is reasonable. (more details to follow)
> 
> 3. Use cases: network slicing, virtual dc and l3 hypervisor. (more details to follow)
> 
> Please take a look, and provide comment.
> 
> (Sorry about many editing mistakes, as we are bouncing between projects)
> 
> Regards,
> 
> Ping
> 
> 
> On Tue, Mar 13, 2012 at 6:58 AM, Thomas Nadeau <tnadeau at lucidvision.com<mailto:tnadeau at lucidvision.com>> wrote:
> 
>       Please review and send us comments/feedback.
> 
> http://tools.ietf.org/html/draft-pan-sdn-dc-problem-statement-and-use-cases-02
> 
>       --Tom
> 
> 
> _______________________________________________
> SDNP mailing list
> SDNP at lucidvision.com<mailto:SDNP at lucidvision.com>
> http://lucidvision.com/mailman/listinfo/sdnp
> 
> _______________________________________________
> SDNP mailing list
> SDNP at lucidvision.com
> http://lucidvision.com/mailman/listinfo/sdnp
> 
> 
> _______________________________________________
> SDNP mailing list
> SDNP at lucidvision.com
> http://lucidvision.com/mailman/listinfo/sdnp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lucidvision.com/pipermail/sdnp/attachments/20120323/a05420e2/attachment.html>