[Seamoby] CAR Discovery Requirements Slide from Govind

"James Kempf" <kempf@docomolabs-usa.com> Thu, 20 December 2001 20:54 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 PAA20274 for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 15:54:43 -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 PAA25593; Thu, 20 Dec 2001 15:43:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25556 for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 15:43:27 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19945 for <seamoby@ietf.org>; Thu, 20 Dec 2001 15:43:23 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBKKgt809758 for <seamoby@ietf.org>; Thu, 20 Dec 2001 12:42:55 -0800 (PST)
Message-ID: <034401c18996$ad640ec0$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: seamoby@ietf.org
Date: Thu, 20 Dec 2001 12:41:18 -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
Subject: [Seamoby] CAR Discovery Requirements Slide from Govind
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

        REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS

1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs


2. MUST support L2 devices of different technologies


3. MUST support for L2 devices (and ARs) in private/site-local spaces


4. MUST communicate capability information between GAARs in a secure and
reliable manner


5. MUST use standard format for capabilities..
 and this is TBD

6. Protocol applicability - SHOULD (show of hands indicated that a MUST
is needed here) support inter-domain as well as Intra-domain scope


7. MUST NOT introduce network elements dedicated to CAR discovery.


8. SHOULD minimize involvement of ARs which are not GAARs in CAR
discovery


9. MUST NOT depend on a particular mobility management protocol





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