[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: Proposal / RFC: Change xAP wire format
--90e6ba6e8d2473a0c304a78dcca1
Content-Type: text/plain; charset=ISO-8859-1
>
>
> Secondly, if you were working on the assumption of TCP based
networking
> (and it must be that 99.999% of working implementations are..), would
you
> use the UDP broadcast mechanism as-is, without some form of assured
> delivery? Whilst rare, UDP packet loss, can cause significant issues
when
> xAP is being used for heating control, lighting,
sprinklers/irrigation,
> etc., where there is M2M interaction. Wireless only exacerbates this.
So at
> some level, I feel, this needs addressing as part of a next generation
xAP.
>
RFC3208 (Pragmatic general multicast) is one way to assure UDP delivery.
Simpler schemes, such as a sequential sequence number would also work, but
would probably end up evolving into something similar to PGM eventually.
(Reliable delivery over non-TCP wireless is whole different ball game, and
would be better addressed at the link-layer IMO.)
Which of course comes down to how should any evolution be managed? Who
> should manage this? Should there be a committee? An RFC like process?
Should
> non-standard implementations be 'jumped on', to maximise long term
> interoperability? Is there any appetite for this amongst the developer
> community?
That's quite a can of worms! I really don't know the answer - are there
existing projects that have a governance model that works particularly
well/mirrors the needs of the xAP community that we could borrow from?
P.
--90e6ba6e8d2473a0c304a78dcca1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<head>
<style type=3D"text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title=20
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;=20
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html>
<head>
<style type=3D"text/css">
<!--
#ygrp-mkp {
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 10px 0;
padding: 0 10px;
}
#ygrp-mkp hr {
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd {
color: #628c2a;
font-size: 85%;
font-weight: 700;
line-height: 122%;
margin: 10px 0;
}
#ygrp-mkp #ads {
margin-bottom: 10px;
}
#ygrp-mkp .ad {
padding: 0 0;
}
#ygrp-mkp .ad p {
margin: 0;
}
#ygrp-mkp .ad a {
color: #0000ff;
text-decoration: none;
}
-->
</style>
</head>
<body>
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<div class=3D"gmail_quote"><blockquote
class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div
text=3D"#00=
0000" bgcolor=3D"#ffffff"><br>
Secondly, if you were working on the assumption of TCP based
networking (and it must be that 99.999% of working implementations
are..), would you use the UDP broadcast mechanism as-is, without
some form of assured delivery? Whilst rare, UDP packet loss, can
cause significant issues when xAP is being used for heating control,
lighting, sprinklers/irrigation, etc., where there is M2M
interaction. Wireless only exacerbates this. So at some level, I
feel, this needs addressing as part of a next generation xAP.
<br></div=
></blockquote><div><br></div><div>RFC3208
(Pragmatic general multicast) is =
one way to assure UDP delivery. Simpler schemes, such as a sequential
seque=
nce number would also work, but would probably end up evolving into
somethi=
ng similar to PGM eventually. (Reliable delivery over non-TCP wireless is
w=
hole different ball game, and would be better addressed at the link-layer
I=
MO.)</div>
<div><br></div><div><br></div></div><meta
charset=3D"utf-8"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin-top: 0px; margin-right:
0px; margin-bott=
om: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color:
rgb=
(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span class=3D"Apple-style-span"
style=3D"border-collapse: collapse; font-f=
amily: arial, sans-serif; font-size: 13px; ">Which of course comes
down to =
how should any evolution be managed? Who should manage this? Should there
b=
e a committee? An RFC like process? Should non-standard implementations be
=
'jumped on', to maximise long term interoperability? Is
there any a=
ppetite for this amongst the developer
community?</span></blockquote>
<div><br></div><div>That's quite a can of
worms! I really don't kno=
w the answer - are there existing projects that have a governance model
tha=
t works particularly well/mirrors the needs of the xAP community that we
co=
uld borrow from?</div>
<div><br></div><div>P.=A0</div>
<!-- **begin egp html banner** -->
<br>
=20=20=20=20
=20=20=20=20
<br>
<!-- **end egp html banner** -->
<div width=3D"1" style=3D"color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src=3D"http://geo.yahoo.com/serv?s=3D97476590/grpId=3D9629476/grpspI=
d=3D1705007709/msgId=3D2196/stime=3D1310127377" width=3D"1"
height=3D"1"> <=
br>
<!-- **end egp html banner** -->
=20=20
<!-- **begin egp html banner** -->
<br>
<div style=3D"font-family: verdana; font-size: 77%; border-top: 1px
s=
olid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href=3D"http://groups.yahoo.com/group/xAP_developer/join;_ylc=3DX3=
oDMTJmdGQwZGdiBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5B=
HNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEzMTAxMjczNzc-">Change settings
via the We=
b</a> (Yahoo! ID required) <br>
Change settings via email: <a href=3D"mailto:xAP_developer-digest@yah=
oogroups.com?subject=3DEmail Delivery: Digest">Switch delivery to
Daily Dig=
est</a> <a href =3D "mailto:xAP_developer-fullfeatured@xxxxxxx?su=
bject=3DChange Delivery Format: Fully Featured">Switch to Fully
Featured</a=
> <br>
<a href=3D"http://groups.yahoo.com/group/xAP_developer;_ylc=3DX3=
oDMTJkcmZwZDdkBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5B=
HNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMzEwMTI3Mzc3">
Visit Your Group=20
</a>
<a href=3D"http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href=3D"mailto:xAP_developer-unsubscribe@xxxxxxx?subject=
=3DUnsubscribe">
Unsubscribe=20
</a>=20
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style=3D"color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--90e6ba6e8d2473a0c304a78dcca1--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|