Re: [Seamoby] CAR DiscoveryProtocol Requirements...

Vijay Devarapalli <vijayd@iprg.nokia.com> Fri, 21 December 2001 18:57 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 NAA29426 for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:57:55 -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 NAA11937; Fri, 21 Dec 2001 13:41:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11910 for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:41:13 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28993 for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:41:10 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA17191; Fri, 21 Dec 2001 10:40:42 -0800 (PST)
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBLIegT25303; Fri, 21 Dec 2001 10:40:42 -0800
X-mProtect: Fri, 21 Dec 2001 10:40:42 -0800 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdRWBu18; Fri, 21 Dec 2001 10:40:40 PST
Message-ID: <3C238229.4D2AA9E4@iprg.nokia.com>
Date: Fri, 21 Dec 2001 10:40:41 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
CC: Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
References: <DC504E9C3384054C8506D3E6BB012460382D9E@bsebe001.NOE.Nokia.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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

how about "it makes the CAR discovery protocol very 
complicated".

and tell me why its there in the first place..

all other requirements are fine.

Vijay

"Trossen Dirk (NRC/Boston)" wrote:
> 
> 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