As one of the people who worked on said xmpp repo, ?known quantity? I think it also means that there where existing ?carrier grade? server implementations that a HW mfg could use, because the RA server needed to handle millions of home gateways.
> >What you need to understand is how those protocols are considered by >routers >usually found on end users' homes. We're not talking about intra-cloud >communication here nor about local-network communication of devices in a >smart >home. We're talking about gaining access to a network and transporting >OIC >message payloads (which use CoAP) over existing, consumer-grade wireless >access points and routers. > >We had to choose an existing and well-known protocol that allowed for bi- >directional exchange of messages of arbitrary format. Those >qualifications >exclude MQTT and CoAP, since those aren't known to most consumer routers. > >> What does mean "known quantity" for XMPP? > >See above. It's about the router know about XMPP and knows to route >replies >properly back to the originating gateway. > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5859 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151007/50bc1e22/attachment.p7s>
