RE: Last-call (RE: [rohc] I-D ACTION:draft-ietf-rohc-rtp-07.txt)

[haihong.zheng@nokia.com]

Hi, Carsten and all,

I have one question on section 5.8.4.3.

It is said in the draft that "A compressed item consists of a compressed
sequence number. When an item is compressed, Padding and Next Header are
removed near the end of the packet." I think you are talking about encrypted
Padding and Next Header fields. But there are two problems here: First, the
encrypted data of the same field may not  be the same as the one in the last
packet. Second, removing these encrypted fields may affect the decryption of
the rest fields. I'm not an expert in encryption algorithm. If someone has
any knowledge in this area, please comment. 

BR,

Haihong

-----Original Message-----
From: ext Dr. Carsten Bormann [mailto:cabo@tzi.org]
Sent: 2. February 2001 7:40 AM
To: rohc@cdt.luth.se
Cc: Mikael Degermark
Subject: Last-call (RE: [rohc] I-D ACTION:draft-ietf-rohc-rtp-07.txt)


ROHCers,

as announced previously, we are now holding a five-day abbreviated WG
last-call for:

   draft-ietf-rohc-rtp-07.txt
   (http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-07.txt)>
   draft-ietf-rohc-rtp-requirements-04.txt

(http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-requirements-04.txt
)

(Note that there are no changes to, and thus no need to last-call again,
   draft-ietf-rohc-rtp-lower-layer-guidelines-00.txt.)

-- Since you all could get the document from the ROHC web site, have
   already seen intermediate snapshots there, and since the changes
   are minor, this second last-call is limited to five real-time days
   from the minute of announcement on the IETF-announce mailing list.

   The last-call ends 2001-02-07 1400 UTC.
   Please comment quickly...

   Please direct comments to the ROHC mailing list, rohc@cdt.luth.se

-- If in the second WG last-call period any significant changes turn
   out to be required, we have to generate a new document and
   last-call that again.  (In any case, unless there are no changes
   from the second last-call period at all, we will have to generate a
   new revision of the I-D before the IESG last-call.)

Gruesse, Carsten

---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/