RObust Header Compression (ROHC): A Compression Profile for IP
draft-ietf-rohc-ip-only-05

Approval announcement
Draft of message to be sent after approval:

Announcement

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: Protocol Action: 'RObust Header Compression (ROHC): A 
         Compression Profile for IP' to Proposed Standard 

The IESG has approved the following document:

- 'RObust Header Compression (ROHC): A Compression Profile for IP '
   <draft-ietf-rohc-ip-only-06.txt> as a Proposed Standard

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-ip-only-06.txt

Ballot Text

Technical Summary

     This document defines one additional compression profile for
     the RObust Header Compression (ROHC) framework, as defined by
     RFC 3095. In RFC 3095, profiles are specified for compression
     of IP/UDP, IP/UDP/RTP, IP/ESP, as well as for uncompressed
     ROHC transmission. However, a compression profile for IP only
     was omitted in RFC 3095, and this document contributes with
     that missing piece. The profile is defined to require minimal
     modifications to existing ROHC code base, although it does
     provide some minor but useful enhancements and corrections,
     compared to the RFC 3095 profiles.


Working Group Summary

      There was strong consensus in the working group to get this
      profile published, as it was seen to become an important
      complement to RFC 3095.


Protocol Quality

      Allison Mankin reviewed the document for the IESG. In the
      working group, the document was carefully reviewed by
      several implementers of RFC 3095, and the working group
      and IETF Last Calls did not raise any issues.

RFC Editor Note

    Re-name the References - Normative References

RFC Editor Note