[Seamoby] issue-#48: Use of trusted-anchor sub-option between Access Routers

"James Kempf" <kempf@docomolabs-usa.com> Wed, 05 May 2004 22:48 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17177 for <seamoby-archive@odin.ietf.org>; Wed, 5 May 2004 18:48:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLV6f-0001BP-GD for seamoby-archive@odin.ietf.org; Wed, 05 May 2004 18:43:13 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i45MhDMi004539 for seamoby-archive@odin.ietf.org; Wed, 5 May 2004 18:43:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLV1h-0007VW-Br for seamoby-web-archive@optimus.ietf.org; Wed, 05 May 2004 18:38:05 -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 SAA16710 for <seamoby-web-archive@ietf.org>; Wed, 5 May 2004 18:38:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLV1e-0005jW-7I for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:38:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLV0b-0005R1-00 for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:36:58 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLUzh-00059K-00 for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:36:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLUuv-0004ms-Nz; Wed, 05 May 2004 18:31:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLUnB-0001gV-6N for seamoby@optimus.ietf.org; Wed, 05 May 2004 18:23:05 -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 SAA15987 for <seamoby@ietf.org>; Wed, 5 May 2004 18:23:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLUn8-0001De-6N for seamoby@ietf.org; Wed, 05 May 2004 18:23:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLUmD-0000vz-00 for seamoby@ietf.org; Wed, 05 May 2004 18:22:06 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1BLUlc-0000ea-00 for seamoby@ietf.org; Wed, 05 May 2004 18:21:28 -0400
Message-ID: <01db01c432ef$630b8b50$366115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: seamoby@ietf.org
Date: Wed, 05 May 2004 15:21:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] issue-#48: Use of trusted-anchor sub-option between Access Routers
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The issue is that draft 07 requires use of the Trusted Anchor sub-option
between access routers for an AR to request its CAR to send certificates.
Typically an AR would be interested in obtaining certificate chains for all
trusted anchors possessed by the CAR, and since there is no logical
bandwidth limitation on the inter-router interface, there is no reason to
limit the number of certificates transmitted.

The suggested resolution is to include a flag in the CARD Request header for
the AR to indicate that it wants all the certificate chains.

            jak



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