RObust Header Compression (ROHC): Requirements on TCP/IP Header Compression
RFC 4163

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    rohc mailing list <rohc@ietf.org>, 
    rohc chair <rohc-chairs@tools.ietf.org>
Subject: Document Action: 'Requirements for ROHC IP/TCP Header 
         Compression' to Informational RFC 

The IESG has approved the following document:

- 'Requirements for ROHC IP/TCP Header Compression '
   <draft-ietf-rohc-tcp-requirements-09.txt> as an Informational RFC

This document is the product of the Robust Header Compression Working 
Group. 

The IESG contact persons are Allison Mankin and Magnus Westerlund.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-tcp-requirements-09.txt

RFC Editor Note

OLD:
   2.5. Intellectual Property Rights (IPR)
 
      The ROHC WG must spend effort to achieve a high degree of confidence
<<<   that there are no known IPR that covers a final compression solution
      for TCP.
 
      Justification: Currently there is no TCP header compression scheme
      available that can efficiently compress the packet headers of modern
      TCP, e.g. with SACK, ECN, etc. ROHC is expected to fill this gap by 
      providing a ROHC TCP scheme that is applicable in the wide area
      Internet, not only over error-prone radio links. It must thus attempt
<<<   to be as future-proof as possible, and only unencumbered solutions
<<<   will be acceptable to the Internet at large.


with the following:

NEW:
   2.5. Intellectual Property Rights (IPR)
  
      The ROHC WG must spend effort to achieve a high degree of confidence
>>>   that there are no known IPR claims that cover the final compression
      solution for TCP.                        
 
      Justification: Currently there is no TCP header compression scheme
      available that can efficiently compress the packet headers of modern
      TCP, e.g. with SACK, ECN, etc. ROHC is expected to fill this gap by
      providing a ROHC TCP scheme that is applicable in the wide area
      Internet, not only over error-prone radio links. It must thus attempt
>>>   to be as future-proof as possible, and only unencumbered solutions, or
>>>   solutions where the terms of any IPR are such that there is no
>>>   hindrance on implementation and deployment, will be acceptable to the
>>>   Internet at large.