<HTML>
<HEAD>
<TITLE>Re: [Sis-ipo] Adding a note to Encapsulation Service 4.2.2.4</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>I agree with Dave’s comment except it should be a normative statement not a NOTE!<BR>
<BR>
<BR>
On 4/20/09 9:12 PM, "Kazz, Greg J" <greg.j.kazz@jpl.nasa.gov> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT SIZE="5"><FONT FACE="Arial"><SPAN STYLE='font-size:16.0px'>All,<BR>
<BR>
During today’s SIS-IPO meeting, Dave Israel made what I believe is a very good suggestion, discovered during interoperability testing IP/IPE over Encapsulation over AOS frames.<BR>
<BR>
The problem with the current wording of the Encapsulation Service Specification is that two independent implementations will not interoperate if the receive side of the interface implements Encapsulation packet size differently with respect to the transmit side.<BR>
<BR>
The proposed note would be added to the Encapsulation Service Pink Sheets, which is a topic for discussion in the SLS-SLP WG meeting on Friday. The section is 4.2.2.4 Length of Length Field<BR>
<BR>
The proposed note is:<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:16.0px'><FONT COLOR="#000080"><FONT FACE="Times New Roman">NOTE - An implementation <B>on the transmitting end</B> may choose to either use a fixed Encapsulation header size or adaptively/dynamically adjust the size of the Encapsulation Header size according to the payload size in order to optimize bandwidth use (minimize header overhead). Therefore, an implementation must be capable of receiving encapsulation packets implementing either case. <BR>
<BR>
Greg<BR>
</FONT></FONT><FONT FACE="Arial"> <BR>
</FONT></SPAN></FONT><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT>
</BODY>
</HTML>