RE: [Seamoby] CAR DiscoveryProtocol Requirements...
Dirk.Trossen@nokia.com Fri, 21 December 2001 18:53 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 NAA29280 for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:53:40 -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 NAA11870; Fri, 21 Dec 2001 13:39: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 NAA11840 for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:39:16 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28942 for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:39:12 -0500 (EST)
From: Dirk.Trossen@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBLIdCC25943 for <seamoby@ietf.org>; Fri, 21 Dec 2001 20:39:12 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57f789bd24ac158f2504f@esvir05nok.ntc.nokia.com>; Fri, 21 Dec 2001 20:39:13 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78) id <ZHA66VYZ>; Fri, 21 Dec 2001 20:38:50 +0200
Message-ID: <DC504E9C3384054C8506D3E6BB012460382D9E@bsebe001.NOE.Nokia.com>
To: vijayd@iprg.nokia.com, govs23@hotmail.com
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 20:37:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain; charset="iso-8859-1"
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
Hi, is there any specific reason why you want to remove private address space considerations? Regards, Dirk > -----Original Message----- > From: ext Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] > Sent: Friday, December 21, 2001 1:34 PM > To: Govind Krishnamurthi > Cc: seamoby@ietf.org > Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements... > > > hi all, > > Govind Krishnamurthi wrote: > > > > 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 > > Remove 3. everything else is fine. > > Vijay > > > > > > > > > > >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 > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] CAR DiscoveryProtocol Requirements... Govind Krishnamurthi
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Hesham Soliman (ERA)
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… James Kempf
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… Vijay Devarapalli
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Dirk.Trossen
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… Vijay Devarapalli
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Trossen Dirk (NRC/Boston)
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… Vijay Devarapalli
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Hesham Soliman (ERA)
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Hesham Soliman (ERA)
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… James Kempf
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Trossen Dirk (NRC/Boston)
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Hesham Soliman (ERA)
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Trossen Dirk (NRC/Boston)
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… Vijay Devarapalli
- [Seamoby] CAR Discovery Draft James Kempf
- Re: [Seamoby] CAR DiscoveryProtocol Requirements.… Hemant Chaskar
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Qiang Zhang
- RE: [Seamoby] CAR DiscoveryProtocol Requirements.… Hesham Soliman (ERA)