Re: [Seamoby] CAR DiscoveryProtocol Requirements...
"James Kempf" <kempf@docomolabs-usa.com> Fri, 21 December 2001 18:19 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 NAA28534 for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:19:17 -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 NAA10580; Fri, 21 Dec 2001 13:08:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10552 for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:08:05 -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 NAA28184 for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:08:02 -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 fBLI7S819189; Fri, 21 Dec 2001 10:07:28 -0800 (PST)
Message-ID: <01a501c18a4a$20669010$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>, 'Govind Krishnamurthi' <govs23@hotmail.com>, seamoby@ietf.org
References: <4DA6EA82906FD511BE2F00508BCF053801C4C18A@Esealnt861.al.sw.ericsson.se>
Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 10:05:51 -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
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
There is no deadline (yet) on comments for requirements. I believe Last
Call on the CAR discovery problem
statement draft runs out next week.
jak
----- Original Message -----
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'Govind Krishnamurthi'" <govs23@hotmail.com>; <seamoby@ietf.org>
Sent: Friday, December 21, 2001 9:36 AM
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...
> I hope the deadline is not today is it ?
>
> Hesham
>
> > -----Original Message-----
> > From: Govind Krishnamurthi [mailto:govs23@hotmail.com]
> > Sent: Friday, December 21, 2001 6:16 PM
> > To: seamoby@ietf.org
> > Subject: [Seamoby] CAR DiscoveryProtocol Requirements...
> >
> >
> > 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
>
> _______________________________________________
> 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)