[Seamoby] CAR DiscoveryProtocol Requirements...

"Govind Krishnamurthi" <govs23@hotmail.com> Fri, 21 December 2001 17:28 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 MAA27265 for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 12:28:50 -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 MAA09042; Fri, 21 Dec 2001 12:16:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09013 for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 12:16:19 -0500 (EST)
Received: from hotmail.com (f164.law9.hotmail.com [64.4.9.164]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26854 for <seamoby@ietf.org>; Fri, 21 Dec 2001 12:16:14 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 21 Dec 2001 09:15:48 -0800
Received: from 63.78.179.5 by lw9fd.law9.hotmail.msn.com with HTTP; Fri, 21 Dec 2001 17:15:48 GMT
X-Originating-IP: [63.78.179.5]
From: Govind Krishnamurthi <govs23@hotmail.com>
To: seamoby@ietf.org
Date: Fri, 21 Dec 2001 12:15:48 -0500
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID: <F164USVeHV30TrbGn3S0000c6f7@hotmail.com>
X-OriginalArrivalTime: 21 Dec 2001 17:15:48.0442 (UTC) FILETIME=[2234EBA0:01C18A43]
Subject: [Seamoby] CAR DiscoveryProtocol 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,
To add to James' mail. Please let us know if any of these
requirements need to be modified or whether any other requirements
are needed.


Regards,
Govind.




        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






_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


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