IETF Logo Mail Archive

Re: [Seamoby] CAR Discovery Requirements

"James Kempf" <kempf@docomolabs-usa.com> Mon, 14 January 2002 18:31 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 NAA11350 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 13:31:10 -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 MAA17185; Mon, 14 Jan 2002 12:55:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA17154 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 12:55:39 -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 MAA09668 for <seamoby@ietf.org>; Mon, 14 Jan 2002 12:55:34 -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 g0EHstS01912; Mon, 14 Jan 2002 09:54:55 -0800 (PST)
Message-ID: <00c601c19d24$599699b0$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>, 'John Schnizlein' <jschnizl@cisco.com>, Govind Krishnamurthi <govs23@hotmail.com>
Cc: seamoby@ietf.org
References: <4DA6EA82906FD511BE2F00508BCF053801C4C1F6@Esealnt861.al.sw.ericsson.se>
Subject: Re: [Seamoby] CAR Discovery Requirements
Date: Mon, 14 Jan 2002 09:53:18 -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

Hesham,



> => This is exactly why I urge you (this wg) to clearly 
> explain which protocol you are talking about. AR - AR or
> AR MN ???
> Clearly AR - MN lis an obvious way to discover all routers 
> that the MN can hear. Inter/intra domain issues are 
> not relevant. 
> 
> So please make it clear which part of the protocol
> you're referring to. We should not always assume 
> that we're discussing the AR - AR case. 
> 
You are correct, the protocol must apply to both cases,
and the requirements should reflect that.

Perhaps it would make sense to divide the requirements
document into three sections: a) common requirements,
b) requirements for AR-AR case, c) requirements
for AR-MN case.


            jak


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

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