Subject: IPHC RFC2507 clarification

From: "ramanad" <[email-masked]>
Date: Mon, 3 Feb 2003 10:55:29 +0530

Hi,
I am working on IPHC RFC 2507.I need small clarification regarding

1).
Section 6 b) ( RFC 2507, IPHC page 21)

COMPRESSED_TCP_NODELTA header format:

+------------+
+   CID      +
+------------+
+ RANDOM fields ,if any
+---------------
+ Whole TCP header except port numbers
+-----------------

Consider the following two cases:
Case1: IPv4 header with 'Options'.In this case all the fields in IPv4 header
are 'RANDOM'.
Case2: IPv4 header with out 'Options'.In this case onle 'IP_IDentifier' in
IPv4 header is 'RANDOM'.

How the decompressor will distinguish the above two?
Is the only length of the packet is the deciding parameter?

2).
Sections 5.3.1 and 5.3.2 ( RFC 2507, IPHC page 19).
I am using first length field to send CID. Here I have basic confusion, I am
assuming the given format in sections 5.3.1 and 5.3.2 are Host byte order.
So I am filling this field in Network order ( i.e. please see below fig for
example) in
FULL HEADERS. Is it correct?

Given in RFC 2507 as follows:
+------------+-----------+
+  Pkt Nr    +   CID     +
+------------+-----------+

It will be filled as follows in FULL HEADERS ( To make it in Network Order)
+------------+-----------+
+   CID      +  Pkt Nr   +
+------------+-----------+

Please correct me if I am doing wrong?

Thanks in advance.

Regards,
Ramana.

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************