On Mon, Sep 24, 2012 at 9:08 PM, Yakov Rekhter <[email protected]> wrote: >> >> XMPP and SIP are somewhat related. > > How is that information relevant to the choice of XMPP ? > > Yakov. >
There has been some integration between SIP and XMPP solutions, how well those works I don't know, but open source solutions are out there. For connections between hypervisor NVEs (hNVE) you could use the SIP stuff and PR-SCTP as the media (copying the part of the VXLAN header and the inner Ethernet header in the SCTP data chunk), the NVO3 proxy keeps track of the session and liveness detection&traffic engineering is handled by the transport protocol. To reach the external world (WAN) and regular standalone hosts we need something else. Here I would go for the current VXLAN header since the encap/decap is available in merchant silicon. The NVO3 proxy should use XMPP signaling (or SIP messages but XMPP signaling seems to have considered MPLS L3VPN parameters, thus XMPP is more appealing) to setup the session between the hNVE and the asic based NVE (aNVE). Something is needed for liveness detection - is xmpp ping good enough? The NVO3 proxy leverages SIP towards the hNVE and XMPP signaling towards the aNVE - the hNVE contains the modified SIP stack and the aNVE contains the XMPP stack (which is further integrated to BGP). Early ideas to play around with.... Patrick _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
