Requirement for MN Preference (was: Re: [Seamoby] CAR Discovery Requirements)

"James Kempf" <kempf@docomolabs-usa.com> Wed, 13 March 2002 20:05 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 PAA17137 for <seamoby-archive@odin.ietf.org>; Wed, 13 Mar 2002 15:05:09 -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 OAA09488; Wed, 13 Mar 2002 14:51:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09454 for <seamoby@ns.ietf.org>; Wed, 13 Mar 2002 14:51:16 -0500 (EST)
Received: from fridge.docomolabs-usa.com (fridge.docomolabs-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16701 for <seamoby@ietf.org>; Wed, 13 Mar 2002 14:51:12 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomolabs-usa.com [172.21.96.126]) by fridge.docomolabs-usa.com (8.11.3/8.11.3) with SMTP id g2DJogI03762; Wed, 13 Mar 2002 11:50:42 -0800 (PST)
Message-ID: <024d01c1cac8$226440b0$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Trossen Dirk (NRC/Boston)" <dirk.trossen@nokia.com>, seamoby@ietf.org
References: <DC504E9C3384054C8506D3E6BB012460382FEB@bsebe001.NOE.Nokia.com> <017201c1cabb$d48fbf10$7e6015ac@T23KEMPF> <008701c1cac3$3c336840$6401a8c0@Beethoven>
Subject: Requirement for MN Preference (was: Re: [Seamoby] CAR Discovery Requirements)
Date: Wed, 13 Mar 2002 11:49:06 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

This requirement is meant for a solution to expressing MN preferences
without conflating that and routing and capability information
distribution, requested by Dirk.

    The Seamoby CAR discovery solution MUST provide a means for
    the MN to transmit its preferences for CARs based on CAR
    capabilities  to the AR. The MN preference solution SHOULD
    be logically separate from the CAR information distribution
    solution in order to maintain separation of security requirements,
    i.e. it need not be part of the same protocol as that involved
    in CAR information distribution. Existing protocols, such as AAA,
    MUST be examined as part the design process.

Comments?

            jak





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