Re: [rohc] WG last-call for ROHC MIB and related documents

[Juergen Quittek <[e-mail]>]

ROHCers,

In order to facilitate your review of draft-ietf-rohc-mib-rtp-05.txt,
I point out the changes between version -04 and -05 below.

The draft contains three MIB modules: ROHC-MIB, ROHC-UNCOMPRESSED-MIB,
and ROHC-RTP-MIB. The ROHC-MIB module defines properties of ROHC instances,
ROHC channels, ROHC profiles, and ROHC compressor and decompressor contexts.
All managed objects in this module are assumed to be shared by all profiles.

The ROHC-UNCOMPRESSED-MIB module extends the ROHC-MIB by managed objects
that are specific to the ROHC uncompressed profile 0x0000 defined in RFC 3095.
The ROHC-RTP-MIB module so far extended the ROHC-MIB by managed objects that
are specific to the three other profiles defined in RFC 3095 (ROHC RTP profile
0x0001, ROHC UDP profile 0x0002, and ROHC ESP profile 0x0003.

Since version -05 also the ROHC LLA profile 0x0005 (defined in RFC 3242) is
supported by the ROHC-RTP-MIB module. For this purpose, the following managed
objects were added to entries of the rohcRtpContextTable:

rohcRtpContextAlwaysPad:
        "Boolean, only applicable to compressor contexts using the
         LLA profile.  If its value is true, the compressor must
         pad every RHP packet with a minimum of one octet ROHC
         padding."
    REFERENCE
        "RFC 3242, Section 5.1.1"
    DEFVAL { false }

rohcRtpContextLargePktsAllowed:
        "Boolean, only applicable to compressor contexts using the
         LLA profile.  It specifies how to handle packets that do
         not fit any of the preferred packet sizes specified.  If
         its value is true, the compressor must deliver the larger
         packet as-is and must not use segmentation.  If it is set
         to false, the ROHC segmentation scheme must be used to
         split the packet into two or more segments, and each
         segment must further be padded to fit one of the preferred
         packet sizes."
    REFERENCE
        "RFC 3242, Section 5.1.1"
    DEFVAL { true }

rohcRtpContextVerifyPeriod OBJECT-TYPE
        "This object is only applicable to compressor contexts
         using the LLA profile.  It specifies the minimum frequency
         with which a packet validating the context must be sent.
         This tells the compressor that a packet containing a CRC
         field must be sent at least once every N packets, where N
         is the value of the object. A value of 0 indicates that
         periodical verifications are disabled."
    REFERENCE
        "RFC 3242, Section 5.1.1"
    DEFVAL { 0 }

rohcRtpContextNHPs OBJECT-TYPE
        "This object is only applicable to contexts using the
         LLA profile.  It contains the number of all no-header
         packets (NHP) sent or received in this context, respectively."
    REFERENCE
        "RFC 3242, Section 4.1.1."

rohcRtpContextCSPs OBJECT-TYPE
        "This object is only applicable to contexts using the
         LLA profile.  It contains the number of all context
         synchronization packets (CSP) sent or received in this
         context, respectively."
    REFERENCE
        "RFC 3242, Section 4.1.2."
rohcRtpContextCCPs OBJECT-TYPE
        "This object is only applicable to contexts using the
         LLA profile.  It contains the number of all context check
         packets (CCP) sent or received in this context, respectively."
    REFERENCE
        "RFC 3242, Section 4.1.3."

rohcRtpContextPktsLostPhysical OBJECT-TYPE
        "This object is only applicable to decompressor contexts
         using the LLA profile.  It contains the number of physical
         packet losses on the link between compressor and
         decompressor, that have been indicated to the decompressor."
    REFERENCE
        "RFC 3242, Section 5.1.2."

rohcRtpContextPktsLostPreLink OBJECT-TYPE
        "This object is only applicable to decompressor contexts
         using the LLA profile.  It contains the number of pre-link
         packet losses on the link between compressor and
         decompressor, that have been indicated to the decompressor."
    REFERENCE
        "RFC 3242, Section 5.1.2."

The rohcRtpPacketSizeTable was extended such that in addition to "allowed"
 and "used" packet sizes (RFC 3095), it may also contain "preferred" packets
sizes (RFC3242). If a packet sizes in the table is allowed, preferred,
and/or used is indicated by three boolean managed objects called
rohcRtpPacketSizeAllowed, rohcRtpPacketSizePreferred, and
rohcRtpPacketSizeUsed. Additionally, the new managed object
rohcRtpPacketSizeRestrictedType indicates restrictions of preferred sizes:

rohcRtpPacketSizeRestrictedType
    SYNTAX      INTEGER {
                    nhpOnly(1),
                    rhpOnly(2),
                    noRestrictions(3)
                }
    DESCRIPTION
        "This object is only applicable to preferred packet
         sizes of compressor contexts using the LLA profile.
         When retrieved, it will indicate whether the packet
         size is preferred for NHP only, for RHP only, or
         for both of them."
    REFERENCE
         "RFC 3242, Section 5.1.1"

Have fun with the review!

    Juergen

-- Carsten Bormann wrote on 15 January 2003 17:20 +0100:

> ROHCers,
>
> In Atlanta, we said we were going to have another re-spin of the ROHC
> MIB to include LLA.  This has now been available for nearly a month,
> and we believe the document has received enough review to issue the WG
> last-call.  Together with this goes the terminology and examples
> document as additional explanatory material that at some point is
> expected to become part of the ROHC draft standard.
>
> Therefore, we are now issuing a WG last-call for the following two
> documents:
>
>   draft-ietf-rohc-mib-rtp-05.txt
>       (for publication as Proposed Standard)
>
>   draft-ietf-rohc-terminology-and-examples-01.txt
>       (for publication as Informational)
>
> This is a regular two-week WG last-call.
>
> Please direct WG last-call comments to the ROHC mailing list
> [e-mail] before Wed, 2003-01-29, 18:00 UTC.
>
> Gruesse, Carsten
>
> _______________________________________________
> Rohc mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/rohc


_______________________________________________
Rohc mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/rohc