Re: [rohc] Questions about the MIB!

Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Mon, 25 February 2002 17:25 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 MAA19865 for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 12:25:57 -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 MAA04859; Mon, 25 Feb 2002 12:14:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04826 for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 12:13:57 -0500 (EST)
Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19272 for <rohc@ietf.org>; Mon, 25 Feb 2002 12:13:51 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace.heidelberg.ccrle.nec.de [192.168.102.1]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g1PHDOQ06107; Mon, 25 Feb 2002 18:13:24 +0100 (CET) (envelope-from Martin.Stiemerling@ccrle.nec.de)
Received: from imap.heidelberg.ccrle.nec.de (imap.heidelberg.ccrle.nec.de [192.168.102.11]) by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA28137; Mon, 25 Feb 2002 18:13:23 +0100
Received: from elgar (elgar.heidelberg.ccrle.nec.de [192.168.102.180]) by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 73177138A7; Mon, 25 Feb 2002 18:13:23 +0100 (CET)
Date: Mon, 25 Feb 2002 18:13:22 +0100
From: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>, rohc@ietf.org
Cc: Juergen Quittek <quittek@ccrle.nec.de>
Subject: Re: [rohc] Questions about the MIB!
Message-ID: <5400000.1014657202@elgar>
In-Reply-To: <3C7A0BF1.2030805@roke.co.uk>
References: <3C7A0BF1.2030805@roke.co.uk>
X-Mailer: Mulberry/2.1.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi,

since Juergen is off for the next days I'll take the thread to handle the 
comments/thoughts.

Looking forward for a lot of comments!

Cheers
Martin


--On Montag, Februar 25, 2002 10:03:29 +0000 "West, Mark (ITN)" 
<mark.a.west@roke.co.uk> wrote:

>
> Hi ROHC-ers,
>
> If you haven't been put off by my use of 'MIB' in the subject line, then
> read on!
>
> Having just read through the draft MIB, a couple of questions have arisen
> which I think may benefit from a wider audience...
>
> Firstly, I'm curious to know how many fellow implementors have done
> anything with the packet-size / payload-size restrictions?  (I know we
> haven't ;-)
>
> Secondly, the more general issue is this: 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...
>
> On a related note, there are a number of configuration parameters which
> only really have 'per profile' significance (for example 'k_1' and
> 'n_1').  These parameters are specific to certain profiles .  'k and n'
> also make a useful example, in that k_1 and n_1 are likely to be chosen
> based on the link characteristics.  So, we have values that are
> per-profile and should be configurable (at least) per-interface.  (I
> suppose it makes sense, anyway, to know which profiles are supported on
> any given interface...)
>
> Where a context is using a particular profile, it is not clear to me
> whether or not it is desirable to be able to 'tweak' these values on a
> per-context basis.  Again, any thoughts?
>
> Cheers,
>
> Mark.
>
> --
> Mark A. West, Consultant Engineer
> Roke Manor Research Ltd., Romsey, Hants.  SO51 0ZN
> Phone +44 (0)1794 833311   Fax  +44 (0)1794 833433
>
> (Yes, I do know that my disclaimer is in an attachment.  And, no, I
> didn't ask for it to be that way)



Martin Stiemerling

NEC Europe Ltd. -- Network Laboratories      Martin.Stiemerling@ccrle.nec.de
IPv4: http://www.ccrle.nec.de             IPv6: http://www.ipv6.ccrle.nec.de

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