[rfc-dist] RFC 4997 on Formal Notation for RObust Header Compression (ROHC-FN)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Jul 30 18:04:06 PDT 2007

A new Request for Comments is now available in online RFC libraries.

        RFC 4997

        Title:      Formal Notation for RObust Header 
                    Compression (ROHC-FN) 
        Author:     R. Finking, G. Pelletier
        Status:     Standards Track
        Date:       July 2007
        Mailbox:    robert.finking at roke.co.uk, 
                    ghyslain.pelletier at ericsson.com
        Pages:      62
        Characters: 131231
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rohc-formal-notation-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4997.txt

This document defines Robust Header Compression - Formal Notation
(ROHC-FN), a formal notation to specify field encodings for
compressed formats when defining new profiles within the ROHC
framework.  ROHC-FN offers a library of encoding methods that are
often used in ROHC profiles and can thereby help to simplify future
profile development work.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list