[Sis-ipo] Update to Space Link Identifier Pink Sheet availble on CCSDS CWE

[Kazz, Greg J]

SLS-SLP and SIS-IPO WGs,

I have placed a new update to the Space Link Identifers Pink Sheet under current CCSDS review.

This update contains a description of the conditions under which the proposed ID #35 would be used.
The file name is 135x0p302working-wbw4-13-09.doc

I have loaded this file into the public folders of both the SIS-IPO and SLS-SLP WG directories since it impacts both areas.

For SLS: http://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2fsls%2fdocs%2fSLS%2dSLP%2fDraft%20Documents&FolderCTID=&View=%7b16ACDA38%2dFFA3%2d4657%2d8F27%2dB166C23C24A2%7d

For SIS:
http://cwe.ccsds.org/sis/docs/Forms/AllItems.aspx?RootFolder=%2fsis%2fdocs%2fSIS%2dIPO%2fDraft%20Documents&FolderCTID=&View=%7b390C4ADA%2dA69B%2d4E52%2dA0DA%2d50C48F989C4B%7d


The change to the text is:
Enumeration #35    Frame Relay IP Header Compression Control Protocol (FRIHCP)[1]


1Per this standard, the Frame Relay Header Compression Control Protocol exchange is not required for header compression to take place on the link.  The alternate is that the use of header compression is by prior arrangement and the associated parameters have been pre-configured.  This is the only option for header compression on a one way link.  Note that if header compression options are misconfigured between sender and receiver, the link will not successfully pass IP packets, as is true with any misconfiguration (e.g. Virtual Channel number used for IP over AOS).  For this reason, use of IP header compression negotiation is useful and recommended where feasible.



Please let me know if you have any comments or concerns about this proposed addition.



best regards,



Greg Kazz

Chairman CCSDS SLS-SLP & SIS-IPO WGs



________________________________

[1] Per this standard, the Frame Relay Header Compression Control Protocol exchange is not required for header compression to take place on the link.  The alternate is that the use of header compression is by prior arrangement and the associated parameters have been pre-configured.  This is the only option for header compression on a one way link.  Note that if header compression options are misconfigured between sender and receiver, the link will not successfully pass IP packets, as is true with any misconfiguration (e.g. Virtual Channel number used for IP over AOS).  For this reason, use of IP header compression negotiation is useful and recommended where feasible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-ipo/attachments/20090413/0cdf437d/attachment.html