IETF Logo Mail Archive

[Pana] Issue 143: CTP and PANA editorial clarification

Alper Yegin <alper.yegin@samsung.com> Wed, 17 November 2004 22:27 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26291 for <pana-archive@lists.ietf.org>; Wed, 17 Nov 2004 17:27:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUXwa-0002UI-Rv; Wed, 17 Nov 2004 17:06:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUXia-00065d-OC for pana@megatron.ietf.org; Wed, 17 Nov 2004 16:52:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22635 for <pana@ietf.org>; Wed, 17 Nov 2004 16:51:58 -0500 (EST)
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUXl4-0006Y4-OW for pana@ietf.org; Wed, 17 Nov 2004 16:54:35 -0500
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I7C00801FASUY@mailout2.samsung.com> for pana@ietf.org; Thu, 18 Nov 2004 06:49:40 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I7C007UVFAS22@mailout2.samsung.com> for pana@ietf.org; Thu, 18 Nov 2004 06:49:40 +0900 (KST)
Received: from Alperyegin ([105.144.29.156]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0I7C0089JFAQ9Z@mmp1.samsung.com> for pana@ietf.org; Thu, 18 Nov 2004 06:49:40 +0900 (KST)
Date: Wed, 17 Nov 2004 13:49:38 -0800
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <007601c4ccef$56cb9890$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Subject: [Pana] Issue 143: CTP and PANA editorial clarification
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

http://danforsberg.info:8080/pana-issues/issue143

The PaC DOES have an active role in PANA mobility optimization. It
conveys its desire to use CTP by including its session ID in the
PANA-Start-Answer. This is not CTAR, but this is an explicit "message".

This is a CTP (draft-ietf-seamoby-ctp-11.txt) design issue. I recommend
this be fixed in seamoby-ctp, or another simple CTP can be designed. I
don't think we shall morph PANA solution to fit the seamoby-ctp design
(which I think has some room for improvement -- as PANA example shows). 

The PANA spec states seamoby-ctp MAY be useful, it does not mandate its
use. 

Regarding CTP module vs. PANA module, I think this is an implementation
issue. One module needs to talk to the other, and there needs to be
interface between the two.

So, I recommend we reject this issue.

Alper





_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

v2.23.0 | Report a Bug | By Email