[Fwd: Query regarding V2 Profile Classification (Profile 0x104)]

Pradeep,

Re 1):

In the case of the decompressor, the IR packet explicitly binds the 
Context ID to a Profile and Context, and that is how the ROHC 
decompressor determines which Profile the Packet stream belongs to.

In the case of the compressor, I'd think that any incoming packets that 
matched an available Profile would be compared to the existing 
Context(s) to determine if the packets were related to an existing 
Compressed flow in order to determine what action to take, such as 
creating a new Context, or updating an existing one.

Re 2):

I'd say that you would use Profile 0x0104 as the last choice of your 
ROHC Profiles.

This would allow you to use any other supported Profiles first, and 
benefit from the resulting compression.

Profile 0x0104 would only be used after it was found that none of the 
other non-IP headers were present to be compressed.

Bob

-------- Original Message --------
Subject: 	Query regarding V2 Profile Classification (Profile 0x104)
Date: 	Thu, 26 Feb 2009 18:35:19 +0530
From: 	Chaitanya Pradeep <[email protected]>
Reply-To: 	[email protected]
To: 	<[email protected]>



Dear RoHC ers,

      I am facing ambiguity regarding (Profile 0x104) classification in
RoHC V2 Profiles.

      1. On what basis we will choose Profile 0x104 in Version-2 Profiles?

          Because, as mentioned in RFC 5225, all the Profiles present
          in Rohc Version-2 support arbitrary number of IP Levels. So how
do we differentiate between Profile0x104 and
          rest of Profiles (i.e, like Profile0x101 , Profile0x102 ,
Profile0x103 etc) in V2 to classify which Profile the
          Packet stream belongs to?

      2. Is the interpretation correct?

           a) Profile 0x104 is chosen when the Input packet contains only
IP headers and not ended by any RTP/UDP/ESP/TCP headers. (or)
           b) Profile 0x104 is chosen only when no other V2 profile is
supported by the compressor entity other than Profile 0x104.

   Pls share your valuble thoughts regarding the same.

Thanks,
Pradeep.















The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments contained in it.

_______________________________________________
Rohc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rohc

_______________________________________________
Ietf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf