Patrick, > On Mon, Sep 24, 2012 at 4:38 PM, NAPIERALA, MARIA H <[email protected]> wrote: > > Tom, > > > > decoupling PE control plane from the forwarding function has many > > advantage s but mainly it substantially increases operational scale > > - PE/control element is able to control multiple (1000+) compute > > nodes spread across different serve rs and other devices. The > > software complexity (e.g., managing policy functions, gathering of > > operational information like stats, events, diagnostics, etc.) is > > implemented in the control plane elements only. These reduce overall > > cost of a data center deployment. > > In addition, having an open protocol between a control plane and > > a forwarding plane of a PE allows sending local forwarding rules > > to forwarding device(s). XMPP is an open standard, light-weight, > > extendable (can carry various data objects), and flexible protocol > > known to application environment. > > > > Maria > > +1 > > XMPP and SIP are somewhat related.
How is that information relevant to the choice of XMPP ? Yakov. > > >From http://www.sygnalgroup.com/sip-101/ > ------------------------ > There are five parts involved in the making and stopping of > communications that are supported by SIP. These are: > > Location of User: This part determines the location of the end > system that will be used when placing a call. > Availability of User: This part determines the availability of the > end point to participate in a call. > Capabilities of User: This part determines the parameters and > media that will be used in a call. > Setup of Session: This part establishes the session parameters for > each party. > Management of Session: This part invokes transfer, termination and > modification services. > > It is important to note that SIP does not provide services. Instead, > it acts in cooperation with other protocols to provide services. > ----------------------- > Replace "user" with "VM/TES/MAC address" and "call/session" with > tunnel - aren't these the characteristics that we are searching for > the control plane of NVO3?? > > Here is an example of the registration process for a SIP UA; replace > the SIP messages with needed NVO3 XMPP messages and we have a > location/mapping database for NVO3 > http://www.siptutorial.net/SIP/registration.html > > Each CUG could have their own NVO3 location databases; if they need to > exchange information (and allowed to do that) use INVITEs to setup > sessions between proxies, as shown in this diagram > http://www.siptutorial.net/SIP/example.html > (Of course, the INVITE/100/180/200 messages could be replaced with > NVO3 XMPP messages but it is worthwhile to replace it?) > > A SIP proxy can collect CDR - a NVO3 location database should be able > to collect data so you can track where VMs have been located > (presence) and how many tunnels (TDR) a NVE has established. > > The REFER method might be useful for VM mobilty.... > > Etc.... > > Patrick > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
