IETF Logo Mail Archive

[Seamoby] CAR Discovery Requirements

"Govind Krishnamurthi" <govs23@hotmail.com> Thu, 10 January 2002 17:55 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 MAA20274 for <seamoby-archive@odin.ietf.org>; Thu, 10 Jan 2002 12:55:13 -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 MAA07739; Thu, 10 Jan 2002 12:51:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07710 for <seamoby@optimus.ietf.org>; Thu, 10 Jan 2002 12:51:00 -0500 (EST)
Received: from hotmail.com (f150.law9.hotmail.com [64.4.9.150]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20171 for <seamoby@ietf.org>; Thu, 10 Jan 2002 12:50:58 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 10 Jan 2002 09:50:28 -0800
Received: from 63.78.179.5 by lw9fd.law9.hotmail.msn.com with HTTP; Thu, 10 Jan 2002 17:50:28 GMT
X-Originating-IP: [63.78.179.5]
From: Govind Krishnamurthi <govs23@hotmail.com>
To: seamoby@ietf.org
Cc: govind.krishnamurthi@nokia.com
Date: Thu, 10 Jan 2002 12:50:28 -0500
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID: <F150wHUFPDyCEYWKnCk0001f8e5@hotmail.com>
X-OriginalArrivalTime: 10 Jan 2002 17:50:28.0605 (UTC) FILETIME=[4A579AD0:01C199FF]
Subject: [Seamoby] CAR Discovery Requirements
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

Hello all,
I wanted to send out a reminder about the CAR Discovery requirements. Does
anyone have any major revisions to the set of requirements that was posted 
earlier on the mailing list?
There requirements were

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 this
item should be changed to a MUST) 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



Thanks,
Govind.






_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.


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

v2.35.0 | Report a Bug | By Email | System Status