RE: [rohc] Questions about the MIB!

"Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se> Wed, 27 February 2002 15:59 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28961 for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 10:59:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27353; Wed, 27 Feb 2002 10:55:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27302 for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 10:55:55 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28780 for <rohc@ietf.org>; Wed, 27 Feb 2002 10:55:51 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62]) by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1RFtrB22233 for <rohc@ietf.org>; Wed, 27 Feb 2002 16:55:53 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Feb 27 15:49:58 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19) id <FY38S1B5>; Wed, 27 Feb 2002 15:50:03 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E53@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'West, Mark (ITN)'" <mark.a.west@roke.co.uk>
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Questions about the MIB!
Date: Wed, 27 Feb 2002 15:49:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


> -----Original Message-----
> From: West, Mark (ITN) [mailto:mark.a.west@roke.co.uk]
> Sent: den 25 februari 2002 11:03
> To: rohc@ietf.org
> Cc: Juergen Quittek
> Subject: [rohc] Questions about the MIB!
> 
> 
> There is a quantity of 
> information about contexts which is based on the profiles defined in 
> RFC-3095.  (For example, referring to the modes as U, O and R 
> and states 
> as IR/FO/SO).  This makes absolute sense with regard to RFC 
> 3095.  I am 
> interested to know what anyone thinks about the impact of splitting 
> 3095, however!  How much of the MIB can/should be based on specific 
> profile details, rather than 'generic' framework?  (Clearly 
> in the cases 
> mentioned above, opaque numeric identifiers could be used)
> Anyway, it's a general issue that it would be nice to have 
> some input on...

I agree that this must be considered, and the details will of course 
be clearer when we start the Framework/Profile split. However, most
things can clearly be identified as Framework or RTP, and the MIB
should probably separate what is general ROHC Framework properties
from what is RTP specific details.

/L-E 


_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc