[rohc] Comments draft-ietf-rohc-sigcomp-extended-01.txt
"Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se> Thu, 21 February 2002 07:44 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 CAA10294
for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 02:44:29 -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 CAA00603;
Thu, 21 Feb 2002 02:42:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA00574
for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 02:42:34 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se
(albatross-ext.wise.edt.ericsson.se [193.180.251.46])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10274
for <rohc@ietf.org>; Thu, 21 Feb 2002 02:42:32 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id
g1L7g3Zc013857
for <rohc@ietf.org>; Thu, 21 Feb 2002 08:42:03 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ;
Thu Feb 21 08:41:06 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service
(5.5.2653.19) id <YHKD4SWK>; Thu, 21 Feb 2002 08:32:28 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A284@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 21 Feb 2002 08:41:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
charset="iso-8859-1"
Subject: [rohc] Comments draft-ietf-rohc-sigcomp-extended-01.txt
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
Hi, Some comments to draft-ietf-rohc-sigcomp-extended-01.txt: 1) Section 2, Terminology. This should be synchronized with draft-ietf-rohc-sigcomp-04.txt 2) Section 4.1, Available state(s) I think "Available" should be changed to "Saved" to avoid confusion. 3) Section 5, page 6, paragraph 2. "Over reliable and ordered transport the most recent state may be used, if the compressor has downloaded such a UDVM instruction code to its remote decompressor." I do not think this text is valid anymore, as the UDVM memory is reinitialised for each new sigComp message, due to security risks. 4) Section 6.1, page 9, last paragraph. "with the support of all extended operation mechanisms" The word "all" is not right should be changed to "some" or specify exactly what is supported with that example. BR /Hans H _______________________________________________ Rohc mailing list Rohc@ietf.org https://www1.ietf.org/mailman/listinfo/rohc
- [rohc] Comments draft-ietf-rohc-sigcomp-extended-… Hans Hannu (EPL)