RE: [Seamoby] Comment on CTP-09

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> Tue, 04 May 2004 21:10 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29632 for <seamoby-archive@odin.ietf.org>; Tue, 4 May 2004 17:10:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL76N-0006E6-W7 for seamoby-archive@odin.ietf.org; Tue, 04 May 2004 17:05:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44L5Jg3023929 for seamoby-archive@odin.ietf.org; Tue, 4 May 2004 17:05:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6xT-00047l-29 for seamoby-web-archive@optimus.ietf.org; Tue, 04 May 2004 16:56:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28788 for <seamoby-web-archive@ietf.org>; Tue, 4 May 2004 16:56:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL6xR-0006fL-47 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 16:56:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL6wa-0006Y1-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 16:55:12 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL6vX-0006Pm-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 16:54:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6qb-0002LI-1J; Tue, 04 May 2004 16:49:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6ob-0001sL-1b for seamoby@optimus.ietf.org; Tue, 04 May 2004 16:46:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28326 for <seamoby@ietf.org>; Tue, 4 May 2004 16:46:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL6oZ-0005Yr-1q for seamoby@ietf.org; Tue, 04 May 2004 16:46:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL6nx-0005TA-00 for seamoby@ietf.org; Tue, 04 May 2004 16:46:18 -0400
Received: from motgate6.mot.com ([144.189.100.106]) by ietf-mx with esmtp (Exim 4.12) id 1BL6nL-0005MN-00 for seamoby@ietf.org; Tue, 04 May 2004 16:45:39 -0400
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate6.mot.com (Motorola/Motgate6) with ESMTP id i44KjdYg026409 for <seamoby@ietf.org>; Tue, 4 May 2004 13:45:39 -0700 (MST)
Received: from il27exm03.cig.mot.com (il27exm03.cig.mot.com [10.17.193.4]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i44KjQUL028826 for <seamoby@ietf.org>; Tue, 4 May 2004 15:45:33 -0500
Received: by il27exm03.cig.mot.com with Internet Mail Service (5.5.2657.72) id <JSDDRN9R>; Tue, 4 May 2004 15:45:26 -0500
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB03D2AB35@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'hannu.flinck@nokia.com'" <hannu.flinck@nokia.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Comment on CTP-09
Date: Tue, 04 May 2004 15:45:25 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

I don't think implementing CTP over ICMP should be a MUST.
 None of the transport protocols were supposed to MUSTs.

Madjid

-----Original Message-----
From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of
hannu.flinck@nokia.com
Sent: Monday, May 03, 2004 5:18 AM
To: seamoby@ietf.org
Subject: [Seamoby] Comment on CTP-09


Hello

As the final reviewed period is ongoing, I would like to provide following comments to the CTP spec.
The CTP draft states about the MN-AR transport the following:

Comment 1:

"3.2 MN-AR Transport

The MN-AR interface MUST implement and SHOULD use ICMP for transport of the CTAR and CTAA messages. 
  :
  :
Because ICMP contains no provisions for retransmitting packets if signaling is lost, the CARD protocol incorporates 
provisions for improving transport performance on the MN-AR interface...."

It is unclear to the reader why CARD protocol is referenced at this point?  Is the intention to imply piggybacking of CTP and CARD over this interface? Plane provision of retransmission doesn't seem to be the motivation since the CTP draft contains already similar retransmission enhancement to CARD:
 
" CTAR messages for which a response is requested which fail to elicit a response are retransmitted.  The initial retransmission
   occurs after a CTP_REQUEST_RETRY wait period. Retransmissions MUST be made with exponentially increasing wait intervals (doubling the
   wait each time).  CTAR messages should be retransmitted until ether a response (which might be an error) has been obtained, or
   for CTP_RETRY_MAX seconds occurs."

In  the CARD draft, section 4.4, there is identical method provided. Hardly the intention is to run double retransmission scheme. So, it appears that the CTP is self-contained regarding to the retransmission and doesn't require any implementation of CARD to be functional. Right?

Suggestion:

- either to remove the reference to CARD, or add wording to explain what is meant by the CARD reference.  

Comment 2 (minor/editorial) to section 2.5.1

The MN MUST sent the sequence number to the same value for the message sent on both pAR and nAR so pAR can determine whether to use a cached message.

change to 
=> The MN MUST set the sequence number  ....


Regards Hannu

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby