From owner-seamoby@diameter.org  Thu Nov  1 00:45:25 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA13098
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Nov 2001 00:45:24 -0500 (EST)
Received: (qmail 8472 invoked by alias); 1 Nov 2001 05:27:42 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8466 invoked by uid 200); 1 Nov 2001 05:27:42 -0000
Received: (qmail 8461 invoked from network); 1 Nov 2001 05:27:40 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 1 Nov 2001 05:27:40 -0000
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fA15iAA28756
	for <seamoby@diameter.org>; Thu, 1 Nov 2001 07:44:10 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56f345930bac158f24066@esvir04nok.ntc.nokia.com> for <seamoby@diameter.org>;
 Thu, 1 Nov 2001 07:43:30 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <V0W3NH52>; Thu, 1 Nov 2001 07:43:30 +0200
Message-ID: <009CA59D1752DD448E07F8EB2F9117571C206B@esebe004.NOE.Nokia.com>
From: Kimmo.Raatikainen@nokia.com
To: seamoby@diameter.org
Subject: [seamoby] FW: [techb] Fwd: SC7/2001-149: N2544 JTC1/SC7 Consolidated Vocabu
	 lary.
Date: Thu, 1 Nov 2001 07:43:27 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This maybe of interest for the terminology ID. - Kimmo
-----Original Message-----
From: ext Robar Terry-ctr044 [mailto:Terry.Robar@motorola.com] 
Sent: 29. October 2001 17:33
To: Robinson Jeff-RVDS40; 'juren@mail2.jpl.nasa.gov';
Daniel.J.Crichton@jpl.nasa.gov; adrian_p_whitfield; byronsmith; chism;
chowlett; christison margaret; Robar Terry-ctr044; Dan; DaveGlanville;
DaveThomen; deverett; djstemm; DMDurham; DorothyMcKinney; dwoliver;
FrankMaty; Rick Steiner; georgecaple917; GerryGraves; heimann; ianbailey;
jelong; jnallon; josephsimpson; julianjohnson; KenJackson; Howard Lykins;
MartinH; Michael_Giblin; Michael Dickerson; Mike Keenan; Martha Nicholson;
Paul A. Nelson; Dr. Phil Spiby; Robert M. Cohen; RogerCox; RussellPeak;
sbarbeau; Schier-Jim; SeanBarker; sfriedenthal; Sharon Shoshany; sherwood;
smahearn; Simon Phillips; tomthurman; Velman; WillScott; 'Bernd G. Wenzel';
Friedenthal, Sanford; tc@omg.org; sep@omg.org; dock@mitre.org;
fred.cummins@eds.com; larry.johnson@mscsoftware.com;
sridhar.iyengar2@unisys.com; hlowe@omg.org; chism2000@netzero.net;
mcantor@rational.com; marco.temaner@popkin.com; adrian@ilogix.com;
wask@omg.org; dwoliver1@worldnet.att.net; Cris.Kobryn@telelogic.com;
Mark.Sampson@sdrc.com; Robitaille, Paul; Chonoles, Michael J; Sturges, Jim
Subject: FW: [techb] Fwd: SC7/2001-149: N2544 JTC1/SC7 Consolidated Vocabu
lary.


I'm not sure if there is overlap between distribution lists but wanted to
get pass this on given AP233 terminology task in progress.  My apologies for
any repeat addresses in the concatenated list. Terry
-----Original Message-----
From: James.N.Martin@aero.org [mailto:James.N.Martin@aero.org]
Sent: Monday, October 29, 2001 9:05 AM
To: techb@incose.org
Cc: STC@incose.org; WGIG-leaders@incose.org
Subject: [techb] Fwd: SC7/2001-149: N2544 JTC1/SC7 Consolidated Vocabulary.



Here is an interesting compilation of terminology from 34 different
standards (eg, 9000, 15288, and 731) and other standards-like documents (eg,
SE-CMM).  Click on the URL to download a ZIP file of about 400KB in size.   

This "vocabulary" is provided in two formats -- Excel and Access.  The
Access database is particularly useful since the terms are all in one module
and they can be sorted by the "term" column to see how various standards
define the same term in different manners.  Of particular interest are such
terms as system, system architecture, requirement, traceability, system
design, system development, and so on. 

Your WGs may find this useful when trying to determine what term to use in
their own work.  They should at least be aware of how the various standards
use certain terms in their own domain of expertise.   

James 


----- Forwarded by James N Martin/East/Aerospace/US on 10/29/01 09:52 AM
----- 

	Robert Halligan <rhalligan@taa.com.au> 


10/26/01 11:32 PM 


        
        To:        "Ken Crowder" <kvcrowder@aol.com> 
        cc:        "James Martin" <James.N.Martin@aero.org> 
        Subject:        Fwd: SC7/2001-149: N2544 JTC1/SC7 Consolidated
Vocabulary.	




---------------- Begin Forwarded Message ----------------
Date:        01/10  1:51 PM
Received:    01/10  2:08 PM
From:        JTC1/SC7 Secretariat, sc7@qc.bell.ca
To:          SC7 Advisory Group,, sc7_ag@bhhct3.qc.bell.ca

========================================================================
    MESSAGE IDENTIFIER: ISO/IEC JTC1/SC7/Secretariat/SC7-2001-149
========================================================================

                                                  ISO/IEC JTC1/SC7 N2544

Document Type     Memo

Title             JTC1/SC7 Consolidated Vocabulary.

Source            JTC1/SC7 SWG2 Convener.

Project

Status

Reference         N2491

Action ID         FYI or ACT

Due Date

Mailing Date      2001-09-30

Distribution      SC7 AG, SC7 Project Editors

Medium            Acrobat and Access zipped

Number of pages

Note              All Conveners and Project Editors have a responsibility
to
                 ensure that the vocabulary in their documents is
consistent
                 with the JTC1/SC7 vocabulary.

URL:
http://saturne.info.uqam.ca/Labo_Recherche/Lrgl/sc7/N2501-N2550/07n2544.zip


 -------------------------------------------------------------------
|Jean-Normand Drouin                          email: sc7@qc.bell.ca |
|JTC1/SC7 Secretariat                                               |
|Bell Canada                                                        |
|1050 Beaver Hall Hill, fl.2                    TEL: (514) 391-8286 |
|Montreal (Quebec) H2Z 1S4                      FAX: (514) 870-2246 |
|Canada                                                             |
|SC7 WebSite: http://saturne.info.uqam.ca/Labo_Recherche/Lrgl/sc7/  |
-------------------------------------------------------------------



----------------- End Forwarded Message -----------------


__________________________________________________________________
Robert Halligan                            rhalligan@taa.com.au
Managing Director                          Phone:  +61 3 9876 7345
Technology Australasia Pty Ltd             Fax:    +61 3 9876 2664
PO Box 2385, North Ringwood Vic 3134       Res:    +61 3 9876 3799
Australia


Private email: rh111246@bigpond.com
Helping projects succeed ...
http://www.taa.com.au
__________________________________________________________________






From owner-seamoby@diameter.org  Thu Nov  1 16:58:32 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01585
	for <seamoby-archive@lists.ietf.org>; Thu, 1 Nov 2001 16:58:31 -0500 (EST)
Received: (qmail 13879 invoked by alias); 1 Nov 2001 21:41:51 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13873 invoked by uid 200); 1 Nov 2001 21:41:51 -0000
Received: (qmail 13868 invoked from network); 1 Nov 2001 21:41:48 -0000
Received: from ponyexpress.ee.columbia.edu (root@128.59.64.61)
  by c900656-a.plstn1.sfba.home.com with SMTP; 1 Nov 2001 21:41:48 -0000
Received: from SWEETPEA (sweetpea.comet.columbia.edu [128.59.65.202])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with SMTP id fA1LvNn27734;
	Thu, 1 Nov 2001 16:57:25 -0500
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "'Kar Ann Chew'" <k.chew@eim.surrey.ac.uk>, <seamoby@cdma-2000.org>
Subject: RE: [seamoby] drafts on paging
Date: Thu, 1 Nov 2001 16:54:35 -0500
Message-ID: <004101c1631f$cc14b650$ca413b80@SWEETPEA>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <009201c16231$f4afb540$2b6015ac@DOCOMOKEMPF>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The following ID proceeded the Seamoby ID
and may be of interest. Note it is not
an official Seamoby. Mainly FYI.

X. Zhang, J. Castellanos, A. Campbell, K. Sawada, and M. Barry, P-MIP:
Minimal Paging Extensions for Mobile IP, Internet Draft
draft-zhang-pmip-00.txt, IETF Mobile IP Working Group, July 2000.

http://www.comet.columbia.edu/~campbell/andrew/publications/papers/draft-zha
ng-pmip-00.txt

---
Andrew
http://comet.columbia.edu/~campbell


> -----Original Message-----
> From: owner-seamoby@diameter.org [mailto:owner-seamoby@diameter.org]On
> Behalf Of James Kempf
> Sent: Wednesday, October 31, 2001 12:32 PM
> To: Kar Ann Chew; seamoby@cdma-2000.org
> Subject: Re: [seamoby] drafts on paging
>
>
> draft-kooldi-paging-00.txt
> draft-ohba-seamoby-last-hop-dmha-02.txt
> draft-sarikaya-seamoby-confmipv6hp-00.txt,
> 	       draft-sarikaya-seamoby-miv6hp-00.txt,
> 	       draft-guri-seamoby-lahap-00.txt,
> 	       draft-guri-seamoby-conflahap-00.txt
> (counted as one proposal)
> draft-renker-paging-ipv6-01.txt
>
>             jak



From owner-seamoby@diameter.org  Thu Nov  1 19:11:51 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA03221
	for <seamoby-archive@lists.ietf.org>; Thu, 1 Nov 2001 19:11:50 -0500 (EST)
Received: (qmail 14628 invoked by alias); 1 Nov 2001 23:55:14 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14622 invoked by uid 200); 1 Nov 2001 23:55:13 -0000
Received: (qmail 14617 invoked from network); 1 Nov 2001 23:55:12 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 1 Nov 2001 23:55:12 -0000
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 QAA19071;
	Thu, 1 Nov 2001 16:10:37 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fA20Aa828663;
	Thu, 1 Nov 2001 16:10:36 -0800
X-mProtect:  Thu, 1 Nov 2001 16:10:36 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdcq8R90; Thu, 01 Nov 2001 16:09:24 PST
Message-ID: <3BE1E434.A221F172@iprg.nokia.com>
Date: Thu, 01 Nov 2001 16:09:24 -0800
From: Rajeev Koodli <rajeev@IPRG.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: Kar Ann Chew <k.chew@eim.surrey.ac.uk>, seamoby@cdma-2000.org
Subject: Re: [seamoby] drafts on paging
References: <Pine.GSO.4.21.0110311445430.7194-100000@haskins.ee.surrey.ac.uk> <009201c16231$f4afb540$2b6015ac@DOCOMOKEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


James,

a small correction below..

James Kempf wrote:

> draft-kooldi-paging-00.txt

              ^^^^^^
             koodli

(Cool) regards,

-Rajeev


>
> draft-ohba-seamoby-last-hop-dmha-02.txt
> draft-sarikaya-seamoby-confmipv6hp-00.txt,
>                draft-sarikaya-seamoby-miv6hp-00.txt,
>                draft-guri-seamoby-lahap-00.txt,
>                draft-guri-seamoby-conflahap-00.txt
> (counted as one proposal)
> draft-renker-paging-ipv6-01.txt
>
>             jak



From owner-seamoby@diameter.org  Fri Nov  2 03:05:06 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27612
	for <seamoby-archive@lists.ietf.org>; Fri, 2 Nov 2001 03:05:04 -0500 (EST)
Received: (qmail 15838 invoked by alias); 2 Nov 2001 07:47:07 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 15832 invoked by uid 200); 2 Nov 2001 07:47:07 -0000
Received: (qmail 15827 invoked from network); 2 Nov 2001 07:47:04 -0000
Received: from mail.rsasecurity.com (HELO tholian.securitydynamics.com) (204.167.112.129)
  by c900656-a.plstn1.sfba.home.com with SMTP; 2 Nov 2001 07:47:04 -0000
Received: from sdtihq24.securitydynamics.com by tholian.securitydynamics.com
          via smtpd (for c900656-a.plstn1.sfba.home.com [24.20.167.220]) with SMTP; 2 Nov 2001 07:59:23 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id DAA12895
	for <seamoby@diameter.org>; Fri, 2 Nov 2001 03:03:00 -0500 (EST)
Received: from exno02.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.9.3+Sun/8.9.1) with ESMTP id DAA09551
	for <seamoby@diameter.org>; Fri, 2 Nov 2001 03:02:59 -0500 (EST)
Received: from sjosefsson-pc.d.dynas.se ([172.16.13.115]) by exno02.dynas.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id V47A1S9Z; Fri, 2 Nov 2001 09:02:46 +0100
To: seamoby@diameter.org
Subject: [seamoby] Re: Last Call on draft-ietf-seamoby-context-transfe
 r-problem-stat-03.txt
References: <35DBB8B7AC89D4118E98009027B1009B017AA141@IL27EXM10.cig.mot.com>
From: Simon Josefsson <sjosefsson@dynas.se>
Reply-To: Simon Josefsson <sjosefsson@rsasecurity.com>
Date: Fri, 02 Nov 2001 09:05:52 +0100
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B017AA141@IL27EXM10.cig.mot.com>
 (Nakhjiri Madjid-MNAKHJI1's message of "Wed, 31 Oct 2001 17:31:44 GMT")
Message-ID: <m3u1wd8un3.fsf@sjosefsson-pc.d.dynas.se>
Lines: 117
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i686-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-seamoby@diameter.org
Precedence: bulk

I believe both centralized context servers and context transfers will
be used (context transfer improves speed and reduce client complexity,
while a centralized context servers may improve administrative control
and perhaps offer increased security). Hence, my comment was not
"against" context transfers at all -- only that _when_ you use CT of
keying material, you should be aware that the system security might
not be as good as when you use a centralized context server.  This is
not surprising, but I felt it should be pointed out because there may
be situations where CT of keying material probably can't be used
because of this problem -- when the ARs aren't physically protected
for instance.  (I assume the centralized context server is physically
protected.)  I agree it is a context storage issue, and has nothing to
do with the CT protocol actually used -- but the security of CT is not
only about the actual protocol used.

Except this minor comment, I think the document looks good.

/Simon

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> writes:

> Hi Simon,
> 
> See my comments in line:
> 
> -----Original Message-----
> From: Simon Josefsson [mailto:sjosefsson@dynas.se]
> Sent: Monday, October 29, 2001 4:44 AM
> To: seamoby@diameter.org
> Subject: [seamoby] Re: Last Call on
> draft-ietf-seamoby-context-transfer-problem-stat-03.txt
> 
> 
> "James kempf" <kempf@docomolabs-usa.com> writes:
> 
>> Folks,
>> 
>> Working Group Last Call on
> draft-ietf-seamoby-context-transfer-problem-stat-03.txt starts tomorrow,
> Oct. 26, and runs for two weeks until Nov. 9. Please submit comments
>> to the list before Nov. 9.
> 
> I am new to this group and have not followed the development of this
> draft, and my concerns may be specific to 802.11 Wireless LANs and
> when the context includes encryption keying material, but nevertheless
> I have a comment on the security considerations:
> 
> Even when context transfers between network entities (access points in
> 802.11 terminology) are secured via IPSEC or similar, I believe the
> complete system is less secure than compared with when context
> transfer is not used, and instead one backend server handles roaming
> which sends the necessary context (including encryption keys) to each
> access point.
> 
> Madjid>> Centralized context servers, versus context tranfer between ARs
> was discussed early on and I don't want to get into pros and cons of it.
> 
> Madjid>>Just in this case, you would still have a problem when the MN moves
> between
> administrative domains using separate policy/authentication... servers.
> And this is general AAA, security, key management issues with lots of things
>  involved such as AAA brokers, CAs , you name it.
> 
> Madjid>>We need to secure the context transfer channel propoerly to not
> compromise the information (including the keys) going through.
> Unless you are completely against context transfer.
> 
> 
> The reasons is that, if one of the access points is compromised, the
> context received may be used to sniff the network even after the
> mobile node left the compromised network entity.  Compromising a
> access point when context transfer is not used does not make this
> possible.  So the system security has been reduced from having the
> backend server a single-point-of-failure to having
> multiple-point-of-failures, the security is reduced 1:N.
> 
> 
> If you agree (discussion welcome), I'd suggest that something like the
> following text is added to the security considerations:
> 
>       The compromise of only one of the network entities that contain
>       context may be sufficient to reduce the security of the whole
>       system, if for example the context includes encryption keying
>       material.  When the host moves from the compromised network
>       entity to a uncompromised network entity, the compromised
>       context may be used to decrypt the communication channel.  When
>       context transfer is not used, a compromise of only one network
>       entity only gives access to what that network entity can see.
>       This means that network entities must have similar physical
>       and software protection as the backend server.
> 
> Madjid>>
> 1- I agree with James, it is access routers not access points.
> 2- we are dealing with a communications security problem, 
> not a storage security problem, are we not?
> We need to secure the communication of context, not how securely it stored,
> that is the issue of access security.
> Secure storage of keying material is not limited to context transfer.
> 
> 3- context transfer is intended to happen between ARs, how it is gathered
> at old AR, and how the old context is dumped at old AR after transfer, was
> defined as out of scope. 
> 
> Again, I don't quite see this as a problem for context transfer, but rather
> a 
> context storage problem.
> 
> Are you advocating a more secure context transfer, or more secure storage
> of keying material used for context transfer?
> 
> Hope this is not too far out in the woods,
> Madjid
> 
> 
> -- 
> Simon Josefsson
> RSA Security



From owner-seamoby@diameter.org  Fri Nov  2 07:01:44 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA29785
	for <seamoby-archive@lists.ietf.org>; Fri, 2 Nov 2001 07:01:43 -0500 (EST)
Received: (qmail 16716 invoked by alias); 2 Nov 2001 11:44:40 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 16710 invoked by uid 200); 2 Nov 2001 11:44:40 -0000
Received: (qmail 16705 invoked from network); 2 Nov 2001 11:44:37 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 2 Nov 2001 11:44:37 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29646;
	Fri, 2 Nov 2001 07:00:27 -0500 (EST)
Message-Id: <200111021200.HAA29646@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-nakhjiri-seamoby-text-ct-00.txt
Date: Fri, 02 Nov 2001 07:00:26 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Time Efficient conteXt Transfer (TEXT)
	Author(s)	: M. Nakhjiri, A. Singh
	Filename	: draft-nakhjiri-seamoby-text-ct-00.txt
	Pages		: 22
	Date		: 01-Nov-01
	
This document presents a context transfer proposal, greatly in 
line with the current fast handover framework within Mobile IP WG 
[3]. Namely, this proposal allows flow of MNĘs real time traffic 
through a tunnel, while completing context transfer outside 
timing critical path for handover. The context transfer procedure 
is initiated at an instance of MNĘs choice in regard to layer 2 
and 3 handover and MNĘs traffic. To add flexibility, the context 
data is transferred outside the tunnel.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-nakhjiri-seamoby-text-ct-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-nakhjiri-seamoby-text-ct-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-nakhjiri-seamoby-text-ct-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011101124044.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-nakhjiri-seamoby-text-ct-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-nakhjiri-seamoby-text-ct-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011101124044.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Fri Nov  2 09:56:34 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06780
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Nov 2001 09:56:32 -0500 (EST)
Received: (qmail 17757 invoked by alias); 2 Nov 2001 14:39:43 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 17751 invoked by uid 200); 2 Nov 2001 14:39:42 -0000
Received: (qmail 17746 invoked from network); 2 Nov 2001 14:39:40 -0000
Received: from motgate.mot.com (129.188.136.100)
  by c900656-a.plstn1.sfba.home.com with SMTP; 2 Nov 2001 14:39:40 -0000
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (motgate 2.1) with ESMTP id HAA29273 for <seamoby@diameter.org>; Fri, 2 Nov 2001 07:55:37 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id HAA20285 for <seamoby@diameter.org>; Fri, 2 Nov 2001 07:55:37 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WDZL2VB2>; Fri, 2 Nov 2001 08:55:37 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017AA150@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: seamoby@diameter.org
Subject: [seamoby] TEXT: our context transfer proposal
Date: Fri, 2 Nov 2001 08:55:36 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


Hi folks,

Meant to send this note earlier than the IETF announce, seems
like IETF announce outpaced us. Anyhow:

seems like the context transfer req draft got through last call, so while
waiting
for IESG with responses, we sent a context transfer draft as a preliminary
solution proposal before Utah IETF submission deadline.

This draft is of course a preliminary proposal with the goal of
communicating  the  concept, the details are to be improved with help of
people who might be interested.

To encourage a reduction in the amount of amunition in fire power against
the draft :)
 here are a few motivators/ disclaimers:

1-the proposal performs CT outside timing path, so before, after during
handover issues
are not relevant.

2-Although we provide specific suggestions for various elements of the
protocol,
the proposal provides a great amount of flexibility and room for changes in
choice of
 	-triggers
	-who initiates the CT
	-the role of MN in CT
	-amount of reliability
i.e. choices different from what we specified in the draft.

3-Since the CT reliability and transport mechanisms requirements are not
clear,
we provide an optional reliability mechanisms, in case context delivery
needs to be
reliable. Note that reliablity of context may include need for updates (for
dynamic context) as opposed to retransmissions.
 No existing transport protocol provides updates, that is
the job of CT protocol (~application layer).
The reliability mechanism has a lot of room for improvements.

Please fire away,

Regards,
Madjid Nakhjiri


From owner-seamoby@diameter.org  Fri Nov  2 09:59:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06867
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Nov 2001 09:59:17 -0500 (EST)
Received: (qmail 18309 invoked by alias); 2 Nov 2001 14:42:29 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 18303 invoked by uid 200); 2 Nov 2001 14:42:28 -0000
Received: (qmail 18294 invoked by uid 500); 2 Nov 2001 14:42:27 -0000
Date: Fri, 2 Nov 2001 06:42:27 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@diameter.org
Subject: Re: [seamoby] TEXT: our context transfer proposal
Message-ID: <20011102064227.E17532@charizard.diameter.org>
Mail-Followup-To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
	seamoby@diameter.org
References: <35DBB8B7AC89D4118E98009027B1009B017AA150@IL27EXM10.cig.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B017AA150@IL27EXM10.cig.mot.com>; from Madjid.Nakhjiri@motorola.com on Fri, Nov 02, 2001 at 08:55:36AM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

Just as a point of clarification, there were some comments generated during
the last call. These comments are being addressed, and a new version will soon
be available. Given the changes require, a new last call will be required.

Thanks,

PatC
On Fri, Nov 02, 2001 at 08:55:36AM -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> 
> Hi folks,
> 
> Meant to send this note earlier than the IETF announce, seems
> like IETF announce outpaced us. Anyhow:
> 
> seems like the context transfer req draft got through last call, so while
> waiting
> for IESG with responses, we sent a context transfer draft as a preliminary
> solution proposal before Utah IETF submission deadline.
> 
> This draft is of course a preliminary proposal with the goal of
> communicating  the  concept, the details are to be improved with help of
> people who might be interested.
> 
> To encourage a reduction in the amount of amunition in fire power against
> the draft :)
>  here are a few motivators/ disclaimers:
> 
> 1-the proposal performs CT outside timing path, so before, after during
> handover issues
> are not relevant.
> 
> 2-Although we provide specific suggestions for various elements of the
> protocol,
> the proposal provides a great amount of flexibility and room for changes in
> choice of
>  	-triggers
> 	-who initiates the CT
> 	-the role of MN in CT
> 	-amount of reliability
> i.e. choices different from what we specified in the draft.
> 
> 3-Since the CT reliability and transport mechanisms requirements are not
> clear,
> we provide an optional reliability mechanisms, in case context delivery
> needs to be
> reliable. Note that reliablity of context may include need for updates (for
> dynamic context) as opposed to retransmissions.
>  No existing transport protocol provides updates, that is
> the job of CT protocol (~application layer).
> The reliability mechanism has a lot of room for improvements.
> 
> Please fire away,
> 
> Regards,
> Madjid Nakhjiri


From owner-seamoby@diameter.org  Fri Nov  2 13:53:50 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15031
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Nov 2001 13:53:48 -0500 (EST)
Received: (qmail 19344 invoked by alias); 2 Nov 2001 18:36:49 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 19338 invoked by uid 200); 2 Nov 2001 18:36:48 -0000
Received: (qmail 19333 invoked from network); 2 Nov 2001 18:36:46 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 2 Nov 2001 18:36:46 -0000
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 KAA19300;
	Fri, 2 Nov 2001 10:52:07 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fA2Iq6q07983;
	Fri, 2 Nov 2001 10:52:06 -0800
X-mProtect:  Fri, 2 Nov 2001 10:52:06 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdRYXH6V; Fri, 02 Nov 2001 10:23:18 PST
Message-ID: <3BE2E496.5CC81C5D@iprg.nokia.com>
Date: Fri, 02 Nov 2001 10:23:18 -0800
From: "Charles E. Perkins" <charliep@IPRG.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Simon Josefsson <sjosefsson@rsasecurity.com>
CC: seamoby@diameter.org
Subject: Re: [seamoby] Re: Last Call on 
 draft-ietf-seamoby-context-transfer-problem-stat-03.txt
References: <35DBB8B7AC89D4118E98009027B1009B017AA141@IL27EXM10.cig.mot.com> <m3u1wd8un3.fsf@sjosefsson-pc.d.dynas.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Simon,

Suppose we can make the following assumptions:

1. There is a security association between two edge routers.
2. The key between the mobile node and the first
   edge router has been distributed securely.

Now suppose the mobile node moves to a new edge router.

You (Simon Josefsson) wrote:
>            ..............                _when_ you use CT of
> keying material, you should be aware that the system security might
> not be as good as when you use a centralized context server.

What would cause the security to be downgraded?

>                                                               This is
> not surprising, but I felt it should be pointed out because there may
> be situations where CT of keying material probably can't be used
> because of this problem -- when the ARs aren't physically protected
> for instance.

Does this mean that somehow the physical AR has been compromised
and its security associations revealed?  Then
1. Maybe the central server would no longer authenticate security
   messages for the mobile node?  But then, why would the previous
   AR?  Presumably, the central server would have notified its
   still-trustworthy associates about the breach in security
2. Maybe the new edge router would try to supply a key in place
   of the one derived from the previous key?  But this can be
   detected by the mobile node, I reckon, given proper encoding of
   the "real" new key...

I don't deny that there may be threats, but I don't see exactly
what they are.  Maybe we can protect against them, and make edge
security transfers as good as centralized transfers?  For that
reason, it would be good to have as complete a view of the potential
problem areas as possible.

>             I agree it is a context storage issue, and has nothing to
> do with the CT protocol actually used -- but the security of CT is not
> only about the actual protocol used.

Could you describe what you had in mind here?

Thanks!

Regards,
Charlie P.


From owner-seamoby@diameter.org  Wed Nov  7 05:26:25 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA00420
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Nov 2001 05:26:24 -0500 (EST)
Received: (qmail 9839 invoked by alias); 7 Nov 2001 10:09:13 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9833 invoked by uid 200); 7 Nov 2001 10:09:12 -0000
Received: (qmail 9828 invoked from network); 7 Nov 2001 10:09:10 -0000
Received: from smtp5.cluster.oleane.net (195.25.12.27)
  by c900656-a.plstn1.sfba.home.com with SMTP; 7 Nov 2001 10:09:10 -0000
Received: from oleane (upper-side.rain.fr [194.250.212.114]) by smtp5.cluster.oleane.net with SMTP id fA7APLp05782 for <seamoby@cdma-2000.org>; Wed, 7 Nov 2001 11:25:22 +0100 (CET)
Message-ID: <010a01c16776$2cf77020$0601a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <seamoby@cdma-2000.org>
Subject: [seamoby] Mobile Ad Hoc Networks '02
Date: Wed, 7 Nov 2001 11:22:59 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0107_01C1677E.8E3D3240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0107_01C1677E.8E3D3240
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

How to design Ad Hoc routing protocols ?=20
How to manage dynamically changing topology?=20
Which applications are targeted ?=20
Are these networks scalable ?=20
Mobile Ad Hoc Networks '02, to take place in Paris, France, from March 5 =
to 8, 2002, will bring answers and enlightenment to all these questions =
through the presentations of leading-edge researchers in the domain.=20
All details at:
http://www.upperside.fr/adhoc/adhocintro.htm
=20

------=_NextPart_000_0107_01C1677E.8E3D3240
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial>
<DIV><FONT face=3DArial>
<DIV><FONT size=3D2><FONT color=3D#000000>How to design Ad Hoc routing =
protocols ?=20
<BR>How to manage dynamically changing topology? <BR>Which applications =
are=20
targeted ? <BR>Are these networks scalable ? </FONT><BR><FONT=20
color=3D#000000><SPAN class=3Dtexte><FONT color=3D#663366>Mobile Ad Hoc =
Networks=20
'02</FONT>, to take place in <FONT color=3D#663366>Paris</FONT>, France, =
from=20
<FONT color=3D#663366>March 5 to 8, 2002</FONT>, will bring answers and=20
enlightenment to all these questions through the presentations of =
leading-edge=20
researchers in the domain. </SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT color=3D#000000><SPAN class=3Dtexte>All =
details=20
at:</SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT color=3D#000000><SPAN class=3Dtexte><A=20
href=3D"http://www.upperside.fr/adhoc/adhocintro.htm">http://www.uppersid=
e.fr/adhoc/adhocintro.htm</A></SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT color=3D#000000><SPAN=20
class=3Dtexte></SPAN></FONT></FONT>&nbsp;</DIV></FONT></DIV></FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_0107_01C1677E.8E3D3240--



From owner-seamoby@diameter.org  Wed Nov  7 15:13:14 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22443
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Nov 2001 15:13:13 -0500 (EST)
Received: (qmail 11905 invoked by alias); 7 Nov 2001 19:55:33 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11899 invoked by uid 200); 7 Nov 2001 19:55:33 -0000
Received: (qmail 11894 invoked from network); 7 Nov 2001 19:55:31 -0000
Received: from netmail2.alcatel.com (128.251.168.51)
  by c900656-a.plstn1.sfba.home.com with SMTP; 7 Nov 2001 19:55:31 -0000
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA00025;
	Wed, 7 Nov 2001 14:11:45 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id fA7KBfY26104;
	Wed, 7 Nov 2001 14:11:45 -0600 (CST)
Message-ID: <3BE98727.F0A85485@alcatel.com>
Date: Wed, 07 Nov 2001 14:10:31 -0500
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD BDPjm-Sony3  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: h.takusagawa@jp.fujitsu.com
CC: seamoby <seamoby@cdma-2000.org>
Subject: [seamoby] Re: [Fwd: questions on LAHAP draft]
References: <BEEBIBABEABFJNJPKKIAAEDCCCAA.hidetak@flab.fujitsu.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Hideaki,
     L2 paging areas are what we have now in public cellular networks.
Our
protocols (Lahap and mipv6hp) are designed to work with them and
therefore have
a minimum L3 paging protocol such as registration. In this case we do
not use L3
paging areas because there is no need.
     L3 paging areas need to be set up in a 4G type of network where
there are
no L2 paging areas. In this case our protocols define maximum L3 paging
protocol
operations because all IP paging need to be performed in Layer 3, except
on-link
paging.
    On-link paging such as paging channel on cellular networks is a nice
feature
to have from the point of view of L3 paging. If there is on-link paging
support,
then our protocols exploit it to the maximum advantage of L3 paging,
together
with L3 paging areas. If there is no onlink paging support then our
protocols
define time-slot based on-link paging operations.
     Regarding the triggers, the triggers are designed to be used with
L2 paging
areas.
In case of Layer 3 paging areas, the paging area ID is multicast in the
router
advertisements which are Layer 3 messages. So how the host or MN get
this info
in dormant mode depends on how on-link paging is supported. I guess we
need to
do more work on this, it was good you raised this issue. Thanks.

  See you in Salt Lake.


Hideaki Takusagawa wrote:

> hi Behcet,
>
> thanks for the reply.
> i did check for that mail on Oct 5 but it wasn't there,
> there must have been some problems in redirecting mail
> between my 2 accounts.... sorry about that.
>
> >   In the case when Layer 3 paging areas are supported,
> > whenever MN changes paging area, TA in the new subnet is notified using
> > layer 2 trigger. If the new TA is in the same layer 3 paging area, MN does
> > not perform any registration.
>
> how does the MN know of the L3 paging area,
> i was under the impression that the trigger was only
> to inform of the L2 paging area.
>
> > Since the paging request sent by PA is multicast in the layer 3
> > paging area, the new TA also receives the paging request.
>
> yep, i understand now, if MN has moved within a L3 paging area, IP paging
> goes
> DMA -> first TA in L3 paging area that MN was under -> DMA -> PA -> current
> TA. -> Host
>
> but this requires DMA to map L2 paging area to a PA that handles
> L3 paging area right?
> (that didn't sound right to me before....)
>
> and what about the case when MN is still under that first TA in
> in the L3 paging area, couldn't there be some shortcuts here?
>
> hideaki
>
> > -----Original Message-----
> > From: Behcet Sarikaya [mailto:behcet.sarikaya@alcatel.com]
> > Sent: Wednesday, November 07, 2001 12:35 AM
> > To: Hideaki Takusagawa
> > Subject: [Fwd: questions on LAHAP draft]
> >
> >
> > Hello Hideaki,
> >   I had sent this email to you on Oct. 5. It was sent to another address
> > of yours from which we received your email:
> > h.takusagawa@jp.fujitsu.com
> > Our mail system did not notify me of any delivery problems. So the mail
> > must have been waiting for you there.
> >   Please let me know when you  receive this email.
> > Regards,
> >
> > --
> > Behcet Sarikaya
> > Network Strategy Group, Mobile Networking Team
> > Alcatel USA M/S CTO2
> > 1201 E. Campbell Rd.
> > Richardson, TX 75081-1936 USA
> > Email : behcet.sarikaya@alcatel.com
> > Phone : (972) 996-5075 Fax : (972) 996-5174
> >
> >
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> Hideaki Takusagawa
> Network Systems Laboratories     FUJITSU LABORATORIES LTD.
> Phone: (Ext) 044-754-2786 (Int) 7112-6146 Fax: 044-754-2786
> Email: h.takusagawa@jp.fujitsu.com

--
Behcet Sarikaya
Network Strategy Group, Mobile Networking Team
Alcatel USA M/S CTO2
1201 E. Campbell Rd.
Richardson, TX 75081-1936 USA
Email: behcet.sarikaya@alcatel.com
Phone: (972) 996-5075 Fax: (972) 996 5174


From owner-seamoby@diameter.org  Thu Nov  8 16:36:19 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA08568
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Nov 2001 16:36:16 -0500 (EST)
Received: (qmail 18162 invoked by alias); 8 Nov 2001 21:17:45 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 18156 invoked by uid 200); 8 Nov 2001 21:17:45 -0000
Received: (qmail 18151 invoked from network); 8 Nov 2001 21:17:43 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 8 Nov 2001 21:17:43 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09ZZCR>; Thu, 8 Nov 2001 16:32:29 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1FABF@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: seamoby@cdma-2000.org
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject:  [seamoby] Some proposed changes to the requirements draft.
Date: Thu, 8 Nov 2001 16:32:27 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1689C.DD422110"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1689C.DD422110
Content-Type: text/plain;
	charset="iso-8859-1"

Hello Folks,
 
            Although this may be little late, I wanted to comment on the CT
requirements draft. I would like to propose some changes to the existing
draft, and also have some additional requirements that I would like to be
added. I would be grateful if the editor of the draft and the WG members
will consider my recommendations. Thanks.
 
-Sharif.
 
============================================================================
==================
 
Section 5.1.2 "The context transfer protocol MUST define a stanard
representation for coveying context information that will be interpreted
uniformly and perspicuously by different implementations"
 
I would like this to be deleted, because it has nothing to do with the
actual "transfer" of the context. 
 
Section 5.5.2 "A context update MUST preserve the integrity, and thus the
meaning, of the context at each receiving AR"
 
The paragraph following this text has nothing to do with data integrity, and
therefore should be totally removed.
 
Next, I would like to following additional requirements in the CT
requirements draft.
 
4.16 "The context transfer protocol MUST be scalable. It MUST be scalable to
millions of hosts".
 
4.17 "The context transfer protocol MUST minimize the number of signaling
messages at the sending and receiving Access Routers".
 
4.18 "The context transfer protocol MUST support both centralized and
distributed location of context information."
 
5.6.1 "The context transfer protocol MUST include methods for interworking
with any IETF IP handover solutions".
 
5.6.2 "The context transfer solution MAY include methods for interworking
with non-IETF handover solutions".
 
5.1.6 "The context transfer protocol MUST provide mechanisms for sharing
contexts or sub-divisions thereof".
 
 
 
 

------_=_NextPart_001_01C1689C.DD422110
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.3211.1700" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001><STRONG>Hello=20
Folks,</STRONG></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
Although this may be little late, I wanted to comment on the CT =
requirements=20
draft. I would like to propose some changes to the existing draft, and =
also have=20
some additional requirements that I would like to be added. I would be =
grateful=20
if the&nbsp;editor of the draft and the WG members will consider my=20
recommendations. Thanks.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001>-Sharif.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001><STRONG>Section=20
5.1.2 "The context transfer protocol MUST define a stanard =
representation for=20
coveying context information that will be interpreted uniformly and=20
perspicuously by different =
implementations"</STRONG></SPAN></FONT></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D843220521-08112001>I =
would like this to=20
be deleted, because it has nothing to do with the actual "transfer" of =
the=20
context. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001><STRONG>Section=20
5.5.2 "A context update MUST preserve the integrity, and thus the =
meaning, of=20
the context at each receiving AR"</STRONG></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D843220521-08112001>The =
paragraph=20
following this text has nothing to do with data integrity, and =
therefore should=20
be totally removed.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>Next,=20
I would like to following additional requirements in the CT =
requirements=20
draft.</SPAN></FONT></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>4.16 "The=20
context transfer protocol MUST be scalable. It MUST be scalable to =
millions of=20
hosts".</SPAN></FONT></STRONG></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>4.17 "The=20
context transfer protocol MUST minimize the number of signaling =
messages at the=20
sending and receiving Access Routers".</SPAN></FONT></STRONG></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>4.18 "The=20
context transfer protocol MUST support both centralized and distributed =
location=20
of context information."</SPAN></FONT></STRONG></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>5.6.1 "The=20
context transfer protocol MUST include methods for interworking with =
any IETF IP=20
handover solutions".</SPAN></FONT></STRONG></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001>5.6.2 "The=20
context transfer solution MAY include methods for interworking with =
non-IETF=20
handover solutions".</SPAN></FONT></STRONG></DIV>
<DIV><SPAN class=3D843220521-08112001></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D843220521-08112001><STRONG>5.1.6 "The=20
context transfer protocol MUST provide mechanisms for sharing contexts =
or=20
sub-divisions thereof".</STRONG></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D843220521-08112001></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C1689C.DD422110--


From owner-seamoby@diameter.org  Thu Nov  8 18:07:43 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11054
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Nov 2001 18:07:42 -0500 (EST)
Received: (qmail 19356 invoked by alias); 8 Nov 2001 22:50:31 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 19350 invoked by uid 200); 8 Nov 2001 22:50:30 -0000
Received: (qmail 19344 invoked from network); 8 Nov 2001 22:50:28 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 8 Nov 2001 22:50:28 -0000
Received: from DOCOMOKEMPF (dhcp43.docomo-usa.com [172.21.96.43])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fA8N6EB00464;
	Thu, 8 Nov 2001 15:06:14 -0800 (PST)
Message-ID: <002a01c168aa$3d98fd10$2b6015ac@DOCOMOKEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
References: <A1170612471BD21185B90008C7FA0A0D01F1FABF@idcpa4.pa.interdigital.com>
Subject: Re:  [seamoby] Some proposed changes to the requirements draft.
Date: Thu, 8 Nov 2001 15:08:12 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

Last Call for the Seamoby requiremets is already closed. Gary is
currently in the process of generating
a new draft,  based on the comments he received during Last Call.
Because some of those
comments were controversial, we decided to re-issue Last Call again when
the draft is available
in the Internet Drafts directory. That would be the proper time to
submit any new comments
on the document.

Could you please resubmit your comments to the mailing list after Pat or
I have issued Last
Call on the new version of the document? Thanx.

            jak



From owner-seamoby@diameter.org  Fri Nov  9 03:48:29 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA04572
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Nov 2001 03:48:28 -0500 (EST)
Received: (qmail 23627 invoked by alias); 9 Nov 2001 08:31:21 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 23621 invoked by uid 200); 9 Nov 2001 08:31:21 -0000
Received: (qmail 23616 invoked from network); 9 Nov 2001 08:31:19 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 9 Nov 2001 08:31:19 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fA98mGA01650
	for <seamoby@cdma-2000.org>; Fri, 9 Nov 2001 10:48:16 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T571d20fa4cac158f23077@esvir03nok.nokia.com>;
 Fri, 9 Nov 2001 10:47:35 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWR4WG>; Fri, 9 Nov 2001 10:47:35 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8FE5@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: fu@ee.tu-berlin.de, nsis@ietf.org
Cc: seamoby@cdma-2000.org
Subject: [seamoby] RE: [NSIS] CAR Discovery: find an  AR with satisfying/better QoS
Date: Fri, 9 Nov 2001 10:47:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Xiaoming,

> Well, the problem of finding a "good" AR which provides a
> satisfying/better QoS (than current one) possibly will be resolved by
> candidate AR (CAR) discovery solution as suggested in
> seamoby-cardiscovery-issues-01 draft. 
> 
> This explains why this requirement is not listed in the
> mip-qos-requirement draft. Provided such CAR discovery solution is
> going to be available, we only need to coordinate between the the QoS
> signaling solution and CAR here(for this problem)?!

This is possible, but I think it is premature to base
requirements for NSIS on work that has yet to be
started in seamoby (there is no work yet started on 
CAR Discovery solutions).  That being said, SeaMoby
and NSIS should co-operate on issues effecting both
WGs.

cheers,
John


From owner-seamoby@diameter.org  Fri Nov  9 09:30:05 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11955
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Nov 2001 09:30:05 -0500 (EST)
Received: (qmail 1243 invoked by alias); 9 Nov 2001 15:17:20 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1237 invoked by uid 200); 9 Nov 2001 15:17:19 -0000
Received: (qmail 1232 invoked from network); 9 Nov 2001 15:17:17 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 9 Nov 2001 15:17:17 -0000
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fA9Ct0A15437
	for <seamoby@cdma-2000.org>; Fri, 9 Nov 2001 14:55:00 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T571e02de2cac158f22077@esvir02nok.nokia.com>;
 Fri, 9 Nov 2001 14:54:19 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWSDYS>; Fri, 9 Nov 2001 14:54:19 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8FF5@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: fu@ee.tu-berlin.de, nsis@ietf.org, seamoby@cdma-2000.org
Subject: [seamoby] RE: [NSIS] CAR Discovery: find an  AR with satisfying/better QoS
Date: Fri, 9 Nov 2001 14:54:09 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Xiaoming,

> How to work it out depends on which strategy we'd follow: define 
> requirements for both, then resolve individually; or resolve 
> one of them  first, then see what's requirement burdening upon the 
> other. Anyway, I think a general analysis (something like 
> "load-balancing") considering what may be expected in both WGs 
> will be helpful. 

The best way forward would be for you to write an internet
draft on the subject & submit it to both WGs for consideration.

The IETF works best when folks how have an idea or opinion
document it.

John


From owner-seamoby@diameter.org  Fri Nov  9 11:56:21 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA18075
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Nov 2001 11:56:21 -0500 (EST)
Received: (qmail 2681 invoked by alias); 9 Nov 2001 17:43:28 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2675 invoked by uid 200); 9 Nov 2001 17:43:28 -0000
Received: (qmail 2670 invoked from network); 9 Nov 2001 17:43:26 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 9 Nov 2001 17:43:26 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09Z6AB>; Fri, 9 Nov 2001 11:53:45 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1FAC5@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: seamoby@cdma-2000.org,
        "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>,
        "'ipsec@lists.tislabs.com'" <ipsec@lists.tislabs.com>,
        "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject:  [seamoby] Security tutorial
Date: Fri, 9 Nov 2001 11:53:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Is there a security tutorial document published by the IETF, i.e. pulished
as an Informational RFC?
I am also interested in the key IETF documents on security, such as
encryption, firewall, AAA, RADIUS and DIAMETER, etc. 
I was hoping that there is a document published by the IETF, that has
pointers to thsese documents as well.

I would be grateful if someone could provide me with this information.

(Please copy me an e-mail directly, because I'm not currently subscribed to
some of these lists).

-Sharif.



From owner-seamoby@diameter.org  Fri Nov  9 13:03:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21291
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Nov 2001 13:03:08 -0500 (EST)
Received: (qmail 3810 invoked by alias); 9 Nov 2001 18:49:50 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 3804 invoked by uid 200); 9 Nov 2001 18:49:50 -0000
Received: (qmail 3799 invoked from network); 9 Nov 2001 18:49:48 -0000
Received: from motgate3.mot.com (144.189.100.103)
  by c900656-a.plstn1.sfba.home.com with SMTP; 9 Nov 2001 18:49:48 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate3.mot.com (motgate3 2.1) with ESMTP id KAA12781 for <seamoby@diameter.org>; Fri, 9 Nov 2001 10:52:32 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id KAA19285 for <seamoby@diameter.org>; Fri, 9 Nov 2001 10:52:06 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8KB6A>; Fri, 9 Nov 2001 12:01:36 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FAFA@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Charles E. Perkins'" <charliep@IPRG.nokia.com>,
        Simon Josefsson <sjosefsson@rsasecurity.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Re: Last Call on  draft-ietf-seamoby-context-transf
	er-problem-stat-03.txt
Date: Fri, 9 Nov 2001 12:01:34 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Simon,

Sorry for the delay in reply. I think Charlie brought some good
points, which are basically my questions as well.

Furthermore, even assuming that you have a centralized server
in your system for storage and transfer of keys, using this
server for transfer of security related material creates an
architecture problem, and that is:

What about the other features, such as QoS, header compression...
would you have them transferred from this centralized server or
would you have security transferred from the server, while the 
rest is transferred from the edge routers. Going down this path
means forgetting about why started to talk about context transfer
protocol in the first place: which was we wanted a generic protocol
and a generic procedure for all features, otherwise we might as well
let each feature and protocol take care of its own state and that work
would be done in the respective WG. This has been brought up before,
but obviously not the path that we have chosen for context transfer,
unless people feel differently now.

So I guess what we can do is try to address your concerns about
a lowered security "grade" at the AR and see what we need to do 
about it. 

Regards,
Madjid

-----Original Message-----
From: Charles E. Perkins [mailto:charliep@IPRG.nokia.com]
Sent: Friday, November 02, 2001 12:23 PM
To: Simon Josefsson
Cc: seamoby@diameter.org
Subject: Re: [seamoby] Re: Last Call on
draft-ietf-seamoby-context-transfer-problem-stat-03.txt



Hello Simon,

Suppose we can make the following assumptions:

1. There is a security association between two edge routers.
2. The key between the mobile node and the first
   edge router has been distributed securely.

Now suppose the mobile node moves to a new edge router.

You (Simon Josefsson) wrote:
>            ..............                _when_ you use CT of
> keying material, you should be aware that the system security might
> not be as good as when you use a centralized context server.

What would cause the security to be downgraded?

>                                                               This is
> not surprising, but I felt it should be pointed out because there may
> be situations where CT of keying material probably can't be used
> because of this problem -- when the ARs aren't physically protected
> for instance.

Does this mean that somehow the physical AR has been compromised
and its security associations revealed?  Then
1. Maybe the central server would no longer authenticate security
   messages for the mobile node?  But then, why would the previous
   AR?  Presumably, the central server would have notified its
   still-trustworthy associates about the breach in security
2. Maybe the new edge router would try to supply a key in place
   of the one derived from the previous key?  But this can be
   detected by the mobile node, I reckon, given proper encoding of
   the "real" new key...

I don't deny that there may be threats, but I don't see exactly
what they are.  Maybe we can protect against them, and make edge
security transfers as good as centralized transfers?  For that
reason, it would be good to have as complete a view of the potential
problem areas as possible.

>             I agree it is a context storage issue, and has nothing to
> do with the CT protocol actually used -- but the security of CT is not
> only about the actual protocol used.

Could you describe what you had in mind here?

Thanks!

Regards,
Charlie P.


From owner-seamoby@diameter.org  Mon Nov 12 12:42:13 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12688
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 12:42:13 -0500 (EST)
Received: (qmail 26405 invoked by alias); 12 Nov 2001 18:29:11 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26398 invoked by uid 200); 12 Nov 2001 18:29:11 -0000
Received: (qmail 26393 invoked from network); 12 Nov 2001 18:29:09 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 18:29:09 -0000
Received: from T23KEMPF (dhcp116.docomo-usa.com [172.21.96.116])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fACHeg528698
	for <seamoby@diameter.org>; Mon, 12 Nov 2001 09:40:42 -0800 (PST)
Message-ID: <003801c16ba0$ed4fe4a0$746015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@diameter.org>
Subject: [seamoby] Sharif's Comments
Date: Mon, 12 Nov 2001 09:39:04 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0035_01C16B5D.DE3E4D00"
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
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0035_01C16B5D.DE3E4D00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

After discussions with Pat, we've decided to open discussion on Sharif's =
comments immediately rather than wait for Gary to issue another draft. =
That should help speed up the process.=20

So, if anyone has discussion, please send it along.

            jak

------=_NextPart_000_0035_01C16B5D.DE3E4D00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>After discussions with Pat, we've =
decided to open=20
discussion on Sharif's comments immediately rather than wait for Gary to =
issue=20
another draft. That should help speed up the process. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So, if anyone has&nbsp;discussion, =
please send it=20
along.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; jak</FONT></DIV></BODY></HTML>

------=_NextPart_000_0035_01C16B5D.DE3E4D00--



From owner-seamoby@diameter.org  Mon Nov 12 13:06:53 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13521
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 13:06:52 -0500 (EST)
Received: (qmail 27046 invoked by alias); 12 Nov 2001 18:53:57 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27040 invoked by uid 200); 12 Nov 2001 18:53:57 -0000
Received: (qmail 27035 invoked from network); 12 Nov 2001 18:53:55 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 18:53:55 -0000
Received: from T23KEMPF (dhcp116.docomo-usa.com [172.21.96.116])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fACI5Q529291;
	Mon, 12 Nov 2001 10:05:26 -0800 (PST)
Message-ID: <009001c16ba4$62393750$746015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: Re:  [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 10:03:48 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

Comments included, marked with jak>.

Section 5.1.2 "The context transfer protocol MUST define a stanard
representation for coveying context information that will be interpreted
uniformly and perspicuously by different implementations"

I would like this to be deleted, because it has nothing to do with the
actual "transfer" of the context.

jak> Agreed. This requirement is in the domain of the individual
applications that use the protocol. Perhaps
it should say:

    Any application area that utilizes the context transfer protocol
MUST define a standard representation
    for conveying context information.


4.18 "The context transfer protocol MUST support both centralized and
distributed location of context information."

jak> I don't understand this. What is this supposed to mean?

5.6.1 "The context transfer protocol MUST include methods for
interworking
with any IETF IP handover solutions".

5.6.2 "The context transfer solution MAY include methods for
interworking
with non-IETF handover solutions".
contexts or sub-divisions thereof".

jak> These two requirements assume that there will be only one context
transfer protocol for all application areas. I tend to believe that
there will be a set of protocols, some of which are tied directly to the
handover protocol, for better integration of those areas where timing
requirements are tightly tied to handover.

            jak






From owner-seamoby@diameter.org  Mon Nov 12 14:17:33 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15781
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 14:17:32 -0500 (EST)
Received: (qmail 27717 invoked by alias); 12 Nov 2001 20:04:30 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27711 invoked by uid 200); 12 Nov 2001 20:04:30 -0000
Received: (qmail 27706 invoked from network); 12 Nov 2001 20:04:28 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 20:04:28 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09Z0JQ>; Mon, 12 Nov 2001 14:15:00 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F991@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 14:14:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hello James,


4.18 "The context transfer protocol MUST support both centralized and
distributed location of context information."

This requirement should be there so that there can be a "local" context
database (LCD)  within each AR. The LCD keeps a log of the context
parameters of every session that is currently active for the MN. 

In addition, there should be a "central"  context database (CCD). The CCD
keeps a log of all parameters that the MN is likely ever to need, whether or
not they are currently used.

Thus, LCD is a local cache memory and the CCD is a secondary storage memory.
New data in the LCD may replace that in the CCD using a write-through cache
coherency policy, whenever it needs to be updated.  When a new session
becomes active, the appropriate parameters may be read from the CCD to
replace the "unused" entries in the LCD.

The LCD is local to its AR, but the CCD is centralized and may be shared by
all the ARs.

This 2-level cache-main memory hierarchy will help reduce the size of the
LCD, and the CCD will help the context transfer itself, since it is
accessable by all the ARs.


jak> I don't understand this. What is this supposed to mean?

5.6.1 "The context transfer protocol MUST include methods for
interworking
with any IETF IP handover solutions".

5.6.2 "The context transfer solution MAY include methods for
interworking
with non-IETF handover solutions".
contexts or sub-divisions thereof".

jak> These two requirements assume that there will be only one context
transfer protocol for all application areas. I tend to believe that
there will be a set of protocols, some of which are tied directly to the
handover protocol, for better integration of those areas where timing
requirements are tightly tied to handover.

Note, Iuse the word "interworking" and not "independance". I feel that it is
better come up with a single context transfer solution that meets all the
"worst-case" handover scanarios, because otherwise we may end up
standardizing many  different context transfer protocols; each to meet a
specific handover specification, possibly leading to interworking problems,
amongst other things. 

As far as the scope of the problem SEAMOBY assigned to us, I believe, should
be to come up with a single context transfer protocol.

Did you have any comments to my other requirements?

-Sharif


From owner-seamoby@diameter.org  Mon Nov 12 15:32:47 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17613
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 15:32:42 -0500 (EST)
Received: (qmail 28381 invoked by alias); 12 Nov 2001 21:18:55 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28375 invoked by uid 200); 12 Nov 2001 21:18:55 -0000
Received: (qmail 28370 invoked from network); 12 Nov 2001 21:18:53 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 21:18:53 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fACKThS24818
	for <seamoby@cdma-2000.org>; Mon, 12 Nov 2001 15:29:43 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Mon, 12 Nov 2001 15:30:10 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W3291DKD>; Mon, 12 Nov 2001 15:29:21 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4630@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 15:29:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16BB8.B39DEAF0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16BB8.B39DEAF0
Content-Type: text/plain;
	charset="iso-8859-1"

James, Sharif:

  Just to clarify:

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: November 12, 2001 13:04
> To: Shahrier, Sharif M.; seamoby
> Cc: Shahrier, Sharif M.
> Subject: Re: [seamoby] Some proposed changes to the 
> requirements draft.
> 
> 
> Sharif,
> 
> Comments included, marked with jak>.
> 
> Section 5.1.2 "The context transfer protocol MUST define a stanard
> representation for coveying context information that will be 
> interpreted
> uniformly and perspicuously by different implementations"
> 
> I would like this to be deleted, because it has nothing to do with the
> actual "transfer" of the context.
> 
> jak> Agreed. This requirement is in the domain of the individual
> applications that use the protocol. Perhaps
> it should say:
> 
>     Any application area that utilizes the context transfer protocol
> MUST define a standard representation
>     for conveying context information.

The wording may need to be fixed, but the requirement is not as you
are both interpreting it. The "standard representation"
referred to is the representation of the data chunks, or objects,
in the context transfer protocol that are used to contain the context.
The actual context is encapsulated within these data chunks, and the 
representation of that context is opaque to context transfer. What is
needed is a standard representation for these containers.

The words do say "a standard representation for *conveying*"; the
key words are "for conveying". They do not say "a standard representation
for the context" which is how you are both interpreting the requirement.

Again, we can clarify the wording, but the requirement still makes sense.
As for James proposal, this would be a new requirement.

Gary

------_=_NextPart_001_01C16BB8.B39DEAF0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>James, Sharif:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; Just to clarify:</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:kempf@docomolabs-usa.com">mailto:kempf@docomolabs-usa.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: November 12, 2001 13:04</FONT>
<BR><FONT SIZE=2>&gt; To: Shahrier, Sharif M.; seamoby</FONT>
<BR><FONT SIZE=2>&gt; Cc: Shahrier, Sharif M.</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [seamoby] Some proposed changes to the </FONT>
<BR><FONT SIZE=2>&gt; requirements draft.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Sharif,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Comments included, marked with jak&gt;.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Section 5.1.2 &quot;The context transfer protocol MUST define a stanard</FONT>
<BR><FONT SIZE=2>&gt; representation for coveying context information that will be </FONT>
<BR><FONT SIZE=2>&gt; interpreted</FONT>
<BR><FONT SIZE=2>&gt; uniformly and perspicuously by different implementations&quot;</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I would like this to be deleted, because it has nothing to do with the</FONT>
<BR><FONT SIZE=2>&gt; actual &quot;transfer&quot; of the context.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; jak&gt; Agreed. This requirement is in the domain of the individual</FONT>
<BR><FONT SIZE=2>&gt; applications that use the protocol. Perhaps</FONT>
<BR><FONT SIZE=2>&gt; it should say:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Any application area that utilizes the context transfer protocol</FONT>
<BR><FONT SIZE=2>&gt; MUST define a standard representation</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; for conveying context information.</FONT>
</P>

<P><FONT SIZE=2>The wording may need to be fixed, but the requirement is not as you</FONT>
<BR><FONT SIZE=2>are both interpreting it. The &quot;standard representation&quot;</FONT>
<BR><FONT SIZE=2>referred to is the representation of the data chunks, or objects,</FONT>
<BR><FONT SIZE=2>in the context transfer protocol that are used to contain the context.</FONT>
<BR><FONT SIZE=2>The actual context is encapsulated within these data chunks, and the </FONT>
<BR><FONT SIZE=2>representation of that context is opaque to context transfer. What is</FONT>
<BR><FONT SIZE=2>needed is a standard representation for these containers.</FONT>
</P>

<P><FONT SIZE=2>The words do say &quot;a standard representation for *conveying*&quot;; the</FONT>
<BR><FONT SIZE=2>key words are &quot;for conveying&quot;. They do not say &quot;a standard representation</FONT>
<BR><FONT SIZE=2>for the context&quot; which is how you are both interpreting the requirement.</FONT>
</P>

<P><FONT SIZE=2>Again, we can clarify the wording, but the requirement still makes sense.</FONT>
<BR><FONT SIZE=2>As for James proposal, this would be a new requirement.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16BB8.B39DEAF0--


From owner-seamoby@diameter.org  Mon Nov 12 15:53:54 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18233
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 15:53:29 -0500 (EST)
Received: (qmail 28964 invoked by alias); 12 Nov 2001 21:39:05 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28958 invoked by uid 200); 12 Nov 2001 21:39:05 -0000
Received: (qmail 28953 invoked from network); 12 Nov 2001 21:39:03 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 21:39:03 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09Z0SC>; Mon, 12 Nov 2001 15:49:35 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F993@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 15:49:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16BBB.88A18E30"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16BBB.88A18E30
Content-Type: text/plain;
	charset="iso-8859-1"

Gary,
> 
>     Any application area that utilizes the context transfer protocol 
> MUST define a standard representation 
>     for conveying context information. 
The wording may need to be fixed, but the requirement is not as you 
are both interpreting it. The "standard representation" 
referred to is the representation of the data chunks, or objects, 
in the context transfer protocol that are used to contain the context. 
The actual context is encapsulated within these data chunks, and the 
representation of that context is opaque to context transfer. What is 


I was not involved with the earlier drafting of this requirement. Could you
please explain why it's necessary
To define representation of data chunks for encapsulating the context?
I would prefer to just send the context information as part of the DATA
SEGMENT in a regular IP datagram, without any form
Of encapsulation .
-Sharif.
                                      

------_=_NextPart_001_01C16BBB.88A18E30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16B92.656E9DF0">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p><font size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:navy'>Gary,</span></font><font size=3D2 color=3Dnavy><span =
style=3D'font-size:
10.0pt;color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font></p=
>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Any application area that =
utilizes
the context transfer protocol</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; MUST define a standard =
representation</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt;&nbsp;&nbsp;&nbsp;&nbsp; for conveying context =
information.</span></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p style=3D'tab-stops:112.5pt'><font size=3D2 color=3Dblack =
face=3D"Times New Roman"><span
style=3D'font-size:10.0pt;color:black'>The wording may need to be =
fixed, but the
requirement is not as you</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>are both interpreting it. The &quot;standard =
representation&quot;</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>referred to is the representation of the data chunks, or =
objects,</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>in the context transfer protocol that are used to contain =
the
context.</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>The actual context is encapsulated within these data =
chunks, and
the </span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>representation of that context is opaque to context =
transfer. What
is</span></font><font color=3Dblack><span style=3D'color:black'> <br
style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]></span></font><font color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p style=3D'tab-stops:112.5pt'><span class=3DEmailStyle19><font =
size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I was not involved with the earlier drafting of this =
requirement. Could
you please explain why it&#8217;s =
necessary<o:p></o:p></span></font></span></p>

<p style=3D'tab-stops:112.5pt'><span class=3DEmailStyle19><font =
size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>To define representation of data chunks for encapsulating the =
context?<o:p></o:p></span></font></span></p>

<p style=3D'tab-stops:112.5pt'><span class=3DEmailStyle19><font =
size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I would prefer to just send the context information as part of =
the DATA
SEGMENT in a regular IP datagram, without any =
form<o:p></o:p></span></font></span></p>

<p style=3D'tab-stops:112.5pt'><span class=3DEmailStyle19><font =
size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Of encapsulation .<o:p></o:p></span></font></span></p>

<p style=3D'tab-stops:112.5pt'><span class=3DEmailStyle19><font =
size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

<p style=3D'tab-stops:112.5pt'><font size=3D3 color=3Dnavy =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;color:navy'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

</div>

</body>

</html>

------_=_NextPart_001_01C16BBB.88A18E30--


From owner-seamoby@diameter.org  Mon Nov 12 17:03:59 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20306
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 17:03:44 -0500 (EST)
Received: (qmail 29682 invoked by alias); 12 Nov 2001 22:48:27 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29676 invoked by uid 200); 12 Nov 2001 22:48:27 -0000
Received: (qmail 29671 invoked from network); 12 Nov 2001 22:48:25 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 22:48:25 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fACLxLS03287
	for <seamoby@cdma-2000.org>; Mon, 12 Nov 2001 16:59:21 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Mon, 12 Nov 2001 16:59:34 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W3291FQD>; Mon, 12 Nov 2001 16:57:36 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4636@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        seamoby <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 16:57:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16BC5.08F30C40"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16BC5.08F30C40
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
The thought was that the payload would be comprised of one or more of these
"chunks", each one representing a different feature context. The container
format would have to at least to provide a type field (where the type would
indicate the feature the context belonged to, but would be simply be used by
the
receiving AR to dispatch the container content to the appropriate entity),
and, a length field. There may be more to the container format, but nothing 
comes to mind.
 
Of course, the actually container representation is still to be determined.
The requirement states only that a representation must be defined.
 
There are plenty of analogies in other IETF protocols for this mechanism for
conveying pieces of similar but different data in one IP payload.
 
Gary
 
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 12, 2001 15:50
To: Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; Shahrier, Sharif M.;
seamoby
Cc: Shahrier, Sharif M.
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
> 
>     Any application area that utilizes the context transfer protocol 
> MUST define a standard representation 
>     for conveying context information. 
The wording may need to be fixed, but the requirement is not as you 
are both interpreting it. The "standard representation" 
referred to is the representation of the data chunks, or objects, 
in the context transfer protocol that are used to contain the context. 
The actual context is encapsulated within these data chunks, and the 
representation of that context is opaque to context transfer. What is 


I was not involved with the earlier drafting of this requirement. Could you
please explain why it's necessary
To define representation of data chunks for encapsulating the context?
I would prefer to just send the context information as part of the DATA
SEGMENT in a regular IP datagram, without any form
Of encapsulation .
-Sharif.
                                      

------_=_NextPart_001_01C16BC5.08F30C40
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16B92.656E9DF0" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>The&nbsp;thought was that the payload would be 
comprised of one or more of these</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>"chunks", each one representing a different feature 
context. The container</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>format would have to at least to provide a type field 
(where the type would</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>indicate the feature the context belonged to, but would 
be&nbsp;simply be used by the</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>receiving AR to dispatch the container content to the 
appropriate entity),</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>and, a length field. There may be more to the container 
format, but nothing </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>comes to mind.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=788375621-12112001>Of 
course, the actually container representation is still to be 
determined.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=788375621-12112001>The 
requirement states only that a representation must be 
defined.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>There are plenty of analogies in other IETF protocols 
for this mechanism for</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>conveying pieces of similar but different data in one 
IP payload.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001>Gary</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=788375621-12112001></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 12, 2001 
  15:50<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; Shahrier, 
  Sharif M.; seamoby<BR><B>Cc:</B> Shahrier, Sharif M.<BR><B>Subject:</B> RE: 
  [seamoby] Some proposed changes to the requirements 
draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P><FONT color=navy face="Times New Roman" size=2><SPAN 
  style="COLOR: navy; FONT-SIZE: 10pt">Gary,</SPAN></FONT><FONT color=navy 
  size=2><SPAN 
  style="COLOR: navy; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt; </SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><FONT color=black 
  size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp; Any 
  application area that utilizes the context transfer 
  protocol</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"> 
  <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt; MUST define a standard 
  representation</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"> 
  <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp; for 
  conveying context information.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style="tab-stops: 112.5pt"><FONT color=black face="Times New Roman" 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">The wording may need to be 
  fixed, but the requirement is not as you</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">are both interpreting it. The "standard 
  representation"</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"> 
  <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">referred to is the representation of the 
  data chunks, or objects,</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">in the context transfer protocol that 
  are used to contain the context.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">The actual context is encapsulated 
  within these data chunks, and the </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"><BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">representation of that context is opaque 
  to context transfer. What is</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR style="mso-special-character: line-break"><![if !supportLineBreakNewLine]><BR 
  style="mso-special-character: line-break"><![endif]></SPAN></FONT><FONT 
  color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style="tab-stops: 112.5pt"><SPAN class=EmailStyle19><FONT color=navy 
  face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I was 
  not involved with the earlier drafting of this requirement. Could you please 
  explain why it&#8217;s necessary<o:p></o:p></SPAN></FONT></SPAN></P>
  <P style="tab-stops: 112.5pt"><SPAN class=EmailStyle19><FONT color=navy 
  face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">To 
  define representation of data chunks for encapsulating the 
  context?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P style="tab-stops: 112.5pt"><SPAN class=EmailStyle19><FONT color=navy 
  face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  would prefer to just send the context information as part of the DATA SEGMENT 
  in a regular IP datagram, without any form<o:p></o:p></SPAN></FONT></SPAN></P>
  <P style="tab-stops: 112.5pt"><SPAN class=EmailStyle19><FONT color=navy 
  face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Of 
  encapsulation .<o:p></o:p></SPAN></FONT></SPAN></P>
  <P style="tab-stops: 112.5pt"><SPAN class=EmailStyle19><FONT color=navy 
  face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P style="tab-stops: 112.5pt"><FONT color=navy face="Times New Roman" 
  size=3><SPAN style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN></SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16BC5.08F30C40--


From owner-seamoby@diameter.org  Mon Nov 12 17:20:13 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20885
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 17:20:10 -0500 (EST)
Received: (qmail 30300 invoked by alias); 12 Nov 2001 23:07:05 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 30294 invoked by uid 200); 12 Nov 2001 23:07:05 -0000
Received: (qmail 30289 invoked from network); 12 Nov 2001 23:07:04 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 12 Nov 2001 23:07:04 -0000
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 OAA11264;
	Mon, 12 Nov 2001 14:18:38 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fACMIbG18336;
	Mon, 12 Nov 2001 14:18:37 -0800
X-mProtect:  Mon, 12 Nov 2001 14:18:37 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpda1vE5z; Mon, 12 Nov 2001 14:18:36 PST
Message-ID: <3BF04ABC.D68DB2DE@iprg.nokia.com>
Date: Mon, 12 Nov 2001 14:18:36 -0800
From: Rajeev Koodli <rajeev@IPRG.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
References: <009001c16ba4$62393750$746015ac@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello James,


James Kempf wrote:

> Sharif,
>
> Comments included, marked with jak>.
>
> Section 5.1.2 "The context transfer protocol MUST define a stanard
> representation for coveying context information that will be interpreted
> uniformly and perspicuously by different implementations"
>
> I would like this to be deleted, because it has nothing to do with the
> actual "transfer" of the context.
>
> jak> Agreed. This requirement is in the domain of the individual
> applications that use the protocol. Perhaps
> it should say:
>

As Gary pointed out, this requirement is meant for interpreting the context
blob that is carried. In a message format, before the actual context
parameters are enumerated, an object (e.g., an IANA type number) identifies
the feature context so that a receiver can parse, interpret and act on.

Also, your use of the term of "application" may be confusing. We have been
using the term "feature" from the begining to refer to QoS, HC, security
etc..If by application you mean something else, please excuse this note and
explain further.

Regards,

-Rajeev



>
>     Any application area that utilizes the context transfer protocol
> MUST define a standard representation
>     for conveying context information.
>
> 4.18 "The context transfer protocol MUST support both centralized and
> distributed location of context information."
>
> jak> I don't understand this. What is this supposed to mean?
>
> 5.6.1 "The context transfer protocol MUST include methods for
> interworking
> with any IETF IP handover solutions".
>
> 5.6.2 "The context transfer solution MAY include methods for
> interworking
> with non-IETF handover solutions".
> contexts or sub-divisions thereof".
>
> jak> These two requirements assume that there will be only one context
> transfer protocol for all application areas. I tend to believe that
> there will be a set of protocols, some of which are tied directly to the
> handover protocol, for better integration of those areas where timing
> requirements are tightly tied to handover.

>
>
>             jak



From owner-seamoby@diameter.org  Mon Nov 12 18:16:22 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22635
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 18:16:17 -0500 (EST)
Received: (qmail 31076 invoked by alias); 13 Nov 2001 00:03:19 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 31070 invoked by uid 200); 13 Nov 2001 00:03:19 -0000
Received: (qmail 31062 invoked by uid 500); 13 Nov 2001 00:03:17 -0000
Date: Mon, 12 Nov 2001 16:03:17 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011112160317.F30901@charizard.diameter.org>
Mail-Followup-To: Gary Kenward <gkenward@nortelnetworks.com>,
	'James Kempf' <kempf@docomolabs-usa.com>,
	"Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
	seamoby <seamoby@cdma-2000.org>
References: <9FBD322B7824D511B36900508BF93C9C01AA4630@zcard031.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <9FBD322B7824D511B36900508BF93C9C01AA4630@zcard031.ca.nortel.com>; from gkenward@nortelnetworks.com on Mon, Nov 12, 2001 at 03:29:17PM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

I agree with Gary.

PatC
On Mon, Nov 12, 2001 at 03:29:17PM -0500, Gary Kenward wrote:
> James, Sharif:
> 
>   Just to clarify:
> 
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: November 12, 2001 13:04
> > To: Shahrier, Sharif M.; seamoby
> > Cc: Shahrier, Sharif M.
> > Subject: Re: [seamoby] Some proposed changes to the 
> > requirements draft.
> > 
> > 
> > Sharif,
> > 
> > Comments included, marked with jak>.
> > 
> > Section 5.1.2 "The context transfer protocol MUST define a stanard
> > representation for coveying context information that will be 
> > interpreted
> > uniformly and perspicuously by different implementations"
> > 
> > I would like this to be deleted, because it has nothing to do with the
> > actual "transfer" of the context.
> > 
> > jak> Agreed. This requirement is in the domain of the individual
> > applications that use the protocol. Perhaps
> > it should say:
> > 
> >     Any application area that utilizes the context transfer protocol
> > MUST define a standard representation
> >     for conveying context information.
> 
> The wording may need to be fixed, but the requirement is not as you
> are both interpreting it. The "standard representation"
> referred to is the representation of the data chunks, or objects,
> in the context transfer protocol that are used to contain the context.
> The actual context is encapsulated within these data chunks, and the 
> representation of that context is opaque to context transfer. What is
> needed is a standard representation for these containers.
> 
> The words do say "a standard representation for *conveying*"; the
> key words are "for conveying". They do not say "a standard representation
> for the context" which is how you are both interpreting the requirement.
> 
> Again, we can clarify the wording, but the requirement still makes sense.
> As for James proposal, this would be a new requirement.
> 
> Gary


From owner-seamoby@diameter.org  Mon Nov 12 18:19:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22739
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 18:19:04 -0500 (EST)
Received: (qmail 31578 invoked by alias); 13 Nov 2001 00:05:45 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 31572 invoked by uid 200); 13 Nov 2001 00:05:44 -0000
Received: (qmail 31564 invoked by uid 500); 13 Nov 2001 00:05:43 -0000
Date: Mon, 12 Nov 2001 16:05:43 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        seamoby <seamoby@cdma-2000.org>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011112160543.G30901@charizard.diameter.org>
Mail-Followup-To: Gary Kenward <gkenward@nortelnetworks.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	'James Kempf' <kempf@docomolabs-usa.com>,
	seamoby <seamoby@cdma-2000.org>
References: <9FBD322B7824D511B36900508BF93C9C01AA4636@zcard031.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <9FBD322B7824D511B36900508BF93C9C01AA4636@zcard031.ca.nortel.com>; from gkenward@nortelnetworks.com on Mon, Nov 12, 2001 at 04:57:34PM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

Sharif,

Gary's comments below show WG consensus, and unless other folks chime in 
here to show that we don't have consensus I'd prefer to leave this one dead.

Thanks,

PatC
On Mon, Nov 12, 2001 at 04:57:34PM -0500, Gary Kenward wrote:
> Sharif:
>  
> The thought was that the payload would be comprised of one or more of these
> "chunks", each one representing a different feature context. The container
> format would have to at least to provide a type field (where the type would
> indicate the feature the context belonged to, but would be simply be used by
> the
> receiving AR to dispatch the container content to the appropriate entity),
> and, a length field. There may be more to the container format, but nothing 
> comes to mind.
>  
> Of course, the actually container representation is still to be determined.
> The requirement states only that a representation must be defined.
>  
> There are plenty of analogies in other IETF protocols for this mechanism for
> conveying pieces of similar but different data in one IP payload.
>  
> Gary
>  
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 12, 2001 15:50
> To: Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; Shahrier, Sharif M.;
> seamoby
> Cc: Shahrier, Sharif M.
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
> 
> 
> Gary,
> > 
> >     Any application area that utilizes the context transfer protocol 
> > MUST define a standard representation 
> >     for conveying context information. 
> The wording may need to be fixed, but the requirement is not as you 
> are both interpreting it. The "standard representation" 
> referred to is the representation of the data chunks, or objects, 
> in the context transfer protocol that are used to contain the context. 
> The actual context is encapsulated within these data chunks, and the 
> representation of that context is opaque to context transfer. What is 
> 
> 
> I was not involved with the earlier drafting of this requirement. Could you
> please explain why it's necessary
> To define representation of data chunks for encapsulating the context?
> I would prefer to just send the context information as part of the DATA
> SEGMENT in a regular IP datagram, without any form
> Of encapsulation .
> -Sharif.
>                                       


From owner-seamoby@diameter.org  Mon Nov 12 20:19:55 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26248
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 20:19:54 -0500 (EST)
Received: (qmail 32495 invoked by alias); 13 Nov 2001 02:06:44 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 32489 invoked by uid 200); 13 Nov 2001 02:06:43 -0000
Received: (qmail 32484 invoked from network); 13 Nov 2001 02:06:41 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 02:06:41 -0000
Received: from T23KEMPF (dhcp152.docomo-usa.com [172.21.96.152])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAD1IA510334;
	Mon, 12 Nov 2001 17:18:10 -0800 (PST)
Message-ID: <000e01c16be0$d61dad40$986015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
References: <9FBD322B7824D511B36900508BF93C9C01AA4630@zcard031.ca.nortel.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 17:16:32 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary,

> The wording may need to be fixed, but the requirement is not as you
> are both interpreting it. The "standard representation"
> referred to is the representation of the data chunks, or objects,
> in the context transfer protocol that are used to contain the context.
> The actual context is encapsulated within these data chunks, and the
> representation of that context is opaque to context transfer. What is
> needed is a standard representation for these containers.
>
> The words do say "a standard representation for *conveying*"; the
> key words are "for conveying". They do not say "a standard
representation
> for the context" which is how you are both interpreting the
requirement.
>
> Again, we can clarify the wording, but the requirement still makes
sense.
> As for James proposal, this would be a new requirement.
>

I misunderstood the requirement. I think you need to reword it to avoid
the possibility of misunderstanding. How about:

    The context transfer protocol MUST define a standardized container
    format for encapsulating and conveying context information.
Interpretation
    of the context information within the container is the domain of the
application
    for which context is being transfered. Applications SHOULD define an
interoperable
    format for context information if they want to use the context
transfer protocol.

Or, you can simply include the first sentence if you feel that the rest
is too controversial
or would expand the requirement beyond what is currently agreed.

            jak



From owner-seamoby@diameter.org  Mon Nov 12 20:35:54 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26579
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 20:35:52 -0500 (EST)
Received: (qmail 596 invoked by alias); 13 Nov 2001 02:22:44 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 589 invoked by uid 200); 13 Nov 2001 02:22:43 -0000
Received: (qmail 584 invoked from network); 13 Nov 2001 02:22:42 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 02:22:42 -0000
Received: from T23KEMPF (dhcp152.docomo-usa.com [172.21.96.152])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAD1Y9510680;
	Mon, 12 Nov 2001 17:34:09 -0800 (PST)
Message-ID: <002a01c16be3$1152ecc0$986015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@IPRG.nokia.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <seamoby@cdma-2000.org>
References: <009001c16ba4$62393750$746015ac@T23KEMPF> <3BF04ABC.D68DB2DE@iprg.nokia.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 17:32:31 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Rajeev,

I actually meant "feature." I agree with the idea of having the blob
identified, I think the wording needs some work, since
apparently both Sharif and I misunderstood the nature of the
requirement.

        jak

----- Original Message -----
From: "Rajeev Koodli" <rajeev@IPRG.nokia.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>;
<seamoby@cdma-2000.org>
Sent: Monday, November 12, 2001 2:18 PM
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


>
> Hello James,
>
>
> James Kempf wrote:
>
> > Sharif,
> >
> > Comments included, marked with jak>.
> >
> > Section 5.1.2 "The context transfer protocol MUST define a stanard
> > representation for coveying context information that will be
interpreted
> > uniformly and perspicuously by different implementations"
> >
> > I would like this to be deleted, because it has nothing to do with
the
> > actual "transfer" of the context.
> >
> > jak> Agreed. This requirement is in the domain of the individual
> > applications that use the protocol. Perhaps
> > it should say:
> >
>
> As Gary pointed out, this requirement is meant for interpreting the
context
> blob that is carried. In a message format, before the actual context
> parameters are enumerated, an object (e.g., an IANA type number)
identifies
> the feature context so that a receiver can parse, interpret and act
on.
>
> Also, your use of the term of "application" may be confusing. We have
been
> using the term "feature" from the begining to refer to QoS, HC,
security
> etc..If by application you mean something else, please excuse this
note and
> explain further.
>
> Regards,
>
> -Rajeev
>
>
>
> >
> >     Any application area that utilizes the context transfer protocol
> > MUST define a standard representation
> >     for conveying context information.
> >
> > 4.18 "The context transfer protocol MUST support both centralized
and
> > distributed location of context information."
> >
> > jak> I don't understand this. What is this supposed to mean?
> >
> > 5.6.1 "The context transfer protocol MUST include methods for
> > interworking
> > with any IETF IP handover solutions".
> >
> > 5.6.2 "The context transfer solution MAY include methods for
> > interworking
> > with non-IETF handover solutions".
> > contexts or sub-divisions thereof".
> >
> > jak> These two requirements assume that there will be only one
context
> > transfer protocol for all application areas. I tend to believe that
> > there will be a set of protocols, some of which are tied directly to
the
> > handover protocol, for better integration of those areas where
timing
> > requirements are tightly tied to handover.
>
> >
> >
> >             jak
>
>



From owner-seamoby@diameter.org  Mon Nov 12 20:40:40 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26696
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Nov 2001 20:40:38 -0500 (EST)
Received: (qmail 1173 invoked by alias); 13 Nov 2001 02:27:33 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1167 invoked by uid 200); 13 Nov 2001 02:27:33 -0000
Received: (qmail 1162 invoked from network); 13 Nov 2001 02:27:31 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 02:27:31 -0000
Received: from T23KEMPF (dhcp152.docomo-usa.com [172.21.96.152])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAD1d0510819;
	Mon, 12 Nov 2001 17:39:00 -0800 (PST)
Message-ID: <005c01c16be3$bf0923c0$986015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
        "Gary Kenward" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
References: <9FBD322B7824D511B36900508BF93C9C01AA4630@zcard031.ca.nortel.com> <000e01c16be0$d61dad40$986015ac@T23KEMPF>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Mon, 12 Nov 2001 17:37:22 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Re. Pat's email, how about just:

    The context transfer protocol MUST define a standardized container
    format for encapsulating and conveying context information.
   Interpretation of the context information within the container is the
domain of the
   feature  for which context is being transfered.

This should avoid the kind of misunderstanding that I apparently had.

        jak

----- Original Message -----
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Sent: Monday, November 12, 2001 5:16 PM
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


> Gary,
>
> > The wording may need to be fixed, but the requirement is not as you
> > are both interpreting it. The "standard representation"
> > referred to is the representation of the data chunks, or objects,
> > in the context transfer protocol that are used to contain the
context.
> > The actual context is encapsulated within these data chunks, and the
> > representation of that context is opaque to context transfer. What
is
> > needed is a standard representation for these containers.
> >
> > The words do say "a standard representation for *conveying*"; the
> > key words are "for conveying". They do not say "a standard
> representation
> > for the context" which is how you are both interpreting the
> requirement.
> >
> > Again, we can clarify the wording, but the requirement still makes
> sense.
> > As for James proposal, this would be a new requirement.
> >
>
> I misunderstood the requirement. I think you need to reword it to
avoid
> the possibility of misunderstanding. How about:
>
>     The context transfer protocol MUST define a standardized container
>     format for encapsulating and conveying context information.
> Interpretation
>     of the context information within the container is the domain of
the
> application
>     for which context is being transfered. Applications SHOULD define
an
> interoperable
>     format for context information if they want to use the context
> transfer protocol.
>
> Or, you can simply include the first sentence if you feel that the
rest
> is too controversial
> or would expand the requirement beyond what is currently agreed.
>
>             jak
>
>



From owner-seamoby@diameter.org  Tue Nov 13 02:23:22 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17465
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 02:23:21 -0500 (EST)
Received: (qmail 2118 invoked by alias); 13 Nov 2001 08:10:24 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2112 invoked by uid 200); 13 Nov 2001 08:10:24 -0000
Received: (qmail 2107 invoked from network); 13 Nov 2001 08:10:21 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 08:10:21 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAD7N6A21062
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 09:23:06 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57316c6ebbac158f23076@esvir03nok.nokia.com>;
 Tue, 13 Nov 2001 09:22:24 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWT8JR>; Tue, 13 Nov 2001 09:22:24 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D901C@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
        seamoby@cdma-2000.org
Cc: Sharif.Shahrier@InterDigital.com
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 09:22:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

> Comments included, marked with jak>.
> 
> Section 5.1.2 "The context transfer protocol MUST define a stanard
> representation for coveying context information that will be 
> interpreted
> uniformly and perspicuously by different implementations"
> 
> I would like this to be deleted, because it has nothing to do with the
> actual "transfer" of the context.
> 
> jak> Agreed. This requirement is in the domain of the individual
> applications that use the protocol. Perhaps
> it should say:
> 
>     Any application area that utilizes the context transfer protocol
>     MUST define a standard representation for conveying context 
>     information.

I agree, but SHOULD might be more applicable than MUST, as I 
see this as more of a recommendation as opposed to an 
absolute requirement.

Then a general comment on Sharif's proposals:

> 4.18 "The context transfer protocol MUST support both centralized and
> distributed location of context information."
> 
> 5.6.1 "The context transfer protocol MUST include methods for
> interworking with any IETF IP handover solutions".
> 
> 5.6.2 "The context transfer solution MAY include methods for
> interworking with non-IETF handover solutions".
> contexts or sub-divisions thereof".

Unless we have a reason why these are requirements,
I don't think we can support adding these into the document.

br,
John


From owner-seamoby@diameter.org  Tue Nov 13 02:25:44 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17480
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 02:25:43 -0500 (EST)
Received: (qmail 2437 invoked by alias); 13 Nov 2001 08:11:52 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2431 invoked by uid 200); 13 Nov 2001 08:11:51 -0000
Received: (qmail 2419 invoked from network); 13 Nov 2001 08:11:49 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 08:11:49 -0000
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAD7OYA22057
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 09:24:34 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57316dbee2ac158f24076@esvir04nok.ntc.nokia.com>;
 Tue, 13 Nov 2001 09:23:50 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWT8M2>; Tue, 13 Nov 2001 09:23:50 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D901D@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: Sharif.Shahrier@InterDigital.com, kempf@docomolabs-usa.com,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 09:23:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Sharif,

> 4.18 "The context transfer protocol MUST support both centralized and
> distributed location of context information."
> 
> This requirement should be there so that there can be a 
> "local" context
> database (LCD)  within each AR. The LCD keeps a log of the context
> parameters of every session that is currently active for the MN. 

I don't support this requirement.  This is getting very
close to an implementational issue, not a general requirement.

It sounds like you want a Context Transfer proxy or something
along those lines.  I don't see anything explicitly requiring
this.

John


From owner-seamoby@diameter.org  Tue Nov 13 04:59:01 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA18753
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 04:59:00 -0500 (EST)
Received: (qmail 3363 invoked by alias); 13 Nov 2001 10:46:04 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 3357 invoked by uid 200); 13 Nov 2001 10:46:04 -0000
Received: (qmail 3352 invoked from network); 13 Nov 2001 10:46:02 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 10:46:02 -0000
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAD9wmA18181
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 11:58:48 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5731fafbf6ac158f24076@esvir04nok.ntc.nokia.com>;
 Tue, 13 Nov 2001 11:58:06 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAW4HKR>; Tue, 13 Nov 2001 11:58:06 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09BC08@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: Sharif.Shahrier@InterDigital.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 11:58:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Sharif,

My comments, inline:

> Next, I would like to following additional requirements in the CT 
> requirements draft.

> 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> scalable to millions of hosts".

This is 'motherhood & apple pie' text (i.e. - noone would really
disagree). I don't know how this adds anything to the text.  
Additionally, I would suggest SHOULD rather than MUST is
what you mean.

> 4.17 "The context transfer protocol MUST minimize the number of 
> signaling messages at the sending and receiving Access Routers".

I don't see the need for this.  I don't think this should be
a requirement.

> 4.18 "The context transfer protocol MUST support both centralized 
> and distributed location of context information."

I don't think that there is any concensus for this kind of 
requirement to be added.

> 5.6.1 "The context transfer protocol MUST include methods for 
> interworking with any IETF IP handover solutions".
>
> 5.6.2 "The context transfer solution MAY include methods for 
> interworking with non-IETF handover solutions".
>
> 5.1.6 "The context transfer protocol MUST provide mechanisms for 
> sharing contexts or sub-divisions thereof".

I don't agree that the last 3 should be added.

John


From owner-seamoby@diameter.org  Tue Nov 13 09:55:12 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27632
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 09:55:07 -0500 (EST)
Received: (qmail 4622 invoked by alias); 13 Nov 2001 15:40:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4616 invoked by uid 200); 13 Nov 2001 15:40:24 -0000
Received: (qmail 4611 invoked from network); 13 Nov 2001 15:40:23 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 15:40:23 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095BCD>; Tue, 13 Nov 2001 09:50:57 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F995@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 09:50:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C52.99F0D5A0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C52.99F0D5A0
Content-Type: text/plain;
	charset="iso-8859-1"

 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C52.99F0D5A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C29.76A57B60">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3D"#993366" face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:#993366'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3D"#993366"><span =
style=3D'color:#993366;mso-color-alt:windowtext'><o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D3 color=3D"#993366" face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:#993366'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3D"#993366"><span =
style=3D'color:#993366;mso-color-alt:windowtext'><o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D3 color=3D"#993366" face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:#993366'>I have some issues with the =
following
requirement in the CT draft.</span></font><font color=3D"#993366"><span
style=3D'color:#993366;mso-color-alt:windowtext'><o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></fon=
t></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>4.9 The entities transferring context MUST have completed a =
mutual authentication
process prior to<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>initiating the transfer.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I don&#8217;t support this =
requirement.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>It appears to me this may not fit the case for =
&#8220;break-before-make&#8221;
handover . <span style=3D"mso-spacerun: yes">&nbsp;</span>For instance, =
the
mobile may break connection with the =
old<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>AP, and re-establish connection with the new AP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Assuming that the context is transferred prior to =
re-establishing the
new connection.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>The mobile will need to re-authenticate after it makes a new =
connection
at its new AP.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I have seen several practical cases that supports this scanario, =
thus I
feel it is necessary for authentication after the transfer of context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>in =
&#8220;break-before-make&#8221;.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C16C52.99F0D5A0--


From owner-seamoby@diameter.org  Tue Nov 13 10:14:02 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28983
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 10:14:02 -0500 (EST)
Received: (qmail 5186 invoked by alias); 13 Nov 2001 16:01:06 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 5180 invoked by uid 200); 13 Nov 2001 16:01:05 -0000
Received: (qmail 5175 invoked from network); 13 Nov 2001 16:01:03 -0000
Received: from netmail2.alcatel.com (128.251.168.51)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 16:01:03 -0000
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id JAA01384;
	Tue, 13 Nov 2001 09:13:09 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id fADFD8117882;
	Tue, 13 Nov 2001 09:13:08 -0600 (CST)
Message-ID: <3BF138DC.22365174@alcatel.com>
Date: Tue, 13 Nov 2001 09:14:36 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: john.loughney@nokia.com
CC: seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09BC08@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,
  I think that IETF does not want the words like MUST, SHOULD in a
requirements document. The requirements are a must anyway.

My 0.02 euros.

john.loughney@nokia.com wrote:

> Hi Sharif,
>
> My comments, inline:
>
> > Next, I would like to following additional requirements in the CT
> > requirements draft.
>
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be
> > scalable to millions of hosts".
>
> This is 'motherhood & apple pie' text (i.e. - noone would really
> disagree). I don't know how this adds anything to the text.
> Additionally, I would suggest SHOULD rather than MUST is
> what you mean.
>
> > 4.17 "The context transfer protocol MUST minimize the number of
> > signaling messages at the sending and receiving Access Routers".
>
> I don't see the need for this.  I don't think this should be
> a requirement.
>
> > 4.18 "The context transfer protocol MUST support both centralized
> > and distributed location of context information."
>
> I don't think that there is any concensus for this kind of
> requirement to be added.
>
> > 5.6.1 "The context transfer protocol MUST include methods for
> > interworking with any IETF IP handover solutions".
> >
> > 5.6.2 "The context transfer solution MAY include methods for
> > interworking with non-IETF handover solutions".
> >
> > 5.1.6 "The context transfer protocol MUST provide mechanisms for
> > sharing contexts or sub-divisions thereof".
>
> I don't agree that the last 3 should be added.
>
> John

--
Behcet



From owner-seamoby@diameter.org  Tue Nov 13 10:36:02 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00153
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 10:36:01 -0500 (EST)
Received: (qmail 5752 invoked by alias); 13 Nov 2001 16:22:46 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 5746 invoked by uid 200); 13 Nov 2001 16:22:46 -0000
Received: (qmail 5741 invoked from network); 13 Nov 2001 16:22:44 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 16:22:44 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095BH8>; Tue, 13 Nov 2001 10:33:19 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F996@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 10:33:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hello John,


> 4.17 "The context transfer protocol MUST minimize the number of 
> signaling messages at the sending and receiving Access Routers".

I don't see the need for this.  I don't think this should be
a requirement.

Minimizing signaling messages have several benefits (a) reduces load on the
networks, (b) improves the effective utilization by ensuring that the
traffic is not dominated by signaling messages, (c) improves reliability,
(d) improves scalability.

> 4.18 "The context transfer protocol MUST support both centralized 
> and distributed location of context information."

I don't think that there is any concensus for this kind of 
requirement to be added.

Would you prefer it if it were re-worded as follows:

4.18 "The context transfer protocol SHOULD support centralized and
distributed storage of context information, if the network provides for it".

[Some current context directories e.g. PDP context has a centralized
directory structure within a system, other networks have a distributed
storage structure. Now, consider inter-system handoff from one network that
has a "centralized" directory to another network which supports a
"distributed" directory. If we want to use the same context transfer
protocol in this situation, it should work for both centralized and
distributed directory architectures. Do you not agree?]



> 5.6.1 "The context transfer protocol MUST include methods for 
> interworking with any IETF IP handover solutions".
>
> 5.6.2 "The context transfer solution MAY include methods for 
> interworking with non-IETF handover solutions".
>
> 5.1.6 "The context transfer protocol MUST provide mechanisms for 
* sharing contexts or sub-divisions thereof".

In some cases a feature context may be shared by two or more mobiles. Now,
it is possible to duplicate this feature context into individual context
areas for each mobile. No problem, If there are only a few feature context
being shared.

But what if there are large numbers of feature contexts being shared? Large
numbers of duplications would lead to a lot of excess directory space being
used up. This is not efficient.

Thus "sharing" feature context would require only one copy of it, and would
save a lot of space - hence the requirement.

I hope you agree.

I don't agree that the last 3 should be added.

Can you provide us a good reason why this should be the case. 

The current requirement draft clearly states in 4.14 and 4.15 that the CT
protocol MUST/SHOULD interwork with IETF/non IETF mobility solutions. Given
that the IETF has a number of mobility protocols, I think this is a
necessary requirement.

The IETF also has several handover solutions in the works, and thus to be
perfectly consistent with the aforementioned mobility requirements, we need
to  add these requirements as well for handover.

And there are also plenty on non IETF handover proposals, interworking
between UMTS and 802.11; UMTS and HYPERLAN1/2; between large scale 802.11
LANs and more. These are currently quite active areas, and any context
transfer solution that we standardize in the IP-layer, SHOULD be able to
interwork with these systems as well.

-Sharif.


From owner-seamoby@diameter.org  Tue Nov 13 11:01:20 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01301
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:01:19 -0500 (EST)
Received: (qmail 6319 invoked by alias); 13 Nov 2001 16:39:22 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 6313 invoked by uid 200); 13 Nov 2001 16:39:21 -0000
Received: (qmail 6308 invoked from network); 13 Nov 2001 16:39:20 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 16:39:20 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADFoIS21115
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 10:50:18 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Tue, 13 Nov 2001 10:49:40 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W3291Q3T>; Tue, 13 Nov 2001 10:48:50 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4638@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 10:48:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C5A.AE4071C0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C5A.AE4071C0
Content-Type: text/plain;
	charset="iso-8859-1"

James:

  I can include both sentences: the first is fine for re-wording of the
existing requirement. However, the second is actually a new, separate
requirement, and should
be included as such. There are lots of reasons for trying to keep
requirements separated,
the best one being that each can be debated separately on it's own merits.

Gary

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: November 12, 2001 20:17
> To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.; seamoby
> Cc: Shahrier, Sharif M.
> Subject: Re: [seamoby] Some proposed changes to the 
> requirements draft.
> 
> 
> Gary,
> 
> > The wording may need to be fixed, but the requirement is not as you
> > are both interpreting it. The "standard representation"
> > referred to is the representation of the data chunks, or objects,
> > in the context transfer protocol that are used to contain 
> the context.
> > The actual context is encapsulated within these data chunks, and the
> > representation of that context is opaque to context 
> transfer. What is
> > needed is a standard representation for these containers.
> >
> > The words do say "a standard representation for *conveying*"; the
> > key words are "for conveying". They do not say "a standard
> representation
> > for the context" which is how you are both interpreting the
> requirement.
> >
> > Again, we can clarify the wording, but the requirement still makes
> sense.
> > As for James proposal, this would be a new requirement.
> >
> 
> I misunderstood the requirement. I think you need to reword 
> it to avoid
> the possibility of misunderstanding. How about:
> 
>     The context transfer protocol MUST define a standardized container
>     format for encapsulating and conveying context information.
> Interpretation
>     of the context information within the container is the 
> domain of the
> application
>     for which context is being transfered. Applications 
> SHOULD define an
> interoperable
>     format for context information if they want to use the context
> transfer protocol.
> 
> Or, you can simply include the first sentence if you feel 
> that the rest
> is too controversial
> or would expand the requirement beyond what is currently agreed.
> 
>             jak
> 
> 

------_=_NextPart_001_01C16C5A.AE4071C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>James:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; I can include both sentences: the first is =
fine for re-wording of the existing requirement. However, the second is =
actually a new, separate requirement, and should</FONT></P>

<P><FONT SIZE=3D2>be included as such. There are lots of reasons for =
trying to keep requirements separated,</FONT>
<BR><FONT SIZE=3D2>the best one being that each can be debated =
separately on it's own merits.</FONT>
</P>

<P><FONT SIZE=3D2>Gary</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: James Kempf [<A =
HREF=3D"mailto:kempf@docomolabs-usa.com">mailto:kempf@docomolabs-usa.com=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: November 12, 2001 20:17</FONT>
<BR><FONT SIZE=3D2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, =
Sharif M.; seamoby</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Shahrier, Sharif M.</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [seamoby] Some proposed changes to =
the </FONT>
<BR><FONT SIZE=3D2>&gt; requirements draft.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gary,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The wording may need to be fixed, but the =
requirement is not as you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; are both interpreting it. The =
&quot;standard representation&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; referred to is the representation of the =
data chunks, or objects,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in the context transfer protocol that are =
used to contain </FONT>
<BR><FONT SIZE=3D2>&gt; the context.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The actual context is encapsulated within =
these data chunks, and the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; representation of that context is opaque =
to context </FONT>
<BR><FONT SIZE=3D2>&gt; transfer. What is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; needed is a standard representation for =
these containers.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The words do say &quot;a standard =
representation for *conveying*&quot;; the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; key words are &quot;for conveying&quot;. =
They do not say &quot;a standard</FONT>
<BR><FONT SIZE=3D2>&gt; representation</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; for the context&quot; which is how you are =
both interpreting the</FONT>
<BR><FONT SIZE=3D2>&gt; requirement.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Again, we can clarify the wording, but the =
requirement still makes</FONT>
<BR><FONT SIZE=3D2>&gt; sense.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As for James proposal, this would be a new =
requirement.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I misunderstood the requirement. I think you =
need to reword </FONT>
<BR><FONT SIZE=3D2>&gt; it to avoid</FONT>
<BR><FONT SIZE=3D2>&gt; the possibility of misunderstanding. How =
about:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; The context transfer =
protocol MUST define a standardized container</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; format for =
encapsulating and conveying context information.</FONT>
<BR><FONT SIZE=3D2>&gt; Interpretation</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; of the context =
information within the container is the </FONT>
<BR><FONT SIZE=3D2>&gt; domain of the</FONT>
<BR><FONT SIZE=3D2>&gt; application</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; for which context is =
being transfered. Applications </FONT>
<BR><FONT SIZE=3D2>&gt; SHOULD define an</FONT>
<BR><FONT SIZE=3D2>&gt; interoperable</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; format for context =
information if they want to use the context</FONT>
<BR><FONT SIZE=3D2>&gt; transfer protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Or, you can simply include the first sentence =
if you feel </FONT>
<BR><FONT SIZE=3D2>&gt; that the rest</FONT>
<BR><FONT SIZE=3D2>&gt; is too controversial</FONT>
<BR><FONT SIZE=3D2>&gt; or would expand the requirement beyond what is =
currently agreed.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16C5A.AE4071C0--


From owner-seamoby@diameter.org  Tue Nov 13 11:07:02 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01672
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:06:59 -0500 (EST)
Received: (qmail 6908 invoked by alias); 13 Nov 2001 16:52:58 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 6902 invoked by uid 200); 13 Nov 2001 16:52:58 -0000
Received: (qmail 6896 invoked from network); 13 Nov 2001 16:52:56 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 16:52:56 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADG3nS23318
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 11:03:49 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Tue, 13 Nov 2001 11:04:16 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W3291RAJ>; Tue, 13 Nov 2001 11:03:27 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4639@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Sharif.Shahrier@InterDigital.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 11:03:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C5C.B8EB6470"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C5C.B8EB6470
Content-Type: text/plain;
	charset="iso-8859-1"

John:

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: November 13, 2001 04:58
> To: Sharif.Shahrier@InterDigital.com; seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the 
> requirements draft.
> 
> 
> Hi Sharif,
> 
> My comments, inline:
> 
> > Next, I would like to following additional requirements in the CT 
> > requirements draft.
> 
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> > scalable to millions of hosts".
> 
> This is 'motherhood & apple pie' text (i.e. - noone would really
> disagree). I don't know how this adds anything to the text.  
> Additionally, I would suggest SHOULD rather than MUST is
> what you mean.
> 

I wasn't going to comment, but your observation needs some clarification.
While scaleability is important, there are definitely different domains of
"scaleability". ARP for example, scales within a subnetwork, and not to the 
global internet. Myself, I do not know what "scaleable to millions of hosts"
really means. If the concern is in regards to the ability for the context
transfer solution to support a real wireless mobile network and one of the
constraining factors is the number of ct's that can be handled per time
period,
then both the number of terminals *and* the number of handoffs per time
period
are at issue (is trivial to say that any ct solution can handle an infinite
number
of terminals if the handoff rate is zero). The number of ARs are also
important,
for, again, ct is only required if there are more then one ARs.

 It is not clear to me how we would define the scaleability of ct in any
real
terms. We know that it must be applicable to within an administrative
domain,
and thus, the top limit would be the IP address space, but that is a
greatest
upper bound and not very useful. Usually, in these situations, people resort
to rate of complexity measures to define scaleability.

 Finally, scaleability is desireable, as long as the requirement is for
scaleability
at an acceptable cost. 

 Other then this, I do not know how one would word a requirement around
scaleability
other then the motherhood of "ct must be scaleable at an acceptable cost".

gary
 
*snip*

> 
> John
> 

------_=_NextPart_001_01C16C5C.B8EB6470
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>John:</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: john.loughney@nokia.com [<A HREF="mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: November 13, 2001 04:58</FONT>
<BR><FONT SIZE=2>&gt; To: Sharif.Shahrier@InterDigital.com; seamoby@cdma-2000.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] Some proposed changes to the </FONT>
<BR><FONT SIZE=2>&gt; requirements draft.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hi Sharif,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; My comments, inline:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Next, I would like to following additional requirements in the CT </FONT>
<BR><FONT SIZE=2>&gt; &gt; requirements draft.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; 4.16 &quot;The context transfer protocol MUST be scalable. It MUST be </FONT>
<BR><FONT SIZE=2>&gt; &gt; scalable to millions of hosts&quot;.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; This is 'motherhood &amp; apple pie' text (i.e. - noone would really</FONT>
<BR><FONT SIZE=2>&gt; disagree). I don't know how this adds anything to the text.&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; Additionally, I would suggest SHOULD rather than MUST is</FONT>
<BR><FONT SIZE=2>&gt; what you mean.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

<P><FONT SIZE=2>I wasn't going to comment, but your observation needs some clarification.</FONT>
<BR><FONT SIZE=2>While scaleability is important, there are definitely different domains of</FONT>
<BR><FONT SIZE=2>&quot;scaleability&quot;. ARP for example, scales within a subnetwork, and not to the </FONT>
<BR><FONT SIZE=2>global internet. Myself, I do not know what &quot;scaleable to millions of hosts&quot;</FONT>
<BR><FONT SIZE=2>really means. If the concern is in regards to the ability for the context</FONT>
<BR><FONT SIZE=2>transfer solution to support a real wireless mobile network and one of the</FONT>
<BR><FONT SIZE=2>constraining factors is the number of ct's that can be handled per time period,</FONT>
<BR><FONT SIZE=2>then both the number of terminals *and* the number of handoffs per time period</FONT>
<BR><FONT SIZE=2>are at issue (is trivial to say that any ct solution can handle an infinite number</FONT>
<BR><FONT SIZE=2>of terminals if the handoff rate is zero). The number of ARs are also important,</FONT>
<BR><FONT SIZE=2>for, again, ct is only required if there are more then one ARs.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;It is not clear to me how we would define the scaleability of ct in any real</FONT>
<BR><FONT SIZE=2>terms. We know that it must be applicable to within an administrative domain,</FONT>
<BR><FONT SIZE=2>and thus, the top limit would be the IP address space, but that is a greatest</FONT>
<BR><FONT SIZE=2>upper bound and not very useful. Usually, in these situations, people resort</FONT>
<BR><FONT SIZE=2>to rate of complexity measures to define scaleability.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;Finally, scaleability is desireable, as long as the requirement is for scaleability</FONT>
<BR><FONT SIZE=2>at an acceptable cost. </FONT>
</P>

<P><FONT SIZE=2>&nbsp;Other then this, I do not know how one would word a requirement around scaleability</FONT>
<BR><FONT SIZE=2>other then the motherhood of &quot;ct must be scaleable at an acceptable cost&quot;.</FONT>
</P>

<P><FONT SIZE=2>gary</FONT>
<BR><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>*snip*</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; John</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16C5C.B8EB6470--


From owner-seamoby@diameter.org  Tue Nov 13 11:13:49 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01999
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:13:43 -0500 (EST)
Received: (qmail 7340 invoked by alias); 13 Nov 2001 16:57:04 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 7334 invoked by uid 200); 13 Nov 2001 16:57:03 -0000
Received: (qmail 7323 invoked from network); 13 Nov 2001 16:57:00 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 16:57:00 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADG7uS23941
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 11:07:56 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Tue, 13 Nov 2001 11:07:33 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W3291RDY>; Tue, 13 Nov 2001 11:06:44 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA463B@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 11:06:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C5D.2F39A5B0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C5D.2F39A5B0
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C5D.2F39A5B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16C29.76A57B60" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>P.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN-LEFT: 0in; =
MARGIN-RIGHT: 0in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle20 {
	COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle21 {
	COLOR: #993366; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US link=3Dblue style=3D"tab-interval: .5in" =
vLink=3Dblue>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760040916-12112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760040916-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760040916-12112001>&nbsp;=20
This requirement is for the ARs to authenticate each other so that a ct =
exchange=20
can</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D760040916-12112001>be=20
trusted. It has nothing to do with the MN and handoff per=20
se.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760040916-12112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D760040916-12112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif =
M.=20
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November =
13, 2001=20
  09:51<BR><B>To:</B> Shahrier, Sharif M.<BR><B>Cc:</B>=20
  'seamoby@cdma-2000.org'<BR><B>Subject:</B> RE: [seamoby] Some =
proposed changes=20
  to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT color=3D#993366 face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: #993366; FONT-SIZE: 12pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT=20
  color=3D#993366><SPAN=20
  style=3D"COLOR: #993366; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3D#993366 face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: #993366; FONT-SIZE: 12pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT=20
  color=3D#993366><SPAN=20
  style=3D"COLOR: #993366; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3D#993366 face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: #993366; FONT-SIZE: 12pt">I have some issues with the =
following=20
  requirement in the CT draft.</SPAN></FONT><FONT color=3D#993366><SPAN =

  style=3D"COLOR: #993366; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">4.9=20
  The entities transferring context MUST have completed a mutual =
authentication=20
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>initiating the=20
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">I=20
  don&#8217;t support this =
requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">It=20
  appears to me this may not fit the case for =
&#8220;break-before-make&#8221; handover .=20
  <SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>For instance, the =
mobile may=20
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">AP,=20
  and re-establish connection with the new AP.=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">Assuming=20
  that the context is transferred prior to re-establishing the new=20
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">The=20
  mobile will need to re-authenticate after it makes a new connection =
at its new=20
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">I have=20
  seen several practical cases that supports this scanario, thus I feel =
it is=20
  necessary for authentication after the transfer of context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">in=20
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle21><FONT color=3D#993366 =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></BLOCKQUOTE><=
/BODY></HTML>

------_=_NextPart_001_01C16C5D.2F39A5B0--


From owner-seamoby@diameter.org  Tue Nov 13 11:34:42 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03325
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:34:31 -0500 (EST)
Received: (qmail 8117 invoked by alias); 13 Nov 2001 17:18:30 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8111 invoked by uid 200); 13 Nov 2001 17:18:30 -0000
Received: (qmail 8106 invoked from network); 13 Nov 2001 17:18:28 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 17:18:28 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095BPX>; Tue, 13 Nov 2001 11:28:59 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F997@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 11:28:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C60.4B1370B0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C60.4B1370B0
Content-Type: text/plain;
	charset="iso-8859-1"

Gary,
> 
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> > scalable to millions of hosts". 
> 
> This is 'motherhood & apple pie' text (i.e. - noone would really 
> disagree). I don't know how this adds anything to the text.  
> Additionally, I would suggest SHOULD rather than MUST is 
> what you mean. 
> 
Myself, I do not know what "scaleable to millions of hosts" 
really means. If the concern is in regards to the ability for the context 
transfer solution to support a real wireless mobile network and one of the 
constraining factors is the number of ct's that can be handled per time
period, 
then both the number of terminals *and* the number of handoffs per time
period 
are at issue (is trivial to say that any ct solution can handle an infinite
number 
of terminals if the handoff rate is zero
I agree with this. Number of ct's handled per time period and the number of
handoffs per time
Period are both good cases to support the scalability requirement. The other
point is the quantity of context information
Being transferred for each mobile over a given time. This bandwidth must be
scalable.
 It is not clear to me how we would define the scaleability of ct in any
real 
terms. We know that it must be applicable to within an administrative
domain, 
and thus, the top limit would be the IP address space, but that is a
greatest 
upper bound and not very useful. Usually, in these situations, people resort

to rate of complexity measures to define scaleability. 
I agree that the scalability of the CT must be applicabile within an
administrative domain; scalability must also
Be applicable across different operator networks as well.
I don't see how the IPv4 address space affects the scalability of CT. Could
you please explain?
 Finally, scaleability is desireable, as long as the requirement is for
scaleability 
at an acceptable cost. 
 Other then this, I do not know how one would word a requirement around
scaleability 
other then the motherhood of "ct must be scaleable at an acceptable cost". 
I agree. Perhaps something like:
4.16 The context transfer protocol MUST be scalable at an acceptable cost.
        The context transfer protocol MUST be ale to handle a large number
of  of context transfers per second, and MUST
        Be able to support a large number of handoffs per second. The
quantity of context information being transferred for each 
        Mobile per second MUST be scalable, i.e. the bandwidth of the
context transfer MUST be scalable.
        The context transfers MAY be within the same administrative domain,
or they MAY be across different 
         administrative domains. 

------_=_NextPart_001_01C16C60.4B1370B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C37.27CD6DA0">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p><b style=3D'mso-bidi-font-weight:normal'><font size=3D3 color=3Dnavy
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;
color:navy;font-weight:bold'>Gary,</span></font></b><b =
style=3D'mso-bidi-font-weight:
normal'><font color=3Dnavy><span =
style=3D'mso-bidi-font-size:10.0pt;color:navy;
mso-color-alt:windowtext;font-weight:bold'><o:p></o:p></span></font></b>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; &gt; 4.16 &quot;The context transfer protocol MUST be
scalable. It MUST be </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; &gt; scalable to millions of =
hosts&quot;.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; This is 'motherhood &amp; apple pie' text (i.e. - =
noone would
really</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; disagree). I don't know how this adds anything to the
text.&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Additionally, I would suggest SHOULD rather than MUST =
is</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; what you mean.</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>Myself, I do not know what &quot;scaleable to millions of
hosts&quot;</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>really means. If the concern is in regards to the ability =
for the
context</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>transfer solution to support a real wireless mobile =
network and
one of the</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>constraining factors is the number of ct's that can be =
handled per
time period,</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>then both the number of terminals *and* the number of =
handoffs per
time period</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>are at issue (is trivial to say that any ct solution can =
handle an
infinite number</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>of terminals if the handoff rate is =
zero</span></font><font
size=3D2 color=3Dnavy><span =
style=3D'font-size:10.0pt;color:navy;mso-color-alt:windowtext'><o:p></o:=
p></span></font></p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 agree
with this. Number of ct&#8217;s handled per time period and the number =
of handoffs
per time<o:p></o:p></span></font></span></p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>P=
eriod are
both good cases to support the scalability requirement. The other point =
is the quantity
of context information<o:p></o:p></span></font></span></p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>B=
eing transferred
for each mobile over a given time. This bandwidth must be =
scalable.<o:p></o:p></span></font></span></p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;It is not clear to me how we would define the =
scaleability
of ct in any real</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>terms. We know that it must be applicable to within an =
administrative
domain,</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>and thus, the top limit would be the IP address space, but =
that is
a greatest</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>upper bound and not very useful. Usually, in these =
situations,
people resort</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>to rate of complexity measures to define =
scaleability.</span></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 agree
that the scalability of the CT must be applicabile within an =
administrative domain;
scalability must also<o:p></o:p></span></font></span></p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>B=
e applicable
across different operator networks as =
well.<o:p></o:p></span></font></span></p>

<p><span class=3DEmailStyle19><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 don&#8217;t
see how the IPv4 address space affects the scalability of CT. Could you =
please
explain?<o:p></o:p></span></font></span></p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;Finally, scaleability is desireable, as long as the
requirement is for scaleability</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>at an acceptable cost. </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;Other then this, I do not know how one would word a
requirement around scaleability</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>other then the motherhood of &quot;ct must be scaleable at =
an
acceptable cost&quot;.</span></font><font color=3Dblack><span =
style=3D'color:black'>
</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'>I agree. Perhaps something like:</span></font><font =
color=3Dnavy><span
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'>4.16 The context transfer protocol MUST be scalable at an
acceptable cost.</span></font><font color=3Dnavy><span =
style=3D'color:navy;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'><span style=3D"mso-spacerun:
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>The context =
transfer
protocol MUST be ale to handle a large number of <span =
style=3D"mso-spacerun:
yes">&nbsp;</span>of context transfers per second, and =
MUST</span></font><font
color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'><span style=3D"mso-spacerun:
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Be able to =
support a
large number of handoffs per second. The quantity of context =
information being
transferred for each </span></font><font color=3Dnavy><span =
style=3D'color:navy;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'><span style=3D"mso-spacerun:
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Mobile per =
second MUST
be scalable, i.e. the bandwidth of the context transfer MUST be =
scalable.</span></font><font
color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'><span style=3D"mso-spacerun:
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>The context =
transfers MAY
be within the same administrative domain, or they MAY be across =
different </span></font><font
color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p><font size=3D3 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:navy'><span style=3D"mso-spacerun:
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>administrative
domains.</span></font><font color=3Dblack><span style=3D'color:black'> =
</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

</div>

</body>

</html>

------_=_NextPart_001_01C16C60.4B1370B0--


From owner-seamoby@diameter.org  Tue Nov 13 11:42:10 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03913
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:42:10 -0500 (EST)
Received: (qmail 8450 invoked by alias); 13 Nov 2001 17:24:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8444 invoked by uid 200); 13 Nov 2001 17:24:25 -0000
Received: (qmail 8433 invoked from network); 13 Nov 2001 17:24:18 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 17:24:18 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fADGZk504010;
	Tue, 13 Nov 2001 08:35:46 -0800 (PST)
Message-ID: <003401c16c61$05557a40$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <john.loughney@nokia.com>, <Sharif.Shahrier@InterDigital.com>,
        <seamoby@cdma-2000.org>
References: <0C1353ABB1DEB74DB067ADFF749C4EEF5D901D@esebe004.NOE.Nokia.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 08:34:09 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

I agree. I do not understand what the distinction is here. Context
transfer is an optimization and as such it involves
two parties and a fairly limited time interval over which the
information is valid. Trying to expand it into more risks "boiling the
ocean".

        jak

----- Original Message -----
From: <john.loughney@nokia.com>
To: <Sharif.Shahrier@InterDigital.com>; <kempf@docomolabs-usa.com>;
<seamoby@cdma-2000.org>
Sent: Monday, November 12, 2001 11:23 PM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Hi Sharif,
>
> > 4.18 "The context transfer protocol MUST support both centralized
and
> > distributed location of context information."
> >
> > This requirement should be there so that there can be a
> > "local" context
> > database (LCD)  within each AR. The LCD keeps a log of the context
> > parameters of every session that is currently active for the MN.
>
> I don't support this requirement.  This is getting very
> close to an implementational issue, not a general requirement.
>
> It sounds like you want a Context Transfer proxy or something
> along those lines.  I don't see anything explicitly requiring
> this.
>
> John
>



From owner-seamoby@diameter.org  Tue Nov 13 11:45:41 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04079
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:45:40 -0500 (EST)
Received: (qmail 8694 invoked by alias); 13 Nov 2001 17:29:00 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8688 invoked by uid 200); 13 Nov 2001 17:28:59 -0000
Received: (qmail 8679 invoked from network); 13 Nov 2001 17:28:57 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 17:28:57 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fADGeS504174;
	Tue, 13 Nov 2001 08:40:28 -0800 (PST)
Message-ID: <004d01c16c61$ada00ee0$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F995@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 08:38:52 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

How about:

    A mutual trust relationship MUST exist between the entities
performing context transfer prior to the actual context
   being transferred. The relationship MAY require an authentication
exchange between the two parties at some point
   prior to the context transfer, or it MAY derive transitively from an
exchange through a third party which both
   entities trust.

                    jak


----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: <seamoby@cdma-2000.org>
Sent: Tuesday, November 13, 2001 6:50 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


>
>
> I have some issues with the following requirement in the CT draft.
>
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>
> I don't support this requirement.
>
> It appears to me this may not fit the case for "break-before-make"
handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP.
>
> Assuming that the context is transferred prior to re-establishing the
new
> connection.
>
> The mobile will need to re-authenticate after it makes a new
connection at
> its new AP.
>
> I have seen several practical cases that supports this scanario, thus
I feel
> it is necessary for authentication after the transfer of context
> in "break-before-make".
>
> -Sharif.
>



From owner-seamoby@diameter.org  Tue Nov 13 11:52:57 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04654
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 11:52:46 -0500 (EST)
Received: (qmail 9427 invoked by alias); 13 Nov 2001 17:33:26 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9420 invoked by uid 200); 13 Nov 2001 17:33:26 -0000
Received: (qmail 9406 invoked from network); 13 Nov 2001 17:33:23 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 17:33:23 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095BRM>; Tue, 13 Nov 2001 11:43:58 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F998@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 11:43:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C62.638219B0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C62.638219B0
Content-Type: text/plain;
	charset="iso-8859-1"

Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C62.638219B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C39.4040D190">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>Gary,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Understood.
However, the requirements contains nothing (?) about the mobile =
authenticating
with its context, after the context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'>Has been transferred. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'>I think a requirement should be =
there
for this, otherwise, without authentication, the MN can &#8220;get =
at&#8221; any context,
or context feature that its not authorized access =
to.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'>How =
about:<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><b><span
style=3D'font-weight:bold'>There MUST be mutual authentication between =
the MN and
its context, after the context transfer has =
occurred.<o:p></o:p></span></b></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><b><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman";font-weight:bold'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></b></span>=
</p>

<p class=3DMsoNormal><span class=3DEmailStyle22><b><font size=3D2 =
color=3D"#003300"
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman";font-weight:bold'>-Sharif.<o:p></o:p></span></font></b></span></p=
>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#003300"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gary Kenward
[mailto:gkenward@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
11:07 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Sharif:</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp; This requirement is for the =
ARs to
authenticate each other so that a ct exchange can</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>be trusted. It has nothing to do =
with the
MN and handoff per se.</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Gary</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:3.75pt;border:none;mso-border-left-alt:solid blue =
1.5pt;padding:
0in;mso-padding-alt:0in 0in 0in 4.0pt'><font size=3D2 color=3Dblack =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> November 13, 2001 =
09:51<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahrier, Sharif =
M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'><![if !supportEmptyParas]>&nbsp;<=
![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3D"#993366" face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:#993366'>I have some issues with the following requirement in the =
CT
draft.</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>4=
.9 The
entities transferring context MUST have completed a mutual =
authentication
process prior to<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>initiating the
transfer.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 don&#8217;t
support this requirement.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
t appears
to me this may not fit the case for &#8220;break-before-make&#8221; =
handover .<span
style=3D"mso-spacerun: yes">&nbsp; </span>For instance, the mobile may =
break
connection with the old<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
P, and
re-establish connection with the new AP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
ssuming
that the context is transferred prior to re-establishing the new =
connection.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
he mobile
will need to re-authenticate after it makes a new connection at its new =
AP.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 have
seen several practical cases that supports this scanario, thus I feel =
it is
necessary for authentication after the transfer of context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>i=
n
&#8220;break-before-make&#8221;.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C16C62.638219B0--


From owner-seamoby@diameter.org  Tue Nov 13 16:00:10 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16603
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 15:59:46 -0500 (EST)
Received: (qmail 11238 invoked by alias); 13 Nov 2001 21:39:59 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11232 invoked by uid 200); 13 Nov 2001 21:39:59 -0000
Received: (qmail 11227 invoked from network); 13 Nov 2001 21:39:57 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 21:39:57 -0000
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id NAA11784 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 13:50:43 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id NAA16692 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 13:50:36 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNGT5S1>; Tue, 13 Nov 2001 14:50:36 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB15@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 14:50:33 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C84.D6D2B2E0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C84.D6D2B2E0
Content-Type: text/plain;
	charset="iso-8859-1"

I don't understand what authentication between MN and its context supposed
to mean?
context is just a piece of data that exists in a protocol unit and is being
transferred
(please look at the problem statement).
 
How can MN authenticate with a piece of data??????????????
 
And why does the authentication has to happen after context transfer, could
you define
context transfer here?
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C84.D6D2B2E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16C39.4040D190" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle20 {
	COLOR: navy; mso-ascii-font-family: Arial; mso-hansi-font-family: =
Arial; mso-bidi-font-family: Arial; mso-style-type: personal; =
mso-ansi-font-size: 10.0pt
}
SPAN.EmailStyle21 {
	COLOR: #993366; mso-ascii-font-family: Arial; mso-hansi-font-family: =
Arial; mso-bidi-font-family: Arial; mso-style-type: personal; =
mso-ansi-font-size: 10.0pt
}
SPAN.EmailStyle22 {
	COLOR: #003300; mso-ascii-font-family: Arial; mso-hansi-font-family: =
Arial; mso-bidi-font-family: Arial; mso-style-type: personal-reply; =
mso-ansi-font-size: 10.0pt
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue =
link=3Dblue>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
don't understand what authentication between MN and its context =
supposed to=20
mean?</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>context is just a piece of data that exists in a protocol unit =
and is=20
being transferred</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>(please look at the problem statement).</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>How=20
can MN authenticate with a piece of =
data??????????????</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>And=20
why does the authentication has to happen after context transfer, could =
you=20
define</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>context transfer here?</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>Maybe=20
you mean that the MN should authenticate the received context data,=20
but</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>then=20
why does the MN should do this. The context is going to the new AR,=20
anyway.</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
authentication of data is needed, new AR does it on behalf of=20
MN.</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>Why=20
are we dragging MN into the authentication process.</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff size=3D2>these=20
issues are attacking the basic framework of CT, =
IMHO</FONT></SPAN></DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D457164620-13112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Madjid</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif =
M.=20
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> Tuesday, =
November=20
  13, 2001 10:44 AM<BR><B>To:</B> 'Gary Kenward'; Shahrier, Sharif=20
  M.<BR><B>Cc:</B> seamoby@cdma-2000.org<BR><B>Subject:</B> RE: =
[seamoby] Some=20
  proposed changes to the requirements draft.<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Understood. However, the requirements contains nothing (?) =
about the=20
  mobile authenticating with its context, after the context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">Has=20
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">I=20
  think a requirement should be there for this, otherwise, without=20
  authentication, the MN can &#8220;get at&#8221; any context, or =
context feature that its=20
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">How=20
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3D"Times =
New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><B><SPAN style=3D"FONT-WEIGHT: bold">There MUST be mutual =
authentication=20
  between the MN and its context, after the context transfer has=20
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><B><FONT =
face=3D"Times New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><B><FONT =
face=3D"Times New Roman"=20
  color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle22><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><FONT face=3DTahoma color=3Dblack size=3D2><SPAN =

  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Gary=20
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 11:07=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, =
Sharif=20
  M.'<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
  'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sharif:</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp; =
This=20
  requirement is for the ARs to authenticate each other so that a ct =
exchange=20
  can</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">be =
trusted. It has=20
  nothing to do with the MN and handoff per se.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Gary</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; MARGIN-BOTTOM: 12pt; PADDING-BOTTOM: =
0in; MARGIN-LEFT: 3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none; mso-margin-top-alt: auto; =
mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in =
4.0pt"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 =
09:51<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif =
M.<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3D#993366 size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: #993366">I have some issues with the =
following=20
  requirement in the CT draft.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">4.9=20
  The entities transferring context MUST have completed a mutual =
authentication=20
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>initiating the=20
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
  don&#8217;t support this =
requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">It=20
  appears to me this may not fit the case for =
&#8220;break-before-make&#8221; handover=20
  .<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For instance, the =
mobile may=20
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">AP,=20
  and re-establish connection with the new AP.=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Assuming=20
  that the context is transferred prior to re-establishing the new=20
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">The=20
  mobile will need to re-authenticate after it makes a new connection =
at its new=20
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I have=20
  seen several practical cases that supports this scanario, thus I feel =
it is=20
  necessary for authentication after the transfer of context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">in=20
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
3.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQ=
UOTE></BODY></HTML>

------_=_NextPart_001_01C16C84.D6D2B2E0--


From owner-seamoby@diameter.org  Tue Nov 13 16:12:47 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA16985
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:12:46 -0500 (EST)
Received: (qmail 11394 invoked by alias); 13 Nov 2001 21:44:48 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11388 invoked by uid 200); 13 Nov 2001 21:44:48 -0000
Received: (qmail 11380 invoked from network); 13 Nov 2001 21:44:45 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 21:44:45 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fADKuG516234
	for <seamoby@diameter.org>; Tue, 13 Nov 2001 12:56:16 -0800 (PST)
Message-ID: <01c701c16c85$69b11e30$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@diameter.org>
Subject: [seamoby] Last Call Closed on draft-ietf-seamoby-context-transfer-problem-statement-03.txt Now Closed
Date: Tue, 13 Nov 2001 12:54:40 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Last Call on
draft-ietf-seamoby-context-transfer-problem-statement-03.txt closed on
Fri. Nov. 2. I will be taking the accumulated comments from the list and
folding them into the draft prior to submission to the IESG.

            jak



From owner-seamoby@diameter.org  Tue Nov 13 16:14:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17050
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:14:26 -0500 (EST)
Received: (qmail 11760 invoked by alias); 13 Nov 2001 21:58:01 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11754 invoked by uid 200); 13 Nov 2001 21:58:01 -0000
Received: (qmail 11674 invoked from network); 13 Nov 2001 21:55:03 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 21:55:03 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fADL6Y516677
	for <seamoby@diameter.org>; Tue, 13 Nov 2001 13:06:34 -0800 (PST)
Message-ID: <01ec01c16c86$d9845370$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@diameter.org>
Subject: [seamoby] Paging Protocol Assesement Complete
Date: Tue, 13 Nov 2001 13:04:57 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The paging protocol assessment team recently completed assessment of the
submitted paging protocols. The assessment has been posted as a draft to
the Internet Drafts directory
(draft-kempf-seamoby-paging-protocol-assessment-00.txt) and should be
available shortly. The assessment is being used by the Working Group
Chairs, our Area Director, and interested IESG members to determine
which protocol draft should become the basis of the Seamoby paging
protocol. The decision will be presented at the Working Group meeting in
Salt Lake City for working group discussion and approval. Meanwhile,
please submit any comments or discussion about the assessment to the
list.

Thanx to the assessment team members for their help in performing the
assessment, and to the protocol development teams for their
contributions.

            jak



From owner-seamoby@diameter.org  Tue Nov 13 16:17:15 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17149
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:17:13 -0500 (EST)
Received: (qmail 12568 invoked by alias); 13 Nov 2001 22:02:23 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 12561 invoked by uid 200); 13 Nov 2001 22:02:23 -0000
Received: (qmail 12540 invoked by uid 500); 13 Nov 2001 22:02:19 -0000
Date: Tue, 13 Nov 2001 14:02:19 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>, seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011113140219.A11802@charizard.diameter.org>
Mail-Followup-To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	'Gary Kenward' <gkenward@nortelnetworks.com>, seamoby@cdma-2000.org
References: <35DBB8B7AC89D4118E98009027B1009B0464FB15@IL27EXM10.cig.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B0464FB15@IL27EXM10.cig.mot.com>; from Madjid.Nakhjiri@motorola.com on Tue, Nov 13, 2001 at 02:50:33PM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

ok, just to put a cap on this one. We are talking about two edge devices exchanging
state in a secure (read: authenticated) manner. We have consensus on this 
requirement, and I don't see the need to re-open this one.

Now let's move on.

PatC
On Tue, Nov 13, 2001 at 02:50:33PM -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> I don't understand what authentication between MN and its context supposed
> to mean?
> context is just a piece of data that exists in a protocol unit and is being
> transferred
> (please look at the problem statement).
>  
> How can MN authenticate with a piece of data??????????????
>  
> And why does the authentication has to happen after context transfer, could
> you define
> context transfer here?
>  
> Maybe you mean that the MN should authenticate the received context data,
> but
> then why does the MN should do this. The context is going to the new AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>  
> Why are we dragging MN into the authentication process.
>  
> these issues are attacking the basic framework of CT, IMHO
>  
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
> 
> 
> Gary,
>  
>                 Understood. However, the requirements contains nothing (?)
> about the mobile authenticating with its context, after the context 
> Has been transferred. 
>  
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature that its
> not authorized access to.
>  
> How about:
>  
>                 There MUST be mutual authentication between the MN and its
> context, after the context transfer has occurred.
>  
> -Sharif.
>  
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
>  
> Sharif:
>  
>   This requirement is for the ARs to authenticate each other so that a ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>  
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
>  
>  
> I have some issues with the following requirement in the CT draft.
>  
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>  
> I don't support this requirement.
>  
> It appears to me this may not fit the case for "break-before-make" handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP. 
>  
> Assuming that the context is transferred prior to re-establishing the new
> connection.
>  
> The mobile will need to re-authenticate after it makes a new connection at
> its new AP.
>  
> I have seen several practical cases that supports this scanario, thus I feel
> it is necessary for authentication after the transfer of context 
> in "break-before-make".
>  
> -Sharif.


From owner-seamoby@diameter.org  Tue Nov 13 16:24:54 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17425
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:24:36 -0500 (EST)
Received: (qmail 12958 invoked by alias); 13 Nov 2001 22:04:11 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 12952 invoked by uid 200); 13 Nov 2001 22:04:11 -0000
Received: (qmail 12940 invoked from network); 13 Nov 2001 22:04:08 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:04:08 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADLF0S04215
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 16:15:00 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Tue, 13 Nov 2001 16:15:21 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W329156Z>; Tue, 13 Nov 2001 16:14:30 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA463D@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:14:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C88.2D1ECD70"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C88.2D1ECD70
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 11:29
To: Kenward, Gary [WDLN2:AN10:EXCH]; 'john.loughney@nokia.com'; Shahrier,
Sharif M.; seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
> 
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> > scalable to millions of hosts". 
> 
> This is 'motherhood & apple pie' text (i.e. - noone would really 
> disagree). I don't know how this adds anything to the text.  
> Additionally, I would suggest SHOULD rather than MUST is 
> what you mean. 
> 
Myself, I do not know what "scaleable to millions of hosts" 
really means. If the concern is in regards to the ability for the context 
transfer solution to support a real wireless mobile network and one of the 
constraining factors is the number of ct's that can be handled per time
period, 
then both the number of terminals *and* the number of handoffs per time
period 
are at issue (is trivial to say that any ct solution can handle an infinite
number 
of terminals if the handoff rate is zero
I agree with this. Number of ct's handled per time period and the number of
handoffs per time
Period are both good cases to support the scalability requirement. The other
point is the quantity of context information
Being transferred for each mobile over a given time. This bandwidth must be
scalable.
 It is not clear to me how we would define the scaleability of ct in any
real 
terms. We know that it must be applicable to within an administrative
domain, 
and thus, the top limit would be the IP address space, but that is a
greatest 
upper bound and not very useful. Usually, in these situations, people resort

to rate of complexity measures to define scaleability. 
I agree that the scalability of the CT must be applicabile within an
administrative domain; scalability must also
Be applicable across different operator networks as well.
I don't see how the IPv4 address space affects the scalability of CT. Could
you please explain?
[gwk] I doesn't, other then it puts "a" limit on the possible number of
mobiles within an 
administrative domain. An very high limit. Even higher if the domain uses
IPv6. 
 Finally, scaleability is desireable, as long as the requirement is for
scaleability 
at an acceptable cost. 
 Other then this, I do not know how one would word a requirement around
scaleability 
other then the motherhood of "ct must be scaleable at an acceptable cost". 
I agree. Perhaps something like:
4.16 The context transfer protocol MUST be scalable at an acceptable cost.
        The context transfer protocol MUST be ale to handle a large number
of  of context transfers per second, and MUST
        Be able to support a large number of handoffs per second. The
quantity of context information being transferred for each 
        Mobile per second MUST be scalable, i.e. the bandwidth of the
context transfer MUST be scalable.
        The context transfers MAY be within the same administrative domain,
or they MAY be across different 
         administrative domains. 
[gwk] This is actually 7 requirements. And, there is no way to ensure
conformance to  a number of them
as written. While there are requirements in the existing draft that will be
difficult to ensure conformance, the wg
has made an effort to stay away from requirements which could not be tested
(e.g. there is no "ct must be fast"
requirement). 
My personal opinion is in line with what John stated, that scalability is a
given. Arguably, many stated requirements
are "givens", but are stated for reinforcement. On the other hand, many
givens are not stated as requirements simply to
keep the number of requirements and the scope of the document to a
manageable level. I would put "saleability" in
the latter category, particularly with all the caveats that must go along
with any saleability requirement for ct.
I hope this helps.
Gary

------_=_NextPart_001_01C16C88.2D1ECD70
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16C37.27CD6DA0" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=927120321-13112001>Sharif:</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 13, 2001 
  11:29<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; 
  'john.loughney@nokia.com'; Shahrier, Sharif M.; 
  seamoby@cdma-2000.org<BR><B>Subject:</B> RE: [seamoby] Some proposed changes 
  to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P><B style="mso-bidi-font-weight: normal"><FONT color=navy 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt; FONT-WEIGHT: bold; mso-bidi-font-size: 10.0pt">Gary,</SPAN></FONT></B><B 
  style="mso-bidi-font-weight: normal"><FONT color=navy><SPAN 
  style="COLOR: navy; FONT-WEIGHT: bold; mso-bidi-font-size: 10.0pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></B></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt; </SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; &gt; 4.16 "The context 
  transfer protocol MUST be scalable. It MUST be </SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; &gt; scalable to 
  millions of hosts".</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"> 
  <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt; </SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; This is 'motherhood 
  &amp; apple pie' text (i.e. - noone would really</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; disagree). I don't 
  know how this adds anything to the text.&nbsp; </SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; Additionally, I would 
  suggest SHOULD rather than MUST is</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&gt; what you mean.</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">&gt; </SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">Myself, I do not know what "scaleable to 
  millions of hosts"</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"> 
  <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">really means. If the concern is in 
  regards to the ability for the context</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">transfer solution to support a real 
  wireless mobile network and one of the</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">constraining factors is the number of 
  ct's that can be handled per time period,</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">then both the number of terminals *and* 
  the number of handoffs per time period</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">are at issue (is trivial to say that any 
  ct solution can handle an infinite number</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">of terminals if the handoff rate is 
  zero</SPAN></FONT><FONT color=navy size=2><SPAN 
  style="COLOR: navy; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  agree with this. Number of ct&#8217;s handled per time period and the number of 
  handoffs per time<o:p></o:p></SPAN></FONT></SPAN></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Period 
  are both good cases to support the scalability requirement. The other point is 
  the quantity of context information<o:p></o:p></SPAN></FONT></SPAN></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Being 
  transferred for each mobile over a given time. This bandwidth must be 
  scalable.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&nbsp;It is not clear to me how we would 
  define the scaleability of ct in any real</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR></SPAN></FONT><FONT color=black size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">terms. We know that it must be 
  applicable to within an administrative domain,</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">and thus, the top limit 
  would be the IP address space, but that is a greatest</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">upper bound and not very 
  useful. Usually, in these situations, people resort</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">to rate of complexity 
  measures to define scaleability.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  agree that the scalability of the CT must be applicabile within an 
  administrative domain; scalability must 
  also<o:p></o:p></SPAN></FONT></SPAN></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Be 
  applicable across different operator networks as 
  well.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P><SPAN class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  don&#8217;t see how the IPv4 address space affects the scalability of CT. Could you 
  please explain?<BR><FONT size=3><FONT color=#0000ff><FONT 
  face="Comic Sans MS"><SPAN class=927120321-13112001>[gwk]&nbsp;I doesn't, 
  other then&nbsp;it puts&nbsp;"a" limit on the&nbsp;possible number of mobiles 
  within an&nbsp;</SPAN></FONT></FONT></FONT></SPAN></FONT></SPAN><SPAN 
  class=EmailStyle19><FONT color=navy face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><FONT 
  size=3><FONT color=#0000ff><FONT face="Comic Sans MS"><SPAN 
  class=927120321-13112001><BR>administrative domain. An very high limit. Even 
  higher if the domain uses 
  IPv6.&nbsp;</SPAN><o:p></o:p></FONT></FONT></FONT></SPAN></FONT></SPAN></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&nbsp;Finally, scaleability is 
  desireable, as long as the requirement is for scaleability</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">at an acceptable cost. 
  </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=black face="Times New Roman" size=2><SPAN 
  style="COLOR: black; FONT-SIZE: 10pt">&nbsp;Other then this, I do not know how 
  one would word a requirement around scaleability</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> <BR></SPAN></FONT><FONT color=black 
  size=2><SPAN style="COLOR: black; FONT-SIZE: 10pt">other then the motherhood 
  of "ct must be scaleable at an acceptable cost".</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"> </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt">I agree. Perhaps something 
  like:</SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt">4.16 The context transfer protocol MUST 
  be scalable at an acceptable cost.</SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>The context transfer protocol MUST be ale to handle a large number of 
  <SPAN style="mso-spacerun: yes">&nbsp;</SPAN>of context transfers per second, 
  and MUST</SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>Be 
  able to support a large number of handoffs per second. The quantity of context 
  information being transferred for each </SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Mobile per second MUST be scalable, i.e. the bandwidth of the context 
  transfer MUST be scalable.</SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>The context transfers MAY be within the same administrative domain, or 
  they MAY be across different </SPAN></FONT><FONT color=navy><SPAN 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P><FONT color=navy face="Times New Roman"><SPAN 
  style="COLOR: navy; FONT-SIZE: 12pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>administrative domains.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"> <BR><FONT color=#0000ff face="Comic Sans MS"><SPAN 
  class=927120321-13112001>[gwk]&nbsp;This is actually&nbsp;7 
  requirements.&nbsp;And, there is no way to ensure conformance to&nbsp; a 
  number of them</SPAN></FONT></SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"><FONT color=#0000ff face="Comic Sans MS"><SPAN 
  class=927120321-13112001><BR>as written. </SPAN></FONT></SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><FONT color=#0000ff 
  face="Comic Sans MS"><SPAN class=927120321-13112001>While&nbsp;there are 
  requirements in the&nbsp;existing draft that will be difficult to ensure 
  conformance,&nbsp;</SPAN></FONT></SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"><FONT color=#0000ff face="Comic Sans MS"><SPAN 
  class=927120321-13112001>the wg</SPAN></FONT></SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black"><FONT color=#0000ff 
  face="Comic Sans MS"><SPAN class=927120321-13112001><BR>has made an effort to 
  stay away from requirements which could not be tested (e.g. there is no "ct 
  must be fast"</SPAN></FONT></SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black"><FONT color=#0000ff face="Comic Sans MS"><SPAN 
  class=927120321-13112001><BR>requirement).&nbsp;</SPAN></FONT></SPAN></FONT></P>
  <P><FONT color=#0000ff face="Comic Sans MS"><SPAN class=927120321-13112001>My 
  personal opinion is in line with what John stated, that scalability is a 
  given. Arguably, many stated requirements<BR>are "givens", but are stated for 
  reinforcement. On the other hand, many givens are not stated as requirements 
  simply to<BR>keep the number of requirements and the scope of the document to 
  a manageable level. I would put "saleability" in<BR>the latter category, 
  particularly with all the caveats that must go along with any saleability 
  requirement for ct.</SPAN></FONT></P>
  <P><FONT color=black><SPAN style="COLOR: black"><FONT color=#0000ff 
  face="Comic Sans MS"><SPAN class=927120321-13112001>I hope this 
  helps.<BR>Gary</SPAN></FONT></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16C88.2D1ECD70--


From owner-seamoby@diameter.org  Tue Nov 13 16:40:56 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18050
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:40:46 -0500 (EST)
Received: (qmail 13395 invoked by alias); 13 Nov 2001 22:07:08 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13385 invoked by uid 200); 13 Nov 2001 22:07:07 -0000
Received: (qmail 13371 invoked from network); 13 Nov 2001 22:07:02 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:07:02 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095CRX>; Tue, 13 Nov 2001 16:17:22 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F999@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:17:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C88.94E7B610"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C88.94E7B610
Content-Type: text/plain;
	charset="iso-8859-1"

Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C88.94E7B610
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C5F.71909C00">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Majid,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>Consider
the case where the context transfer occurs before handover. So, the =
context
will arrive at the newAR before</span></font><font color=3Dolive><span
style=3D'color:olive;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>The
mobile node does. What if something goes wrong &#8211; the context is =
not correctly
received by the newAR.</span></font><font color=3Dolive><span =
style=3D'color:olive;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>When
the MN arrives at the newAR, it needs to know this fact. So, the MN =
should
authenticate the received context, just</span></font><font =
color=3Dolive><span
style=3D'color:olive;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>To
make sure that its context was successfully received by the =
newAR.</span></font><font
color=3Dolive><span =
style=3D'color:olive;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dolive><span =
style=3D'color:olive;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dolive face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:olive'>-Sharif.</span></font><font =
color=3Dblack><span
style=3D'color:black'>&nbsp;</span></font><font color=3Dolive><span
style=3D'color:olive;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Maybe you mean that the MN should
authenticate the received context data, but</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>then why does the MN should do =
this. The
context is going to the new AR, anyway.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>If authentication of data is =
needed, new
AR does it on behalf of MN.</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Why are we dragging MN into the
authentication process.</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>these issues are attacking the =
basic
framework of CT, IMHO</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Madjid</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:.5in'><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
10:44 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Gary Kenward'; =
Shahrier,
Sharif M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
seamoby@cdma-2000.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>Gary,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Understood.
However, the requirements contains nothing (?) about the mobile =
authenticating
with its context, after the context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>Has been =
transferred.
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>I think a =
requirement
should be there for this, otherwise, without authentication, the MN can =
&#8220;get
at&#8221; any context, or context feature that its not authorized =
access to.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>How =
about:<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><b><span
style=3D'font-weight:bold'>There MUST be mutual authentication between =
the MN and
its context, after the context transfer has =
occurred.<o:p></o:p></span></b></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><b><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman";font-weight:bold'>&nbsp;<o:p></o:p></span></font></b></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><b><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman";font-weight:bold'>-Sharif.<o:p></o:p></span></font></b></span></p=
>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gary Kenward
[mailto:gkenward@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
11:07 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Sharif:</span></=
font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>&nbsp; This =
requirement
is for the ARs to authenticate each other so that a ct exchange =
can</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>be trusted. It =
has
nothing to do with the MN and handoff per se.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Gary</span></fon=
t><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:39.75pt;border:none;mso-border-left-alt:solid blue 1.5pt;
padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> November 13, 2001 =
09:51<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahrier, Sharif =
M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3D"#993366" face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:#993366'>I have some issues with the following requirement in the =
CT
draft.</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>4=
.9 The
entities transferring context MUST have completed a mutual =
authentication
process prior to<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>initiating the
transfer.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 don&#8217;t
support this requirement.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
t appears
to me this may not fit the case for &#8220;break-before-make&#8221; =
handover .<span
style=3D"mso-spacerun: yes">&nbsp; </span>For instance, the mobile may =
break
connection with the old<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
P, and
re-establish connection with the new AP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
ssuming
that the context is transferred prior to re-establishing the new =
connection.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
he mobile
will need to re-authenticate after it makes a new connection at its new =
AP.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 have
seen several practical cases that supports this scanario, thus I feel =
it is
necessary for authentication after the transfer of context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>i=
n
&#8220;break-before-make&#8221;.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C16C88.94E7B610--


From owner-seamoby@diameter.org  Tue Nov 13 16:59:47 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18559
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:59:36 -0500 (EST)
Received: (qmail 13630 invoked by alias); 13 Nov 2001 22:11:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13624 invoked by uid 200); 13 Nov 2001 22:11:25 -0000
Received: (qmail 13618 invoked from network); 13 Nov 2001 22:11:20 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:11:20 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADLMFS05056
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 16:22:15 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Tue, 13 Nov 2001 16:22:50 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W32916D2>; Tue, 13 Nov 2001 16:21:54 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA463E@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:21:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C89.36FE9D60"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C89.36FE9D60
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
  You have totally lost me here. The intent for CT is to transfer context
between functionally
equivalent peers. Specifically, ARs. The purpose of this context is to
support forwarding service
at an AR. The MN does not have access to this context. 
 
  If the network has security requirements for MN access (e.g.
authentication, authorization, encryption), 
then this implies there is a security context at the old AR that must be
relocated to the  new AR in order
for the MN to send bearer traffic through the AN. Again, the MN does not
have, or need to have, access
to this context. By definition, the MN would not know what to do with the
context, as it represents forwarding
service features.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 11:44
To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C89.36FE9D60
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16C39.4040D190" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>&nbsp; You have totally lost me here. The intent for CT 
is to transfer context between functionally</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>equivalent peers. Specifically, ARs. The purpose of 
this context is to support forwarding service</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=782162221-13112001>at 
an AR. The MN does not have access to this context. </SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>&nbsp; If the network has security requirements for MN 
access (e.g. authentication, authorization, encryption), </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>then this implies there is a security context at the 
old AR that must be relocated to the&nbsp; new AR in order</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=782162221-13112001>for 
the MN to send bearer traffic through the AN. Again, the MN does not have, or 
need to have, access</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=782162221-13112001>to 
this context. By definition, the MN would not know what to do with the context, 
as it represents forwarding</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>service features.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=782162221-13112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 13, 2001 
  11:44<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif 
  M.<BR><B>Cc:</B> 'seamoby@cdma-2000.org'<BR><B>Subject:</B> RE: [seamoby] Some 
  proposed changes to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Understood. However, the requirements contains nothing (?) about the 
  mobile authenticating with its context, after the context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Has 
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">I 
  think a requirement should be there for this, otherwise, without 
  authentication, the MN can &#8220;get at&#8221; any context, or context feature that its 
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">How 
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN><B><SPAN style="FONT-WEIGHT: bold">There MUST be mutual authentication 
  between the MN and its context, after the context transfer has 
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><B><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><B><FONT color=#003300 
  face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle22><FONT color=#003300 face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><FONT color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Gary 
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 11:07 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif 
  M.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
  style="FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Sharif:</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">&nbsp; This 
  requirement is for the ARs to authenticate each other so that a ct exchange 
  can</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">be trusted. It has 
  nothing to do with the MN and handoff per se.</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Gary</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; BORDER-RIGHT: medium none; BORDER-TOP: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; PADDING-TOP: 0in">
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-margin-top-alt: auto; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 09:51<BR><B><SPAN 
  style="FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif M.<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> 'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=#993366 face="Times New Roman" size=3><SPAN 
  style="COLOR: #993366; FONT-SIZE: 12pt">I have some issues with the following 
  requirement in the CT draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">4.9 
  The entities transferring context MUST have completed a mutual authentication 
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>initiating the 
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  don&#8217;t support this requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">It 
  appears to me this may not fit the case for &#8220;break-before-make&#8221; handover 
  .<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>For instance, the mobile may 
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">AP, 
  and re-establish connection with the new AP. 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Assuming 
  that the context is transferred prior to re-establishing the new 
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The 
  mobile will need to re-authenticate after it makes a new connection at its new 
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I have 
  seen several practical cases that supports this scanario, thus I feel it is 
  necessary for authentication after the transfer of context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">in 
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16C89.36FE9D60--


From owner-seamoby@diameter.org  Tue Nov 13 17:21:10 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19256
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 17:20:46 -0500 (EST)
Received: (qmail 13969 invoked by alias); 13 Nov 2001 22:19:37 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13962 invoked by uid 200); 13 Nov 2001 22:19:37 -0000
Received: (qmail 13948 invoked from network); 13 Nov 2001 22:19:24 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:19:24 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095CTN>; Tue, 13 Nov 2001 16:29:53 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99A@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:29:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C8A.54B1CE30"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C8A.54B1CE30
Content-Type: text/plain;
	charset="iso-8859-1"

Gary,
 
            I  agree that  MN "getting at" a context was not a good
description. However, please refer to my earlier posting to Majid's
comments.
            The reason for authentication with the MN is so that if the
context arrive at the newAR before the MN does, the MN needs to know that
            It did indeed arrive there correctly, and there was no problems
during the transfer, i.e. the context did not end up at a different AR from
that of the MN.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 4:22 PM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  You have totally lost me here. The intent for CT is to transfer context
between functionally
equivalent peers. Specifically, ARs. The purpose of this context is to
support forwarding service
at an AR. The MN does not have access to this context. 
 
  If the network has security requirements for MN access (e.g.
authentication, authorization, encryption), 
then this implies there is a security context at the old AR that must be
relocated to the  new AR in order
for the MN to send bearer traffic through the AN. Again, the MN does not
have, or need to have, access
to this context. By definition, the MN would not know what to do with the
context, as it represents forwarding
service features.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 11:44
To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
              Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
              There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C8A.54B1CE30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C61.3156BC80">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:script;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Gary,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>I
<span style=3D"mso-spacerun: yes">&nbsp;</span>agree that <span
style=3D"mso-spacerun: yes">&nbsp;</span>MN &#8220;getting at&#8221; a =
context was not a good
description. However, please refer to my earlier posting to =
Majid&#8217;s comments.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>The
reason for authentication with the MN is so that if the context arrive =
at the
newAR before the MN does, the MN needs to know =
that<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>It
did indeed arrive there correctly, and there was no problems during the
transfer, i.e. the context did not end up at a different AR from that =
of the
MN.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle23><font size=3D2 =
color=3Dolive
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gary Kenward
[mailto:gkenward@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
4:22 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>Sharif:</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>&nbsp; You have
totally lost me here. The intent for CT is to transfer context between
functionally</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>equivalent
peers. Specifically, ARs. The purpose of this context is to support =
forwarding
service</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>at an =
AR. The
MN does not have access to this context. </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>&nbsp; If the
network has security requirements for MN access (e.g. authentication,
authorization, encryption), </span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>then =
this
implies there is a security context at the old AR that must be =
relocated to
the&nbsp; new AR in order</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>for =
the MN to
send bearer traffic through the AN. Again, the MN does not have, or =
need to
have, access</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>to =
this
context. By definition, the MN would not know what to do with the =
context, as
it represents forwarding</span></font><font color=3Dblack><span =
style=3D'color:
black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>service
features.</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>Gary</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:3.75pt;border:none;mso-border-left-alt:solid blue =
1.5pt;padding:
0in;mso-padding-alt:0in 0in 0in 4.0pt'><font size=3D2 color=3Dblack =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> November 13, 2001 =
11:44<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Kenward, Gary
[WDLN2:AN10:EXCH]; Shahrier, Sharif M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>Gary,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Understood.
However, the requirements contains nothing (?) about the mobile =
authenticating
with its context, after the context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>Has
been transferred. <o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>I
think a requirement should be there for this, otherwise, without =
authentication,
the MN can &#8220;get at&#8221; any context, or context feature that =
its not authorized
access to.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>How
about:<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><b><span
style=3D'font-weight:bold'>There MUST be mutual authentication between =
the MN and
its context, after the context transfer has =
occurred.<o:p></o:p></span></b></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><b><font size=3D2 color=3D"#003300" face=3D"Times =
New Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";
font-weight:bold'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></b></span>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><b><font size=3D2 color=3D"#003300" face=3D"Times =
New Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;mso-ascii-font-famil=
y:"Times New Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";
font-weight:bold'>-Sharif.<o:p></o:p></span></font></b></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle22><font size=3D2 color=3D"#003300" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gary Kenward
[mailto:gkenward@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
11:07 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>Sharif:</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>&nbsp; This requirement is for the ARs to authenticate each =
other
so that a ct exchange can</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>be trusted. It has nothing to do with the MN and handoff =
per se.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>Gary</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:7.5pt;border:none;mso-border-left-alt:solid blue =
1.5pt;padding:
0in;mso-padding-alt:0in 0in 0in 4.0pt'><font size=3D2 color=3Dblack =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> November 13, 2001 =
09:51<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahrier, Sharif =
M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:7.5pt;border:none;mso-border-l=
eft-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3D"#993366" face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:#993366'>I have some issues with the following requirement in the =
CT
draft.</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>4=
.9 The
entities transferring context MUST have completed a mutual =
authentication
process prior to<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>initiating the
transfer.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 don&#8217;t
support this requirement.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
t appears
to me this may not fit the case for &#8220;break-before-make&#8221; =
handover .<span
style=3D"mso-spacerun: yes">&nbsp; </span>For instance, the mobile may =
break
connection with the old<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
P, and
re-establish connection with the new AP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
ssuming
that the context is transferred prior to re-establishing the new =
connection.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
he mobile
will need to re-authenticate after it makes a new connection at its new =
AP.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 have seen
several practical cases that supports this scanario, thus I feel it is
necessary for authentication after the transfer of context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>i=
n
&#8220;break-before-make&#8221;.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C16C8A.54B1CE30--


From owner-seamoby@diameter.org  Tue Nov 13 17:44:23 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20030
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 17:43:48 -0500 (EST)
Received: (qmail 14091 invoked by alias); 13 Nov 2001 22:22:41 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14085 invoked by uid 200); 13 Nov 2001 22:22:41 -0000
Received: (qmail 14073 invoked from network); 13 Nov 2001 22:22:34 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:22:34 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADLXTS06320
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 16:33:29 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Tue, 13 Nov 2001 16:33:54 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W32916NS>; Tue, 13 Nov 2001 16:33:02 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA463F@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:32:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C8A.C3FD5250"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C8A.C3FD5250
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
Sorry, but no, I do not agree. We had an extensive debate last spring over
the role of the MN
in CT, and (it is my understanding) that the MN should not, could not be
required to participate 
in CT. The rationale was that MN involvement would likely slow down the
process, and thus,
degrade the seamlessness.
 
CT is in support of seamless mobility (or at least, that's what I thought
this was all about).
If CT works, then the handover will be seamless. If, by exception, CT does
not work, then
seamlessness is lost and the service will degrade. What it degrades to is,
IMHO, a policy 
set by the operator (or a forced drop of all IP sessions due to the physics
of the channel). 
Having the MN authenticate the context does not improve seamlessness,
indeed, it can only degrade it, as the authentication process implies over
the air signalling,
and significant additional delays. And, definitely, if CT fails - e.g. if
the context has become
"stale" for some reason, then authentication does not help maintain
seamlessness. 
 
If CT failures, whether due to stale context or something else, creates
security problems, then
these need to be addressed. But, we should wait until we understand the
requirements for security
context transfer, before we state requirements for solutions to speculated
problems.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 16:17
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; Kenward, Gary
[WDLN2:AN10:EXCH]
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C8A.C3FD5250
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16C5F.71909C00" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>Sorry, but no, I do not agree. We had an extensive 
debate last spring over the role of the MN</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>in 
CT, and (it is my understanding) that the MN should not, could not be required 
to participate </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>in 
CT. The rationale was that MN involvement would likely slow down the process, 
and thus,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>degrade the seamlessness.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>CT 
is in support of seamless mobility (or at least, that's what I thought this was 
all about).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>If 
CT works, then the handover will be seamless. If, by exception, CT does not 
work, then</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>seamlessness is lost and the service will degrade. What 
it degrades to is, IMHO, a policy </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>set 
by the operator (or a forced drop of all IP sessions due to the physics of the 
channel). </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>Having the MN authenticate the context does not improve 
seamlessness,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>indeed, it can only degrade it, as the authentication 
process implies over the air signalling,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>and 
significant additional delays. And, definitely, if CT fails - e.g. if the 
context has become</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>"stale" for some reason, then authentication does not 
help maintain seamlessness. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=103582721-13112001>If 
CT failures, whether due to stale context or something else, creates security 
problems, then</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>these need to be addressed. But, we should wait until 
we understand the requirements for security</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>context transfer, before we state requirements for 
solutions to speculated problems.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=103582721-13112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 13, 2001 
  16:17<BR><B>To:</B> 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; Kenward, 
  Gary [WDLN2:AN10:EXCH]<BR><B>Cc:</B> seamoby@cdma-2000.org<BR><B>Subject:</B> 
  RE: [seamoby] Some proposed changes to the requirements 
  draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Consider the case where the context transfer occurs before handover. 
  So, the context will arrive at the newAR before</SPAN></FONT><FONT 
  color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>The mobile node does. What if something goes wrong &#8211; the context is not 
  correctly received by the newAR.</SPAN></FONT><FONT color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>When the MN arrives at the newAR, it needs to know this fact. So, the 
  MN should authenticate the received context, just</SPAN></FONT><FONT 
  color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>To make sure that its context was successfully received by the 
  newAR.</SPAN></FONT><FONT color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=olive face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt">-Sharif.</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black">&nbsp;</SPAN></FONT><FONT 
  color=olive><SPAN 
  style="COLOR: olive; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Maybe you mean that 
  the MN should authenticate the received context data, but</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">then why does the MN 
  should do this. The context is going to the new AR, anyway.</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">If authentication of 
  data is needed, new AR does it on behalf of MN.</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Why are we dragging 
  MN into the authentication process.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">these issues are 
  attacking the basic framework of CT, IMHO</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Madjid</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 10:44 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Gary Kenward'; 
  Shahrier, Sharif M.<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  seamoby@cdma-2000.org<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Understood. However, the requirements contains nothing (?) about the 
  mobile authenticating with its context, after the context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Has 
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">I 
  think a requirement should be there for this, otherwise, without 
  authentication, the MN can &#8220;get at&#8221; any context, or context feature that its 
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">How 
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN><B><SPAN style="FONT-WEIGHT: bold">There MUST be mutual authentication 
  between the MN and its context, after the context transfer has 
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Gary 
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 11:07 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif 
  M.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=blue face=Arial 
  size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Sharif:</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">&nbsp; 
  This requirement is for the ARs to authenticate each other so that a ct 
  exchange can</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">be 
  trusted. It has nothing to do with the MN and handoff per 
  se.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT color=blue face=Arial 
  size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Gary</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; BORDER-RIGHT: medium none; BORDER-TOP: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; PADDING-TOP: 0in">
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-margin-top-alt: auto; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 09:51<BR><B><SPAN 
  style="FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif M.<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> 'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=#993366 face="Times New Roman" size=3><SPAN 
  style="COLOR: #993366; FONT-SIZE: 12pt">I have some issues with the following 
  requirement in the CT draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">4.9 
  The entities transferring context MUST have completed a mutual authentication 
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>initiating the 
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  don&#8217;t support this requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">It 
  appears to me this may not fit the case for &#8220;break-before-make&#8221; handover 
  .<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>For instance, the mobile may 
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">AP, 
  and re-establish connection with the new AP. 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Assuming 
  that the context is transferred prior to re-establishing the new 
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The 
  mobile will need to re-authenticate after it makes a new connection at its new 
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I have 
  seen several practical cases that supports this scanario, thus I feel it is 
  necessary for authentication after the transfer of context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">in 
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 39.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16C8A.C3FD5250--


From owner-seamoby@diameter.org  Tue Nov 13 18:04:28 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20642
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 18:04:20 -0500 (EST)
Received: (qmail 14238 invoked by alias); 13 Nov 2001 22:27:17 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14232 invoked by uid 200); 13 Nov 2001 22:27:17 -0000
Received: (qmail 14226 invoked from network); 13 Nov 2001 22:27:12 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:27:12 -0000
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 NAA22245;
	Tue, 13 Nov 2001 13:38:34 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fADLcXK01745;
	Tue, 13 Nov 2001 13:38:33 -0800
X-mProtect:  Tue, 13 Nov 2001 13:38:33 -0800 Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.18.141.130, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdU1lTW9; Tue, 13 Nov 2001 13:38:30 PST
Message-ID: <3BF192D5.C654DAF@iprg.nokia.com>
Date: Tue, 13 Nov 2001 13:38:29 -0800
From: Cedric Westphal <cedric@IPRG.nokia.com>
Organization: NOKIA
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
References: <9FBD322B7824D511B36900508BF93C9C01AA463D@zcard031.ca.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------33B33BA3E05C8396CE56E295"
Sender: owner-seamoby@diameter.org
Precedence: bulk


--------------33B33BA3E05C8396CE56E295
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Gary, Sharif, John,

if the requirement is a given, then let's not argue about/against it. It
cannot
hurt to include it, and _technically_ there is consensus for it.

As far as how to phrase it, usually scalability is described as the
marginal increase
in complexity induced by adding users. So something along the lines:
the processing complexity at each AR (and the burden on the wired
network)
SHOULD increase linearly with the number of MNs or the number of CT
requests.

Also, you can check conformance there.

Cedric.





Gary Kenward wrote:

> Sharif:
>
>      -----Original Message-----
>      From: Shahrier, Sharif M.
>      [mailto:Sharif.Shahrier@InterDigital.com]
>      Sent: November 13, 2001 11:29
>      To: Kenward, Gary [WDLN2:AN10:EXCH];
>      'john.loughney@nokia.com'; Shahrier, Sharif M.;
>      seamoby@cdma-2000.org
>      Subject: RE: [seamoby] Some proposed changes to the
>      requirements draft.
>
>      Gary,
>
>      >
>      > > 4.16 "The context transfer protocol MUST be scalable. It
>      MUST be
>      > > scalable to millions of hosts".
>      >
>      > This is 'motherhood & apple pie' text (i.e. - noone would
>      really
>      > disagree). I don't know how this adds anything to the
>      text.
>      > Additionally, I would suggest SHOULD rather than MUST is
>      > what you mean.
>      >
>
>      Myself, I do not know what "scaleable to millions of hosts"
>      really means. If the concern is in regards to the ability
>      for the context
>      transfer solution to support a real wireless mobile network
>      and one of the
>      constraining factors is the number of ct's that can be
>      handled per time period,
>      then both the number of terminals *and* the number of
>      handoffs per time period
>      are at issue (is trivial to say that any ct solution can
>      handle an infinite number
>      of terminals if the handoff rate is zero
>
>      I agree with this. Number of cts handled per time period
>      and the number of handoffs per time
>
>      Period are both good cases to support the scalability
>      requirement. The other point is the quantity of context
>      information
>
>      Being transferred for each mobile over a given time. This
>      bandwidth must be scalable.
>
>      It is not clear to me how we would define the scaleability
>      of ct in any real
>      terms. We know that it must be applicable to within an
>      administrative domain,
>      and thus, the top limit would be the IP address space, but
>      that is a greatest
>      upper bound and not very useful. Usually, in these
>      situations, people resort
>      to rate of complexity measures to define scaleability.
>
>      I agree that the scalability of the CT must be applicabile
>      within an administrative domain; scalability must also
>
>      Be applicable across different operator networks as well.
>
>      I dont see how the IPv4 address space affects the
>      scalability of CT. Could you please explain?
>      [gwk] I doesn't, other then it puts "a" limit on the
>      possible number of mobiles within an
>      administrative domain. An very high limit. Even higher if
>      the domain uses IPv6.
>
>      Finally, scaleability is desireable, as long as the
>      requirement is for scaleability
>      at an acceptable cost.
>
>      Other then this, I do not know how one would word a
>      requirement around scaleability
>      other then the motherhood of "ct must be scaleable at an
>      acceptable cost".
>
>      I agree. Perhaps something like:
>
>      4.16 The context transfer protocol MUST be scalable at an
>      acceptable cost.
>
>      The context transfer protocol MUST be ale to handle a large
>      number of of context transfers per second, and MUST
>
>      Be able to support a large number of handoffs per second.
>      The quantity of context information being transferred for
>      each
>
>      Mobile per second MUST be scalable, i.e. the bandwidth of
>      the context transfer MUST be scalable.
>
>      The context transfers MAY be within the same administrative
>      domain, or they MAY be across different
>
>      administrative domains.
>      [gwk] This is actually 7 requirements. And, there is no way
>      to ensure conformance to  a number of them
>      as written. While there are requirements in the existing
>      draft that will be difficult to ensure conformance, the wg
>      has made an effort to stay away from requirements which
>      could not be tested (e.g. there is no "ct must be fast"
>      requirement).
>
>      My personal opinion is in line with what John stated, that
>      scalability is a given. Arguably, many stated requirements
>      are "givens", but are stated for reinforcement. On the other
>      hand, many givens are not stated as requirements simply to
>      keep the number of requirements and the scope of the
>      document to a manageable level. I would put "saleability" in
>
>      the latter category, particularly with all the caveats that
>      must go along with any saleability requirement for ct.
>
>      I hope this helps.
>      Gary
>

--------------33B33BA3E05C8396CE56E295
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body link="#0000FF" vlink="#0000FF" lang="EN-US" style="tab-interval: .5in">
Gary, Sharif, John,
<p>if the requirement is a given, then let's not argue about/against it.
It cannot
<br>hurt to include it, and _technically_ there is consensus for it.
<p>As far as how to phrase it, usually scalability is described as the
marginal increase
<br>in complexity induced by adding users. So something along the lines:
<br>the processing complexity at each AR (and the burden on the wired network)
<br>SHOULD increase linearly with the number of MNs or the number of CT
requests.
<p>Also, you can check conformance there.
<p>Cedric.
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>Gary Kenward wrote:
<blockquote TYPE=CITE><link 
href="cid:filelist.xml@01C16C37.27CD6DA0" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]--><style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<span 
class=927120321-13112001><font face="Comic Sans MS"><font color="#0000FF">Sharif:</font></font></span>
<blockquote 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Shahrier, Sharif M.
[<A HREF="mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@InterDigital.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> November 13, 2001 11:29</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> Kenward, Gary [WDLN2:AN10:EXCH];
'john.loughney@nokia.com'; Shahrier, Sharif M.; seamoby@cdma-2000.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> RE: [seamoby] Some
proposed changes to the requirements draft.</font></font>
<br>&nbsp;</div>

<div class=Section1><span 
  style="COLOR: navy; FONT-SIZE: 12pt; FONT-WEIGHT: bold; mso-bidi-font-size: 10.0pt"><b><font face="Times New Roman"><font color="#000080"><font size=+0>Gary,</font></font></font></b></span><span 
  style="COLOR: navy; FONT-WEIGHT: bold; mso-bidi-font-size: 10.0pt; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font face="Times New Roman"><font color="#000000"><font size=-1>>&nbsp;</font></font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
> 4.16 "The context transfer protocol MUST be scalable. It MUST be&nbsp;</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
> scalable to millions of hosts".</font></font></span><span style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>&nbsp;</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
This is 'motherhood &amp; apple pie' text (i.e. - noone would really</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
disagree). I don't know how this adds anything to the text.&nbsp;</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
Additionally, I would suggest SHOULD rather than MUST is</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>
what you mean.</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>>&nbsp;</font></font></span><span 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font face="Times New Roman"><font color="#000000"><font size=-1>Myself,
I do not know what "scaleable to millions of hosts"</font></font></font></span><span style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>really
means. If the concern is in regards to the ability for the context</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>transfer
solution to support a real wireless mobile network and one of the</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>constraining
factors is the number of ct's that can be handled per time period,</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>then
both the number of terminals *and* the number of handoffs per time period</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>are
at issue (is trivial to say that any ct solution can handle an infinite
number</font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>of
terminals if the handoff rate is zero</font></font></span><span 
  style="COLOR: navy; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>I
agree with this. Number of cts handled per time period and the number
of handoffs per time</font></font></font><o:p></o:p></span></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>Period
are both good cases to support the scalability requirement. The other point
is the quantity of context information</font></font></font><o:p></o:p></span></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>Being
transferred for each mobile over a given time. This bandwidth must be scalable.</font></font></font><o:p></o:p></span></span>
<p><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font face="Times New Roman"><font color="#000000"><font size=-1>
It is not clear to me how we would define the scaleability of ct in any
real</font></font></font></span><span 
  style="COLOR: black">
<br></span><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>terms.
We know that it must be applicable to within an administrative domain,</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>and
thus, the top limit would be the IP address space, but that is a greatest</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>upper
bound and not very useful. Usually, in these situations, people resort</font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>to
rate of complexity measures to define scaleability.</font></font></span><span 
  style="COLOR: black"></span><span 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>I
agree that the scalability of the CT must be applicabile within an administrative
domain; scalability must also</font></font></font><o:p></o:p></span></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>Be
applicable across different operator networks as well.</font></font></font><o:p></o:p></span></span>
<p><span class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><font face="Arial"><font color="#000080"><font size=-1>I
dont see how the IPv4 address space affects the scalability of CT. Could
you please explain?</font></font></font>
<br><span class=927120321-13112001><font face="Comic Sans MS"><font color="#0000FF"><font size=+0>[gwk]
I doesn't, other then it puts "a" limit on the possible number of mobiles
within an&nbsp;</font></font></font></span></span></span><span 
  class=EmailStyle19><span 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><span 
  class=927120321-13112001>
<br><font face="Comic Sans MS"><font color="#0000FF"><font size=+0>administrative
domain. An very high limit. Even higher if the domain uses IPv6.&nbsp;</font></font></font></span><o:p></o:p></span></span>
<p><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font face="Times New Roman"><font color="#000000"><font size=-1>
Finally, scaleability is desireable, as long as the requirement is for
scaleability</font></font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>at
an acceptable cost.&nbsp;</font></font></span><span 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: black; FONT-SIZE: 10pt"><font face="Times New Roman"><font color="#000000"><font size=-1>
Other then this, I do not know how one would word a requirement around
scaleability</font></font></font></span><span style="COLOR: black">
<br></span><span style="COLOR: black; FONT-SIZE: 10pt"><font color="#000000"><font size=-1>other
then the motherhood of "ct must be scaleable at an acceptable cost".</font></font></span><span style="COLOR: black"></span><span 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><font face="Times New Roman"><font color="#000080">I
agree. Perhaps something like:</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><font face="Times New Roman"><font color="#000080">4.16
The context transfer protocol MUST be scalable at an acceptable cost.</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><span 
  style="mso-spacerun: yes"></span><font face="Times New Roman"><font color="#000080">The
context transfer protocol MUST be ale to handle a large number of&nbsp;<span style="mso-spacerun: yes"></span>of
context transfers per second, and MUST</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><span 
  style="mso-spacerun: yes"></span><font face="Times New Roman"><font color="#000080">Be
able to support a large number of handoffs per second. The quantity of
context information being transferred for each&nbsp;</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><span 
  style="mso-spacerun: yes"></span><font face="Times New Roman"><font color="#000080">Mobile
per second MUST be scalable, i.e. the bandwidth of the context transfer
MUST be scalable.</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><span 
  style="mso-spacerun: yes"></span><font face="Times New Roman"><font color="#000080">The
context transfers MAY be within the same administrative domain, or they
MAY be across different&nbsp;</font></font></span><span 
  style="COLOR: navy; mso-color-alt: windowtext"><o:p></o:p></span>
<p><span 
  style="COLOR: navy; FONT-SIZE: 12pt"><span 
  style="mso-spacerun: yes"></span><font face="Times New Roman"><font color="#000080">administrative
domains.</font></font></span><span 
  style="COLOR: black">
<br><span 
  class=927120321-13112001><font face="Comic Sans MS"><font color="#0000FF">[gwk]
This is actually 7 requirements. And, there is no way to ensure conformance
to&nbsp; a number of them</font></font></span></span><span 
  style="COLOR: black"><span 
  class=927120321-13112001>
<br><font face="Comic Sans MS"><font color="#0000FF">as written.&nbsp;</span></span><span style="COLOR: black"><span class=927120321-13112001>While
there are requirements in the existing draft that will be difficult to
ensure conformance,&nbsp;</span></span><span 
  style="COLOR: black"><span 
  class=927120321-13112001>the
wg</font></font></span></span><span style="COLOR: black"><span class=927120321-13112001>
<br><font face="Comic Sans MS"><font color="#0000FF">has made an effort
to stay away from requirements which could not be tested (e.g. there is
no "ct must be fast"</font></font></span></span><span 
  style="COLOR: black"><span 
  class=927120321-13112001>
<br><font face="Comic Sans MS"><font color="#0000FF">requirement).&nbsp;</font></font></span></span>
<p><span class=927120321-13112001><font face="Comic Sans MS"><font color="#0000FF">My
personal opinion is in line with what John stated, that scalability is
a given. Arguably, many stated requirements</font></font>
<br><font face="Comic Sans MS"><font color="#0000FF">are "givens", but
are stated for reinforcement. On the other hand, many givens are not stated
as requirements simply to</font></font>
<br><font face="Comic Sans MS"><font color="#0000FF">keep the number of
requirements and the scope of the document to a manageable level. I would
put "saleability" in</font></font>
<br><font face="Comic Sans MS"><font color="#0000FF">the latter category,
particularly with all the caveats that must go along with any saleability
requirement for ct.</font></font></span>
<p><span style="COLOR: black"><span class=927120321-13112001><font face="Comic Sans MS"><font color="#0000FF">I
hope this helps.</font></font>
<br><font face="Comic Sans MS"><font color="#0000FF">Gary</font></font></span></span></div>
</blockquote>
</blockquote>

</body>
</html>

--------------33B33BA3E05C8396CE56E295--



From owner-seamoby@diameter.org  Tue Nov 13 18:23:42 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21407
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 18:23:25 -0500 (EST)
Received: (qmail 14304 invoked by alias); 13 Nov 2001 22:29:01 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14298 invoked by uid 200); 13 Nov 2001 22:29:01 -0000
Received: (qmail 14291 invoked from network); 13 Nov 2001 22:28:54 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:28:54 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADLdkS06997
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 16:39:46 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Tue, 13 Nov 2001 16:40:13 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W32916S7>; Tue, 13 Nov 2001 16:39:22 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4640@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:39:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C8B.A8061770"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C8B.A8061770
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
  I have responded in a previous message, but to add a comment in response
to the direction you
are describing: one vision of CT is that it actually does transfer context
to ARs before the MN 
arrives (e.g. it is proactive), and because of the physics of RF coverage
and mobility, this means
that the context should be transfered to a number of candidate ARs. Yes,
there are lots of issues
with this approach, but the intent is improve bearer service handover.
 
Cheers,
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 16:30
To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
 
            I  agree that  MN "getting at" a context was not a good
description. However, please refer to my earlier posting to Majid's
comments.
            The reason for authentication with the MN is so that if the
context arrive at the newAR before the MN does, the MN needs to know that
            It did indeed arrive there correctly, and there was no problems
during the transfer, i.e. the context did not end up at a different AR from
that of the MN.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 4:22 PM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  You have totally lost me here. The intent for CT is to transfer context
between functionally
equivalent peers. Specifically, ARs. The purpose of this context is to
support forwarding service
at an AR. The MN does not have access to this context. 
 
  If the network has security requirements for MN access (e.g.
authentication, authorization, encryption), 
then this implies there is a security context at the old AR that must be
relocated to the  new AR in order
for the MN to send bearer traffic through the AN. Again, the MN does not
have, or need to have, access
to this context. By definition, the MN would not know what to do with the
context, as it represents forwarding
service features.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 11:44
To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
              Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
              There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16C8B.A8061770
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16C61.3156BC80" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:script;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>&nbsp; I have responded in a previous message, but to 
add a comment in response to the direction you</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=318273821-13112001>are 
describing: one vision of CT is that it actually does transfer context to ARs 
before the MN </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>arrives (e.g. it is proactive), and because of the 
physics of RF coverage and mobility, this means</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>that the context should be transfered to a number of 
candidate ARs. Yes, there are lots of issues</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>with this approach, but the intent is improve bearer 
service handover.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>Cheers,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=318273821-13112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 13, 2001 
  16:30<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif 
  M.<BR><B>Cc:</B> 'seamoby@cdma-2000.org'<BR><B>Subject:</B> RE: [seamoby] Some 
  proposed changes to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>I <SPAN style="mso-spacerun: yes">&nbsp;</SPAN>agree that <SPAN 
  style="mso-spacerun: yes">&nbsp;</SPAN>MN &#8220;getting at&#8221; a context was not a 
  good description. However, please refer to my earlier posting to Majid&#8217;s 
  comments.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>The reason for authentication with the MN is so that if the context 
  arrive at the newAR before the MN does, the MN needs to know 
  that<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>It did indeed arrive there correctly, and there was no problems during 
  the transfer, i.e. the context did not end up at a different AR from that of 
  the MN.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle23><FONT color=olive face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><FONT color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Gary 
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 4:22 
  PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif 
  M.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
  style="FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">Sharif:</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">&nbsp; You 
  have totally lost me here. The intent for CT is to transfer context between 
  functionally</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">equivalent 
  peers. Specifically, ARs. The purpose of this context is to support forwarding 
  service</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">at an AR. 
  The MN does not have access to this context. </SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">&nbsp; If 
  the network has security requirements for MN access (e.g. authentication, 
  authorization, encryption), </SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">then this 
  implies there is a security context at the old AR that must be relocated to 
  the&nbsp; new AR in order</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">for the MN 
  to send bearer traffic through the AN. Again, the MN does not have, or need to 
  have, access</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">to this 
  context. By definition, the MN would not know what to do with the context, as 
  it represents forwarding</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">service 
  features.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">Gary</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; BORDER-RIGHT: medium none; BORDER-TOP: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; PADDING-TOP: 0in">
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-margin-top-alt: auto; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 11:44<BR><B><SPAN 
  style="FONT-WEIGHT: bold">To:</SPAN></B> Kenward, Gary [WDLN2:AN10:EXCH]; 
  Shahrier, Sharif M.<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Understood. However, the requirements contains nothing (?) about the 
  mobile authenticating with its context, after the context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Has 
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">I 
  think a requirement should be there for this, otherwise, without 
  authentication, the MN can &#8220;get at&#8221; any context, or context feature that its 
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">How 
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN><B><SPAN style="FONT-WEIGHT: bold">There MUST be mutual authentication 
  between the MN and its context, after the context transfer has 
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle22><FONT color=#003300 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Gary 
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 11:07 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif 
  M.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Sharif:</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">&nbsp; This 
  requirement is for the ARs to authenticate each other so that a ct exchange 
  can</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">be trusted. It has 
  nothing to do with the MN and handoff per se.</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Gary</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P></DIV>
  <DIV 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; BORDER-RIGHT: medium none; BORDER-TOP: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; PADDING-TOP: 0in">
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-margin-top-alt: auto; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 09:51<BR><B><SPAN 
  style="FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif M.<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> 'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=#993366 face="Times New Roman" size=3><SPAN 
  style="COLOR: #993366; FONT-SIZE: 12pt">I have some issues with the following 
  requirement in the CT draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">4.9 
  The entities transferring context MUST have completed a mutual authentication 
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>initiating the 
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  don&#8217;t support this requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">It 
  appears to me this may not fit the case for &#8220;break-before-make&#8221; handover 
  .<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>For instance, the mobile may 
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">AP, 
  and re-establish connection with the new AP. 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Assuming 
  that the context is transferred prior to re-establishing the new 
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The 
  mobile will need to re-authenticate after it makes a new connection at its new 
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I have 
  seen several practical cases that supports this scanario, thus I feel it is 
  necessary for authentication after the transfer of context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">in 
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 7.5pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16C8B.A8061770--


From owner-seamoby@diameter.org  Tue Nov 13 18:42:56 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21699
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 18:42:52 -0500 (EST)
Received: (qmail 14379 invoked by alias); 13 Nov 2001 22:31:01 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14373 invoked by uid 200); 13 Nov 2001 22:31:01 -0000
Received: (qmail 14366 invoked from network); 13 Nov 2001 22:30:56 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:30:56 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095CVH>; Tue, 13 Nov 2001 16:41:25 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99B@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:41:25 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16C8B.F18CB930"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C8B.F18CB930
Content-Type: text/plain;
	charset="iso-8859-1"

Gary,
 
             
If CT failures, whether due to stale context or something else, creates
security problems, then
these need to be addressed. But, we should wait until we understand the
requirements for security
context transfer, before we state requirements for solutions to speculated
problems.
 
            Are these types of problems outside the scope of the current CT
requirements draft?
 
-Sharif.

------_=_NextPart_001_01C16C8B.F18CB930
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16C62.CE3DDC80">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:script;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:teal;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dteal face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:teal'>Gary,</span></font><font =
color=3Dteal><span
style=3D'color:teal;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dteal face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:teal'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dteal><span =
style=3D'color:teal;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dteal face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:teal'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span></span></font><font
color=3Dblack><span style=3D'color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>If CT =
failures,
whether due to stale context or something else, creates security =
problems, then</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>these =
need to
be addressed. But, we should wait until we understand the requirements =
for
security</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>context
transfer, before we state requirements for solutions to speculated =
problems.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;co=
lor:teal'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>Are
these types of problems outside the scope of the current CT =
requirements draft?</span></font></span><span
class=3DEmailStyle21><font size=3D2 color=3Dteal face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial;color:teal;mso-color-=
alt:
windowtext'><o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C16C8B.F18CB930--


From owner-seamoby@diameter.org  Tue Nov 13 18:50:21 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21807
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 18:50:10 -0500 (EST)
Received: (qmail 15060 invoked by alias); 13 Nov 2001 22:53:45 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 15054 invoked by uid 200); 13 Nov 2001 22:53:45 -0000
Received: (qmail 15046 invoked from network); 13 Nov 2001 22:53:40 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 22:53:40 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fADM4VS08879
	for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:04:31 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Tue, 13 Nov 2001 17:04:49 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W32917AP>; Tue, 13 Nov 2001 16:59:58 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4643@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 16:59:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16C8E.88AE6190"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16C8E.88AE6190
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
Not my call, but I would hope so. We have to address the issues in stages or
we will
never progress.
 
Most important, however, is that you cannot speculate on problems with CT
until we
understand the CT protocol and process. IMHO, the purpose of requirements
draft is not
to try and anticipate all the possible problems that might emerge from a
given solution.
And we already have requirements for maintaining security during CT.
 
Finally, this is not DoD work: the requirements are not intended to be the
utlimate,
cast-in-titanium, truth about CT for all time. It should be reasonably
complete, but
we must expect that we will discover more about the problem domain when we
start
working on solutions. No one, as far as I have ever heard or experienced,
has ever
succeed in doing a complete waterfall design for a system of any significant
complexity
(I think the requirements document for the pet rock was never changed after
approval).
 
Just my delusional opinion.
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 16:41
To: Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.; 'Nakhjiri
Madjid-MNAKHJI1'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
 
             
If CT failures, whether due to stale context or something else, creates
security problems, then
these need to be addressed. But, we should wait until we understand the
requirements for security
context transfer, before we state requirements for solutions to speculated
problems.
 
            Are these types of problems outside the scope of the current CT
requirements draft?
 
-Sharif.

------_=_NextPart_001_01C16C8E.88AE6190
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16C62.CE3DDC80" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:script;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:teal;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=279155721-13112001>Not 
my call, but I would hope so. We have to address the issues in stages or we 
will</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>never progress.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>Most important, however, is that you cannot speculate 
on problems with CT until we</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>understand the CT protocol and process. IMHO,&nbsp;the 
purpose of requirements draft is not</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=279155721-13112001>to 
try and anticipate all the possible problems that might emerge from a given 
solution.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=279155721-13112001>And 
we already have requirements for maintaining security during 
CT.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>Finally, this is not DoD work: the requirements are not 
intended to be the utlimate,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>cast-in-titanium, truth about CT for all time. It 
should be reasonably complete, but</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=279155721-13112001>we 
must expect that we will discover more about the problem domain when 
we&nbsp;start</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>working on solutions. No one, as far as I have ever 
heard or experienced, has ever</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>succeed in doing a complete waterfall design for a 
system of any significant complexity</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=279155721-13112001>(I 
think the requirements document for the pet rock was never changed after 
approval).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>Just my delusional opinion.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=279155721-13112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 13, 2001 
  16:41<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; Shahrier, Sharif M.; 
  'Nakhjiri Madjid-MNAKHJI1'<BR><B>Cc:</B> 
  seamoby@cdma-2000.org<BR><B>Subject:</B> RE: [seamoby] Some proposed changes 
  to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P class=MsoNormal><FONT color=teal face="Times New Roman" size=3><SPAN 
  style="COLOR: teal; FONT-SIZE: 12pt">Gary,</SPAN></FONT><FONT color=teal><SPAN 
  style="COLOR: teal; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=teal face="Times New Roman" size=3><SPAN 
  style="COLOR: teal; FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT 
  color=teal><SPAN 
  style="COLOR: teal; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=teal face="Times New Roman" size=3><SPAN 
  style="COLOR: teal; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN></SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black">&nbsp;</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">If CT 
  failures, whether due to stale context or something else, creates security 
  problems, then</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">these need 
  to be addressed. But, we should wait until we understand the requirements for 
  security</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face="Comic Sans MS" size=3><SPAN 
  style="COLOR: blue; FONT-FAMILY: 'Comic Sans MS'; FONT-SIZE: 12pt">context 
  transfer, before we state requirements for solutions to speculated 
  problems.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><SPAN class=EmailStyle21><FONT color=teal face=Arial 
  size=2><SPAN 
  style="COLOR: teal; FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Are these types of problems outside the scope of the current CT 
  requirements draft?</SPAN></FONT></SPAN><SPAN class=EmailStyle21><FONT 
  color=teal face=Arial size=2><SPAN 
  style="COLOR: teal; FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-color-alt: windowtext; mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16C8E.88AE6190--


From owner-seamoby@diameter.org  Tue Nov 13 18:58:00 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21933
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 18:57:58 -0500 (EST)
Received: (qmail 15903 invoked by alias); 13 Nov 2001 23:26:27 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 15897 invoked by uid 200); 13 Nov 2001 23:26:27 -0000
Received: (qmail 15892 invoked by uid 500); 13 Nov 2001 23:26:25 -0000
Date: Tue, 13 Nov 2001 15:26:25 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011113152625.A15741@charizard.diameter.org>
Mail-Followup-To: Gary Kenward <gkenward@nortelnetworks.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	'Nakhjiri Madjid-MNAKHJI1' <Madjid.Nakhjiri@motorola.com>,
	seamoby@cdma-2000.org
References: <9FBD322B7824D511B36900508BF93C9C01AA463F@zcard031.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <9FBD322B7824D511B36900508BF93C9C01AA463F@zcard031.ca.nortel.com>; from gkenward@nortelnetworks.com on Tue, Nov 13, 2001 at 04:32:59PM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

I agree with Gary. We were here last year, and consensus was clear. I see no reason
to start this whole debacle over again.

PatC

On Tue, Nov 13, 2001 at 04:32:59PM -0500, Gary Kenward wrote:
> Sharif:
>  
> Sorry, but no, I do not agree. We had an extensive debate last spring over
> the role of the MN
> in CT, and (it is my understanding) that the MN should not, could not be
> required to participate 
> in CT. The rationale was that MN involvement would likely slow down the
> process, and thus,
> degrade the seamlessness.
>  
> CT is in support of seamless mobility (or at least, that's what I thought
> this was all about).
> If CT works, then the handover will be seamless. If, by exception, CT does
> not work, then
> seamlessness is lost and the service will degrade. What it degrades to is,
> IMHO, a policy 
> set by the operator (or a forced drop of all IP sessions due to the physics
> of the channel). 
> Having the MN authenticate the context does not improve seamlessness,
> indeed, it can only degrade it, as the authentication process implies over
> the air signalling,
> and significant additional delays. And, definitely, if CT fails - e.g. if
> the context has become
> "stale" for some reason, then authentication does not help maintain
> seamlessness. 
>  
> If CT failures, whether due to stale context or something else, creates
> security problems, then
> these need to be addressed. But, we should wait until we understand the
> requirements for security
> context transfer, before we state requirements for solutions to speculated
> problems.
>  
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 16:17
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; Kenward, Gary
> [WDLN2:AN10:EXCH]
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
> 
> 
> Majid,
>  
>             Consider the case where the context transfer occurs before
> handover. So, the context will arrive at the newAR before
>             The mobile node does. What if something goes wrong - the context
> is not correctly received by the newAR.
>             When the MN arrives at the newAR, it needs to know this fact.
> So, the MN should authenticate the received context, just
>             To make sure that its context was successfully received by the
> newAR.
>  
> -Sharif. 
>  
> Maybe you mean that the MN should authenticate the received context data,
> but
> then why does the MN should do this. The context is going to the new AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>  
> Why are we dragging MN into the authentication process.
>  
> these issues are attacking the basic framework of CT, IMHO
>  
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
> Gary,
>  
>                 Understood. However, the requirements contains nothing (?)
> about the mobile authenticating with its context, after the context 
> Has been transferred. 
>  
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature that its
> not authorized access to.
>  
> How about:
>  
>                 There MUST be mutual authentication between the MN and its
> context, after the context transfer has occurred.
>  
> -Sharif.
>  
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
>  
> Sharif:
>  
>   This requirement is for the ARs to authenticate each other so that a ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>  
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
>  
>  
> I have some issues with the following requirement in the CT draft.
>  
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>  
> I don't support this requirement.
>  
> It appears to me this may not fit the case for "break-before-make" handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP. 
>  
> Assuming that the context is transferred prior to re-establishing the new
> connection.
>  
> The mobile will need to re-authenticate after it makes a new connection at
> its new AP.
>  
> I have seen several practical cases that supports this scanario, thus I feel
> it is necessary for authentication after the transfer of context 
> in "break-before-make".
>  
> -Sharif.


From owner-seamoby@diameter.org  Tue Nov 13 19:01:36 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22014
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:01:35 -0500 (EST)
Received: (qmail 16041 invoked by alias); 13 Nov 2001 23:31:59 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 16035 invoked by uid 200); 13 Nov 2001 23:31:58 -0000
Received: (qmail 16029 invoked by uid 500); 13 Nov 2001 23:31:57 -0000
Date: Tue, 13 Nov 2001 15:31:57 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011113153157.B15741@charizard.diameter.org>
Mail-Followup-To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
	'Gary Kenward' <gkenward@nortelnetworks.com>,
	'Nakhjiri Madjid-MNAKHJI1' <Madjid.Nakhjiri@motorola.com>,
	seamoby@cdma-2000.org
References: <A1170612471BD21185B90008C7FA0A0D0327F99B@idcpa4.pa.interdigital.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <A1170612471BD21185B90008C7FA0A0D0327F99B@idcpa4.pa.interdigital.com>; from Sharif.Shahrier@InterDigital.com on Tue, Nov 13, 2001 at 04:41:25PM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

Sharif,

I don't think that we can expect to do protocol design through the
requirements phase. I am interested in protocol requirements, but
I don't think that we should start listing the various errors that protocols
need to deal with in the requirements document.

PatC
On Tue, Nov 13, 2001 at 04:41:25PM -0500, Shahrier, Sharif M. wrote:
> Gary,
>  
>              
> If CT failures, whether due to stale context or something else, creates
> security problems, then
> these need to be addressed. But, we should wait until we understand the
> requirements for security
> context transfer, before we state requirements for solutions to speculated
> problems.
>  
>             Are these types of problems outside the scope of the current CT
> requirements draft?
>  
> -Sharif.


From owner-seamoby@diameter.org  Tue Nov 13 19:04:17 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22117
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:04:15 -0500 (EST)
Received: (qmail 16280 invoked by alias); 13 Nov 2001 23:41:59 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 16273 invoked by uid 200); 13 Nov 2001 23:41:58 -0000
Received: (qmail 16265 invoked from network); 13 Nov 2001 23:41:54 -0000
Received: from wells.cisco.com (171.71.177.223)
  by c900656-a.plstn1.sfba.home.com with SMTP; 13 Nov 2001 23:41:54 -0000
Received: from JSCHNIZL-W2K1.cisco.com (rtp-vpn1-244.cisco.com [10.82.224.244]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA21872; Tue, 13 Nov 2001 14:52:02 -0800 (PST)
Message-Id: <4.3.2.7.2.20011113174639.037bc958@diablo.cisco.com>
X-Sender: jschnizl@diablo.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 13 Nov 2001 17:51:23 -0500
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
From: John Schnizlein <jschnizl@cisco.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Cc: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>, seamoby@cdma-2000.org
In-Reply-To: <A1170612471BD21185B90008C7FA0A0D0327F999@idcpa4.pa.interdi
 gital.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Color is not an appropriate way to indicate quoting of other's text
in an IETF WG. Recall that despite many efforts to change it, the 
rule for IETF work is plain text. I prefer to include European 
characters in this definition, but that is where the grey-area is.

Please behave!

At 04:17 PM 11/13/2001, Shahrier, Sharif M. wrote:

>Majid,
>
>            Consider the case where the context transfer occurs before handover. So, the context will arrive at the newAR before...
>-Sharif. 
>
>Maybe you mean that the MN should authenticate the received context data, but
>
>then why does the MN should do this. The context is going to the new AR, anyway.
>
>If authentication of data is needed, new AR does it on behalf of MN.
>Madjid
>
>-----Original Message-----
>From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
>Sent: Tuesday, November 13, 2001 10:44 AM
>To: 'Gary Kenward'; Shahrier, Sharif M.
>Cc: seamoby@cdma-2000.org
>Subject: RE: [seamoby] Some proposed changes to the requirements draft.
>               Understood. However, the requirements contains nothing (?) about the mobile authenticating with its context, after the context 
>
>Has been transferred. 
>
> 
>
>I think a requirement should be there for this, otherwise, without authentication, the MN can get at any context, or context feature that its not authorized access to.
>
>How about:
>
>                There MUST be mutual authentication between the MN and its context, after the context transfer has occurred.
>
>-Sharif.
>
>  This requirement is for the ARs to authenticate each other so that a ct exchange can
>
>be trusted. It has nothing to do with the MN and handoff per se.
>
>Gary
>n several practical cases that supports this scanario, thus I feel it is necessary for authentication after the transfer of context 
>
>in break-before-make .
>
> 
>
>-Sharif.



From owner-seamoby@diameter.org  Tue Nov 13 19:16:31 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22351
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:16:30 -0500 (EST)
Received: (qmail 20203 invoked by alias); 14 Nov 2001 01:03:06 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 20197 invoked by uid 200); 14 Nov 2001 01:03:06 -0000
Received: (qmail 20192 invoked from network); 14 Nov 2001 01:03:04 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:03:04 -0000
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate2.mot.com (motgate2 2.1) with ESMTP id RAA15792 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:14:18 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id RAA22370 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:14:17 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <4K0B0YX8>; Tue, 13 Nov 2001 18:14:17 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB19@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:14:12 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi,

We agreed long time ago and mentioned several times so far,
 context transfer is about transfer of the context (great sentence...),
 Not about storage or dump of context.
Where is it stored or dumped, do you have security for the storage,
or redundancy of storage or any other issues, is not part of scope.

Now going even further and making the storage hierarchical or localized
or globalized would even more....

Why are we reopening these issues?

Madjid

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, November 12, 2001 1:15 PM
To: 'James Kempf'; Shahrier, Sharif M.; seamoby@cdma-2000.org
Cc: Shahrier, Sharif M.
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hello James,


4.18 "The context transfer protocol MUST support both centralized and
distributed location of context information."

This requirement should be there so that there can be a "local" context
database (LCD)  within each AR. The LCD keeps a log of the context
parameters of every session that is currently active for the MN. 

In addition, there should be a "central"  context database (CCD). The CCD
keeps a log of all parameters that the MN is likely ever to need, whether or
not they are currently used.

Thus, LCD is a local cache memory and the CCD is a secondary storage memory.
New data in the LCD may replace that in the CCD using a write-through cache
coherency policy, whenever it needs to be updated.  When a new session
becomes active, the appropriate parameters may be read from the CCD to
replace the "unused" entries in the LCD.

The LCD is local to its AR, but the CCD is centralized and may be shared by
all the ARs.

This 2-level cache-main memory hierarchy will help reduce the size of the
LCD, and the CCD will help the context transfer itself, since it is
accessable by all the ARs.


jak> I don't understand this. What is this supposed to mean?

5.6.1 "The context transfer protocol MUST include methods for
interworking
with any IETF IP handover solutions".

5.6.2 "The context transfer solution MAY include methods for
interworking
with non-IETF handover solutions".
contexts or sub-divisions thereof".

jak> These two requirements assume that there will be only one context
transfer protocol for all application areas. I tend to believe that
there will be a set of protocols, some of which are tied directly to the
handover protocol, for better integration of those areas where timing
requirements are tightly tied to handover.

Note, Iuse the word "interworking" and not "independance". I feel that it is
better come up with a single context transfer solution that meets all the
"worst-case" handover scanarios, because otherwise we may end up
standardizing many  different context transfer protocols; each to meet a
specific handover specification, possibly leading to interworking problems,
amongst other things. 

As far as the scope of the problem SEAMOBY assigned to us, I believe, should
be to come up with a single context transfer protocol.

Did you have any comments to my other requirements?

-Sharif


From owner-seamoby@diameter.org  Tue Nov 13 19:19:41 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22382
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:19:38 -0500 (EST)
Received: (qmail 20583 invoked by alias); 14 Nov 2001 01:05:29 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 20576 invoked by uid 200); 14 Nov 2001 01:05:28 -0000
Received: (qmail 20565 invoked from network); 14 Nov 2001 01:05:25 -0000
Received: from motgate3.mot.com (144.189.100.103)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:05:25 -0000
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate3.mot.com (motgate3 2.1) with ESMTP id RAA16530 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:08:24 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id RAA25068 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:17:32 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4ABJ>; Tue, 13 Nov 2001 18:17:32 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB1A@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:17:24 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

<snip > 


>     Any application area that utilizes the context transfer protocol 
> MUST define a standard representation 
>     for conveying context information. 


The wording may need to be fixed, but the requirement is not as you 
are both interpreting it. The "standard representation" 
referred to is the representation of the data chunks, or objects, 
in the context transfer protocol that are used to contain the context. 
The actual context is encapsulated within these data chunks, and the 
representation of that context is opaque to context transfer. What is 
needed is a standard representation for these containers. 

Madjid>> I think, what I all along thought was we define a generic
format for the data and the packets regardless of the type of feature.
See our TEXT draft or Rajeev/ Charlie's draft as examples.

Madjid 


From owner-seamoby@diameter.org  Tue Nov 13 19:25:52 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22589
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:25:36 -0500 (EST)
Received: (qmail 21158 invoked by alias); 14 Nov 2001 01:08:29 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21152 invoked by uid 200); 14 Nov 2001 01:08:28 -0000
Received: (qmail 21137 invoked from network); 14 Nov 2001 01:08:25 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:08:25 -0000
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id RAA18354 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:20:32 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id RAA18757 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:20:32 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4AC7>; Tue, 13 Nov 2001 18:20:32 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB1B@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        seamoby <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:20:28 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16CA2.29D792E0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16CA2.29D792E0
Content-Type: text/plain;
	charset="iso-8859-1"

I agree, you need to specify for the receiving AR and the protocol unit
inside of it
how to parse context data for various features and how to ask to
retransmissions or
updates if necessary. 
 
If we start by saying we don't even want to define a packet format for CT,
then why
are we working on the CT protocol standard, let every technology/ system/
feature
do its own thing??
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Monday, November 12, 2001 3:58 PM
To: 'Shahrier, Sharif M.'; 'James Kempf'; seamoby
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Sharif:
 
The thought was that the payload would be comprised of one or more of these
"chunks", each one representing a different feature context. The container
format would have to at least to provide a type field (where the type would
indicate the feature the context belonged to, but would be simply be used by
the
receiving AR to dispatch the container content to the appropriate entity),
and, a length field. There may be more to the container format, but nothing 
comes to mind.
 
Of course, the actually container representation is still to be determined.
The requirement states only that a representation must be defined.
 
There are plenty of analogies in other IETF protocols for this mechanism for
conveying pieces of similar but different data in one IP payload.
 
Gary
 
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 12, 2001 15:50
To: Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; Shahrier, Sharif M.;
seamoby
Cc: Shahrier, Sharif M.
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Gary,
> 
>     Any application area that utilizes the context transfer protocol 
> MUST define a standard representation 
>     for conveying context information. 
The wording may need to be fixed, but the requirement is not as you 
are both interpreting it. The "standard representation" 
referred to is the representation of the data chunks, or objects, 
in the context transfer protocol that are used to contain the context. 
The actual context is encapsulated within these data chunks, and the 
representation of that context is opaque to context transfer. What is 


I was not involved with the earlier drafting of this requirement. Could you
please explain why it's necessary
To define representation of data chunks for encapsulating the context?
I would prefer to just send the context information as part of the DATA
SEGMENT in a regular IP datagram, without any form
Of encapsulation .
-Sharif.
                                      

------_=_NextPart_001_01C16CA2.29D792E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16B92.656E9DF0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle19 {
	COLOR: navy; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue =
link=3Dblue>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
agree, you need to specify for the receiving AR and the protocol unit =
inside of=20
it</FONT></SPAN></DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>how to=20
parse context data for various features and how to ask to =
retransmissions=20
or</FONT></SPAN></DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>updates if necessary. </FONT></SPAN></DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>If we=20
start by saying we don't even want to define a packet format for CT, =
then=20
why</FONT></SPAN></DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>are we=20
working on the CT protocol standard, let every technology/ system/=20
feature</FONT></SPAN></DIV>
<DIV><SPAN class=3D700121800-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>do its=20
own thing??</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Gary Kenward=20
  [mailto:gkenward@nortelnetworks.com]<BR><B>Sent:</B> Monday, November =
12, 2001=20
  3:58 PM<BR><B>To:</B> 'Shahrier, Sharif M.'; 'James Kempf';=20
  seamoby<BR><B>Subject:</B> RE: [seamoby] Some proposed changes to the =

  requirements draft.<BR><BR></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>Sharif:</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>The&nbsp;thought was that the payload =
would be=20
  comprised of one or more of these</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>"chunks", each one representing a =
different feature=20
  context. The container</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>format would have to at least to provide a =
type field=20
  (where the type would</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>indicate the feature the context belonged =
to, but=20
  would be&nbsp;simply be used by the</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>receiving AR to dispatch the container =
content to the=20
  appropriate entity),</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>and, a length field. There may be more to =
the=20
  container format, but nothing </SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>comes to mind.</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>Of course, the actually container =
representation is=20
  still to be determined.</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>The requirement states only that a =
representation=20
  must be defined.</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>There are plenty of analogies in other =
IETF protocols=20
  for this mechanism for</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>conveying pieces of similar but different =
data in one=20
  IP payload.</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001>Gary</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff><SPAN=20
  class=3D788375621-12112001></SPAN></FONT>&nbsp;</DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, =
Sharif M.=20
    [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November =
12, 2001=20
    15:50<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]; 'James Kempf'; =

    Shahrier, Sharif M.; seamoby<BR><B>Cc:</B> Shahrier, Sharif=20
    M.<BR><B>Subject:</B> RE: [seamoby] Some proposed changes to the=20
    requirements draft.<BR><BR></DIV></FONT>
    <DIV class=3DSection1>
    <P><FONT face=3D"Times New Roman" color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy">Gary,</SPAN></FONT><FONT =
color=3Dnavy=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">&gt; </SPAN></FONT><FONT=20
    color=3Dblack><SPAN style=3D"COLOR: black"><BR></SPAN></FONT><FONT =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: =
black">&gt;&nbsp;&nbsp;&nbsp;&nbsp; Any=20
    application area that utilizes the context transfer=20
    protocol</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: =
black">=20
    <BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">&gt; MUST define a standard =

    representation</SPAN></FONT><FONT color=3Dblack><SPAN =
style=3D"COLOR: black">=20
    <BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: =
black">&gt;&nbsp;&nbsp;&nbsp;&nbsp; for=20
    conveying context information.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black"> </SPAN></FONT><FONT color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P style=3D"tab-stops: 112.5pt"><FONT face=3D"Times New Roman" =
color=3Dblack=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black">The wording =
may need to=20
    be fixed, but the requirement is not as you</SPAN></FONT><FONT=20
    color=3Dblack><SPAN style=3D"COLOR: black"> <BR></SPAN></FONT><FONT =
color=3Dblack=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black">are both =
interpreting it.=20
    The "standard representation"</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">referred to is the =
representation of=20
    the data chunks, or objects,</SPAN></FONT><FONT color=3Dblack><SPAN =

    style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">in the context transfer =
protocol that=20
    are used to contain the context.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">The actual context is =
encapsulated=20
    within these data chunks, and the </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black"><BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black">representation of that =
context is=20
    opaque to context transfer. What is</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black"> <BR style=3D"mso-special-character: =
line-break"><![if !supportLineBreakNewLine]><BR=20
    style=3D"mso-special-character: =
line-break"><![endif]></SPAN></FONT><FONT=20
    color=3Dnavy><SPAN=20
    style=3D"COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P style=3D"tab-stops: 112.5pt"><SPAN class=3DEmailStyle19><FONT =
face=3DArial=20
    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
    was not involved with the earlier drafting of this requirement. =
Could you=20
    please explain why it&#8217;s =
necessary<o:p></o:p></SPAN></FONT></SPAN></P>
    <P style=3D"tab-stops: 112.5pt"><SPAN class=3DEmailStyle19><FONT =
face=3DArial=20
    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">To=20
    define representation of data chunks for encapsulating the=20
    context?<o:p></o:p></SPAN></FONT></SPAN></P>
    <P style=3D"tab-stops: 112.5pt"><SPAN class=3DEmailStyle19><FONT =
face=3DArial=20
    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
    would prefer to just send the context information as part of the =
DATA=20
    SEGMENT in a regular IP datagram, without any=20
    form<o:p></o:p></SPAN></FONT></SPAN></P>
    <P style=3D"tab-stops: 112.5pt"><SPAN class=3DEmailStyle19><FONT =
face=3DArial=20
    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Of=20
    encapsulation .<o:p></o:p></SPAN></FONT></SPAN></P>
    <P style=3D"tab-stops: 112.5pt"><SPAN class=3DEmailStyle19><FONT =
face=3DArial=20
    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P style=3D"tab-stops: 112.5pt"><FONT face=3D"Times New Roman" =
color=3Dnavy=20
    size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: navy"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    </SPAN></SPAN></FONT><FONT color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BODY></HTML>

------_=_NextPart_001_01C16CA2.29D792E0--


From owner-seamoby@diameter.org  Tue Nov 13 19:35:36 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22874
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:35:35 -0500 (EST)
Received: (qmail 21376 invoked by alias); 14 Nov 2001 01:10:57 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21369 invoked by uid 200); 14 Nov 2001 01:10:57 -0000
Received: (qmail 21361 invoked from network); 14 Nov 2001 01:10:53 -0000
Received: from motgate3.mot.com (144.189.100.103)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:10:53 -0000
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate3.mot.com (motgate3 2.1) with ESMTP id RAA18797 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:13:50 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id RAA25329 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:22:58 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <4K0B0Y7N>; Tue, 13 Nov 2001 18:22:57 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB1C@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:22:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

can we not use the word "encapsulating" context information, it
could be inpreted as tunneling, or maybe I am paranoid :)

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Monday, November 12, 2001 7:17 PM
To: Gary Kenward; Shahrier, Sharif M.; seamoby
Cc: Shahrier, Sharif M.
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


Gary,

> The wording may need to be fixed, but the requirement is not as you
> are both interpreting it. The "standard representation"
> referred to is the representation of the data chunks, or objects,
> in the context transfer protocol that are used to contain the context.
> The actual context is encapsulated within these data chunks, and the
> representation of that context is opaque to context transfer. What is
> needed is a standard representation for these containers.
>
> The words do say "a standard representation for *conveying*"; the
> key words are "for conveying". They do not say "a standard
representation
> for the context" which is how you are both interpreting the
requirement.
>
> Again, we can clarify the wording, but the requirement still makes
sense.
> As for James proposal, this would be a new requirement.
>

I misunderstood the requirement. I think you need to reword it to avoid
the possibility of misunderstanding. How about:

    The context transfer protocol MUST define a standardized container
    format for encapsulating and conveying context information.
Interpretation
    of the context information within the container is the domain of the
application
    for which context is being transfered. Applications SHOULD define an
interoperable
    format for context information if they want to use the context
transfer protocol.

Or, you can simply include the first sentence if you feel that the rest
is too controversial
or would expand the requirement beyond what is currently agreed.

            jak


From owner-seamoby@diameter.org  Tue Nov 13 19:38:22 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22956
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:38:18 -0500 (EST)
Received: (qmail 21573 invoked by alias); 14 Nov 2001 01:15:00 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21566 invoked by uid 200); 14 Nov 2001 01:14:59 -0000
Received: (qmail 21558 invoked from network); 14 Nov 2001 01:14:56 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:14:56 -0000
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id RAA21358 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:27:00 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id RAA22178 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:27:00 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8MPRW>; Tue, 13 Nov 2001 18:27:00 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB1D@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
        seamoby@cdma-2000.org
Cc: Sharif.Shahrier@InterDigital.com
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:26:58 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

John, others:

The centralized approach to context transfer was dismissed
very early on. Is this still an issues?

Something like 5.6.1 is included, don't remember if it says
"any" IETF protocols or not.

For 5.6.2 I am not quite sure if some non-IETF protocols even
have the same definition for context as we do (PDP context is one
example), any idea??

Madjid

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Tuesday, November 13, 2001 1:22 AM
To: kempf@docomolabs-usa.com; Sharif.Shahrier@InterDigital.com;
seamoby@cdma-2000.org
Cc: Sharif.Shahrier@InterDigital.com
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hi James,

> Comments included, marked with jak>.
> 
> Section 5.1.2 "The context transfer protocol MUST define a stanard
> representation for coveying context information that will be 
> interpreted
> uniformly and perspicuously by different implementations"
> 
> I would like this to be deleted, because it has nothing to do with the
> actual "transfer" of the context.
> 
> jak> Agreed. This requirement is in the domain of the individual
> applications that use the protocol. Perhaps
> it should say:
> 
>     Any application area that utilizes the context transfer protocol
>     MUST define a standard representation for conveying context 
>     information.

I agree, but SHOULD might be more applicable than MUST, as I 
see this as more of a recommendation as opposed to an 
absolute requirement.

Then a general comment on Sharif's proposals:

> 4.18 "The context transfer protocol MUST support both centralized and
> distributed location of context information."
> 
> 5.6.1 "The context transfer protocol MUST include methods for
> interworking with any IETF IP handover solutions".
> 
> 5.6.2 "The context transfer solution MAY include methods for
> interworking with non-IETF handover solutions".
> contexts or sub-divisions thereof".

Unless we have a reason why these are requirements,
I don't think we can support adding these into the document.

br,
John


From owner-seamoby@diameter.org  Tue Nov 13 19:41:06 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23016
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:41:06 -0500 (EST)
Received: (qmail 21709 invoked by alias); 14 Nov 2001 01:18:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21703 invoked by uid 200); 14 Nov 2001 01:18:10 -0000
Received: (qmail 21696 invoked from network); 14 Nov 2001 01:18:05 -0000
Received: from motgate.mot.com (129.188.136.100)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:18:05 -0000
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate.mot.com (motgate 2.1) with ESMTP id RAA02776 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:30:01 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id RAA00965 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:30:00 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8MPTP>; Tue, 13 Nov 2001 18:30:00 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB1E@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Sharif.Shahrier@InterDigital.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:29:59 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Agree with John,

4.16 and 4.17 don't add any value, seems like we are turning
the clock back to April 2001????

Agree with John on 4.18 and the last 3.


-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Tuesday, November 13, 2001 3:58 AM
To: Sharif.Shahrier@InterDigital.com; seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hi Sharif,

My comments, inline:

> Next, I would like to following additional requirements in the CT 
> requirements draft.

> 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> scalable to millions of hosts".

This is 'motherhood & apple pie' text (i.e. - noone would really
disagree). I don't know how this adds anything to the text.  
Additionally, I would suggest SHOULD rather than MUST is
what you mean.

> 4.17 "The context transfer protocol MUST minimize the number of 
> signaling messages at the sending and receiving Access Routers".

I don't see the need for this.  I don't think this should be
a requirement.

> 4.18 "The context transfer protocol MUST support both centralized 
> and distributed location of context information."

I don't think that there is any concensus for this kind of 
requirement to be added.

> 5.6.1 "The context transfer protocol MUST include methods for 
> interworking with any IETF IP handover solutions".
>
> 5.6.2 "The context transfer solution MAY include methods for 
> interworking with non-IETF handover solutions".
>
> 5.1.6 "The context transfer protocol MUST provide mechanisms for 
> sharing contexts or sub-divisions thereof".

I don't agree that the last 3 should be added.

John


From owner-seamoby@diameter.org  Tue Nov 13 19:52:33 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23267
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 19:52:09 -0500 (EST)
Received: (qmail 23232 invoked by alias); 14 Nov 2001 01:29:44 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 23224 invoked by uid 200); 14 Nov 2001 01:29:43 -0000
Received: (qmail 23203 invoked from network); 14 Nov 2001 01:29:39 -0000
Received: from ftpbox.mot.com (129.188.136.101)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 01:29:39 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id RAA08591 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:41:45 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id RAA08047 for <seamoby@cdma-2000.org>; Tue, 13 Nov 2001 17:32:08 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4AM7>; Tue, 13 Nov 2001 18:41:44 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB20@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Tue, 13 Nov 2001 18:41:41 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16CA5.20546510"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16CA5.20546510
Content-Type: text/plain;
	charset="iso-8859-1"

Sherif,
 
First I think the chairs closed this thread. Authentication has to happen
between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context
reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed
authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open
issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once
for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT
data can be
authenticated if necessary. The receiving AR, will check the authentication
of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that
only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16CA5.20546510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16C5F.71909C00" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle20 {
	COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle21 {
	COLOR: #993366; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle22 {
	COLOR: #003300; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle23 {
	COLOR: olive; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue =
link=3Dblue>
<DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Sherif,</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>First=20
I think the chairs closed this thread. Authentication has to happen =
between ARs,=20
since</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>CT=20
happens between ARs. If the MN was supposed to be involved in context=20
reestablishment,</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>we=20
wouldn't be here in the first place.</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Second, there are a lot of things that can go wrong with CT, =
and failed=20
authentication is one</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>of=20
them. Reliability for CT and the backup mechanisms for CT are still =
open issues,=20
but for sure</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>a=20
failed authentication at MN is not one of these issues and here is=20
why:</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>after=20
the two ARs have authenticated themselves to each other (maybe once for =
all or=20
maybe</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>before=20
a CT, I don't inject my opinion here), then they engage in CT. The CT =
data can=20
be</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>authenticated if necessary. The receiving AR, will check the=20
authentication of context data.</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Architecture-wise, this is the only way to do it,&nbsp; based =
on the fact=20
that only ARs do CT.</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>And MN=20
is not in this picture.</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>Hope=20
this clears things out.</FONT></SPAN></DIV>
<DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Madjid</FONT></SPAN></DIV></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif =
M.=20
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> Tuesday, =
November=20
  13, 2001 3:17 PM<BR><B>To:</B> 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, =
Sharif=20
  M.; 'Gary Kenward'<BR><B>Cc:</B> =
seamoby@cdma-2000.org<BR><B>Subject:</B> RE:=20
  [seamoby] Some proposed changes to the requirements=20
draft.<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Consider the case where the context transfer occurs before =
handover.=20
  So, the context will arrive at the newAR before</SPAN></FONT><FONT=20
  color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>The mobile node does. What if something goes wrong &#8211; the =
context is not=20
  correctly received by the newAR.</SPAN></FONT><FONT =
color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>When the MN arrives at the newAR, it needs to know this fact. =
So, the=20
  MN should authenticate the received context, just</SPAN></FONT><FONT=20
  color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>To make sure that its context was successfully received by the =

  newAR.</SPAN></FONT><FONT color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
  color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive">-Sharif.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dolive><SPAN=20
  style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Maybe you =
mean that=20
  the MN should authenticate the received context data, =
but</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">then why =
does the MN=20
  should do this. The context is going to the new AR, =
anyway.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If =
authentication of=20
  data is needed, new AR does it on behalf of MN.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Why are we =
dragging=20
  MN into the authentication process.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">these =
issues are=20
  attacking the basic framework of CT, IMHO</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Madjid</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; mso-margin-top-alt: =
auto"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 10:44=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Gary =
Kenward';=20
  Shahrier, Sharif M.<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Cc:</SPAN></B>=20
  seamoby@cdma-2000.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Understood. However, the requirements contains nothing (?) =
about the=20
  mobile authenticating with its context, after the context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">Has=20
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">I=20
  think a requirement should be there for this, otherwise, without=20
  authentication, the MN can &#8220;get at&#8221; any context, or =
context feature that its=20
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">How=20
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><B><SPAN style=3D"FONT-WEIGHT: bold">There MUST be mutual =
authentication=20
  between the MN and its context, after the context transfer has=20
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN=20
  class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN=20
  class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3DArial color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Gary=20
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 11:07=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, =
Sharif=20
  M.'<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
  'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sharif:</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;=20
  This requirement is for the ARs to authenticate each other so that a =
ct=20
  exchange can</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">be=20
  trusted. It has nothing to do with the MN and handoff per=20
  se.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Gary</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; MARGIN-BOTTOM: 12pt; PADDING-BOTTOM: =
0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none; mso-margin-top-alt: auto; =
mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in =
4.0pt"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 =
09:51<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif =
M.<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3D#993366 size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: #993366">I have some issues with the =
following=20
  requirement in the CT draft.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">4.9=20
  The entities transferring context MUST have completed a mutual =
authentication=20
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>initiating the=20
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
  don&#8217;t support this requirement.<o:p></o:p></SPAN></FONT></SPAN><=
/P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">It=20
  appears to me this may not fit the case for =
&#8220;break-before-make&#8221; handover=20
  .<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For instance, the =
mobile may=20
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">AP,=20
  and re-establish connection with the new AP.=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Assuming=20
  that the context is transferred prior to re-establishing the new=20
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">The=20
  mobile will need to re-authenticate after it makes a new connection =
at its new=20
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I have=20
  seen several practical cases that supports this scanario, thus I feel =
it is=20
  necessary for authentication after the transfer of context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">in=20
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQ=
UOTE></BODY></HTML>

------_=_NextPart_001_01C16CA5.20546510--


From owner-seamoby@diameter.org  Tue Nov 13 22:20:21 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26289
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 22:20:21 -0500 (EST)
Received: (qmail 24432 invoked by alias); 14 Nov 2001 04:07:15 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 24426 invoked by uid 200); 14 Nov 2001 04:07:14 -0000
Received: (qmail 24417 invoked by uid 500); 14 Nov 2001 04:07:12 -0000
Date: Tue, 13 Nov 2001 20:07:12 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>, seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011113200712.G24140@charizard.diameter.org>
Mail-Followup-To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	'James Kempf' <kempf@docomolabs-usa.com>, seamoby@cdma-2000.org
References: <35DBB8B7AC89D4118E98009027B1009B0464FB19@IL27EXM10.cig.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B0464FB19@IL27EXM10.cig.mot.com>; from Madjid.Nakhjiri@motorola.com on Tue, Nov 13, 2001 at 06:14:12PM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

> We agreed long time ago and mentioned several times so far,
>  context transfer is about transfer of the context (great sentence...),
>  Not about storage or dump of context.
> Where is it stored or dumped, do you have security for the storage,
> or redundancy of storage or any other issues, is not part of scope.
> 
> Now going even further and making the storage hierarchical or localized
> or globalized would even more....
> 
> Why are we reopening these issues?

We are not. Sharif brought up the issue, and we are simply informing
him that we have WG concensus, and will not start over from scratch.

PatC


From owner-seamoby@diameter.org  Tue Nov 13 22:22:57 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26321
	for <seamoby-archive@odin.ietf.org>; Tue, 13 Nov 2001 22:22:56 -0500 (EST)
Received: (qmail 24708 invoked by alias); 14 Nov 2001 04:08:26 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 24701 invoked by uid 200); 14 Nov 2001 04:08:26 -0000
Received: (qmail 24684 invoked by uid 500); 14 Nov 2001 04:08:22 -0000
Date: Tue, 13 Nov 2001 20:08:22 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011113200822.H24140@charizard.diameter.org>
Mail-Followup-To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
	"'john.loughney@nokia.com'" <john.loughney@nokia.com>,
	kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
	seamoby@cdma-2000.org
References: <35DBB8B7AC89D4118E98009027B1009B0464FB1D@IL27EXM10.cig.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B0464FB1D@IL27EXM10.cig.mot.com>; from Madjid.Nakhjiri@motorola.com on Tue, Nov 13, 2001 at 06:26:58PM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

You are correct that centralized state did not have rough consensus. The
archives do show this.

PatC
On Tue, Nov 13, 2001 at 06:26:58PM -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> John, others:
> 
> The centralized approach to context transfer was dismissed
> very early on. Is this still an issues?
> 
> Something like 5.6.1 is included, don't remember if it says
> "any" IETF protocols or not.
> 
> For 5.6.2 I am not quite sure if some non-IETF protocols even
> have the same definition for context as we do (PDP context is one
> example), any idea??
> 
> Madjid
> 
> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Tuesday, November 13, 2001 1:22 AM
> To: kempf@docomolabs-usa.com; Sharif.Shahrier@InterDigital.com;
> seamoby@cdma-2000.org
> Cc: Sharif.Shahrier@InterDigital.com
> Subject: RE: [seamoby] Some proposed changes to the requirements draft.
> 
> 
> Hi James,
> 
> > Comments included, marked with jak>.
> > 
> > Section 5.1.2 "The context transfer protocol MUST define a stanard
> > representation for coveying context information that will be 
> > interpreted
> > uniformly and perspicuously by different implementations"
> > 
> > I would like this to be deleted, because it has nothing to do with the
> > actual "transfer" of the context.
> > 
> > jak> Agreed. This requirement is in the domain of the individual
> > applications that use the protocol. Perhaps
> > it should say:
> > 
> >     Any application area that utilizes the context transfer protocol
> >     MUST define a standard representation for conveying context 
> >     information.
> 
> I agree, but SHOULD might be more applicable than MUST, as I 
> see this as more of a recommendation as opposed to an 
> absolute requirement.
> 
> Then a general comment on Sharif's proposals:
> 
> > 4.18 "The context transfer protocol MUST support both centralized and
> > distributed location of context information."
> > 
> > 5.6.1 "The context transfer protocol MUST include methods for
> > interworking with any IETF IP handover solutions".
> > 
> > 5.6.2 "The context transfer solution MAY include methods for
> > interworking with non-IETF handover solutions".
> > contexts or sub-divisions thereof".
> 
> Unless we have a reason why these are requirements,
> I don't think we can support adding these into the document.
> 
> br,
> John


From owner-seamoby@diameter.org  Wed Nov 14 01:42:49 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04624
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 01:42:48 -0500 (EST)
Received: (qmail 26746 invoked by alias); 14 Nov 2001 07:29:48 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26740 invoked by uid 200); 14 Nov 2001 07:29:48 -0000
Received: (qmail 26735 invoked from network); 14 Nov 2001 07:29:45 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 07:29:45 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAE6gVA28481
	for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 08:42:31 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57366da5d3ac158f23076@esvir03nok.nokia.com>;
 Wed, 14 Nov 2001 08:41:50 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWVBDK>; Wed, 14 Nov 2001 08:41:50 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D904E@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: Madjid.Nakhjiri@motorola.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 08:41:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Madjid,

> The centralized approach to context transfer was dismissed
> very early on. Is this still an issues?

I don't think so.  However, if someone wants to invent
a way to do context transfer via a centralized server,
they can ... I don't think that any changes are needed
to the draft.

> Something like 5.6.1 is included, don't remember if it says
> "any" IETF protocols or not.
> 
> For 5.6.2 I am not quite sure if some non-IETF protocols even
> have the same definition for context as we do (PDP context is one
> example), any idea??

I imagine something could be invented ...

John


From owner-seamoby@diameter.org  Wed Nov 14 01:45:13 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04952
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 01:45:13 -0500 (EST)
Received: (qmail 27104 invoked by alias); 14 Nov 2001 07:31:34 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27098 invoked by uid 200); 14 Nov 2001 07:31:34 -0000
Received: (qmail 27082 invoked from network); 14 Nov 2001 07:31:31 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 07:31:31 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAE6iIA29359
	for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 08:44:18 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57366f423dac158f23076@esvir03nok.nokia.com>;
 Wed, 14 Nov 2001 08:43:35 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWVBFM>; Wed, 14 Nov 2001 08:43:26 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D904F@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: Madjid.Nakhjiri@motorola.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 08:43:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi,

> can we not use the word "encapsulating" context information, it
> could be inpreted as tunneling, or maybe I am paranoid :)

Agreed, so the text could be:

 The context transfer protocol MUST define a standardized container
 format for conveying context information. Interpretation
 of the context information within the container is the domain of the
 application for which context is being transfered. Applications 
 SHOULD define an interoperable format for context information if they 
 want to use the context transfer protocol.

John


From owner-seamoby@diameter.org  Wed Nov 14 02:41:41 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15595
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 02:41:27 -0500 (EST)
Received: (qmail 28154 invoked by alias); 14 Nov 2001 08:22:16 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28148 invoked by uid 200); 14 Nov 2001 08:22:16 -0000
Received: (qmail 28142 invoked from network); 14 Nov 2001 08:22:12 -0000
Received: from 217.134.88.213.host.tele1europe.se (HELO mailgw.ipunplugged.com) (@213.88.134.217)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 08:22:12 -0000
Received: from chardonnay (sparcis.ipunplugged.com [10.0.1.163])
	by mailgw.ipunplugged.com (8.9.3/8.9.3) with ESMTP id IAA16851
	for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 08:33:55 +0100
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 08:34:16 +0100
Message-ID: <GMEEKDGLAJJFGAFEMMPICELOCKAA.henrik@levkowetz.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00E7_01C16CE7.25932510"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3BF192D5.C654DAF@iprg.nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00E7_01C16CE7.25932510
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

No, it is not a given that there's a requirement that the protocol MUST be
scalable to millions
of hosts. It SHOULD be scalable to the number of hosts that a MN may
reasonably have as
candidate access routers for a handover. And I believe that's reasonably
well covered in the
draft, even if it's not explicit and by numbers.

 And no, we MUST NOT have an extensive discussion about the formulation of
this point.
 I think, from the start we've been over this a number of times; so to put
it bluntly, have those
that advocate changes to the draft now have a tangible project with a need
for this protocol,
which would NOT be catered to with the current requirements - if we can ever
get this thing to fly?

The matter of authentication was up earlier; now consider this: If you
require strong mutual
authentication and scalability to a MILLIONS of hosts, you are talking about
MILLIONS
SQUARED number of pairwise security associations. To no tangible use. Until
we get teleportation,
that is, and can go to the neighbourhood of any access router on the earth
instantly.

Please, can we drop this?

    Henrik

  -----Original Message-----
  From: owner-seamoby@diameter.org [mailto:owner-seamoby@diameter.org]On
Behalf Of Cedric Westphal
  Sent: Tuesday, November 13, 2001 10:38 PM
  To: Gary Kenward
  Cc: 'Shahrier, Sharif M.'; seamoby@cdma-2000.org
  Subject: Re: [seamoby] Some proposed changes to the requirements draft.


  Gary, Sharif, John,
  if the requirement is a given, then let's not argue about/against it. It
cannot
  hurt to include it, and _technically_ there is consensus for it.

  As far as how to phrase it, usually scalability is described as the
marginal increase
  in complexity induced by adding users. So something along the lines:
  the processing complexity at each AR (and the burden on the wired network)
  SHOULD increase linearly with the number of MNs or the number of CT
requests.

  Also, you can check conformance there.

  Cedric.





  Gary Kenward wrote:

    Sharif:
      -----Original Message-----
      From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
      Sent: November 13, 2001 11:29
      To: Kenward, Gary [WDLN2:AN10:EXCH]; 'john.loughney@nokia.com';
Shahrier, Sharif M.; seamoby@cdma-2000.org
      Subject: RE: [seamoby] Some proposed changes to the requirements
draft.

      Gary,
      >
      > > 4.16 "The context transfer protocol MUST be scalable. It MUST be
      > > scalable to millions of hosts".
      >
      > This is 'motherhood & apple pie' text (i.e. - noone would really
      > disagree). I don't know how this adds anything to the text.
      > Additionally, I would suggest SHOULD rather than MUST is
      > what you mean.
      >

      Myself, I do not know what "scaleable to millions of hosts"
      really means. If the concern is in regards to the ability for the
context
      transfer solution to support a real wireless mobile network and one of
the
      constraining factors is the number of ct's that can be handled per
time period,
      then both the number of terminals *and* the number of handoffs per
time period
      are at issue (is trivial to say that any ct solution can handle an
infinite number
      of terminals if the handoff rate is zero

      I agree with this. Number of cts handled per time period and the
number of handoffs per time

      Period are both good cases to support the scalability requirement. The
other point is the quantity of context information

      Being transferred for each mobile over a given time. This bandwidth
must be scalable.

      It is not clear to me how we would define the scaleability of ct in
any real
      terms. We know that it must be applicable to within an administrative
domain,
      and thus, the top limit would be the IP address space, but that is a
greatest
      upper bound and not very useful. Usually, in these situations, people
resort
      to rate of complexity measures to define scaleability.

      I agree that the scalability of the CT must be applicabile within an
administrative domain; scalability must also

      Be applicable across different operator networks as well.

      I dont see how the IPv4 address space affects the scalability of CT.
Could you please explain?
      [gwk] I doesn't, other then it puts "a" limit on the possible number
of mobiles within an
      administrative domain. An very high limit. Even higher if the domain
uses IPv6.

      Finally, scaleability is desireable, as long as the requirement is for
scaleability
      at an acceptable cost.

      Other then this, I do not know how one would word a requirement around
scaleability
      other then the motherhood of "ct must be scaleable at an acceptable
cost".

      I agree. Perhaps something like:

      4.16 The context transfer protocol MUST be scalable at an acceptable
cost.

      The context transfer protocol MUST be ale to handle a large number of
of context transfers per second, and MUST

      Be able to support a large number of handoffs per second. The quantity
of context information being transferred for each

      Mobile per second MUST be scalable, i.e. the bandwidth of the context
transfer MUST be scalable.

      The context transfers MAY be within the same administrative domain, or
they MAY be across different

      administrative domains.
      [gwk] This is actually 7 requirements. And, there is no way to ensure
conformance to  a number of them
      as written. While there are requirements in the existing draft that
will be difficult to ensure conformance, the wg
      has made an effort to stay away from requirements which could not be
tested (e.g. there is no "ct must be fast"
      requirement).

      My personal opinion is in line with what John stated, that scalability
is a given. Arguably, many stated requirements
      are "givens", but are stated for reinforcement. On the other hand,
many givens are not stated as requirements simply to
      keep the number of requirements and the scope of the document to a
manageable level. I would put "saleability" in
      the latter category, particularly with all the caveats that must go
along with any saleability requirement for ct.

      I hope this helps.
      Gary


------=_NextPart_000_00E7_01C16CE7.25932510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR></HEAD>
<BODY lang=3DEN-US link=3D#0000ff style=3D"tab-interval: .5in" =
vLink=3D#0000ff>
<DIV><FONT color=3D#0000ff face=3DGaramond>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>No, it is=20
not a given that there's a requirement that the protocol MUST be =
scalable to=20
millions</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>of hosts.=20
It SHOULD be scalable to the number of hosts that a MN may reasonably =
have=20
as</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>candidate=20
access routers for a handover. And I believe that's reasonably well =
covered in=20
the</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>draft,=20
even if it's not explicit and by numbers.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>&nbsp;And=20
no, we MUST NOT have an extensive discussion </SPAN></FONT><FONT =
color=3D#0000ff=20
face=3DGaramond><SPAN class=3D022064423-13112001>about the formulation =
of this=20
point.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>&nbsp;I=20
think, from the start we've been over this a number of =
</SPAN></FONT><FONT=20
color=3D#0000ff face=3DGaramond><SPAN class=3D022064423-13112001>times; =
so to put it=20
bluntly, have those </SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>that=20
advocate changes to the draft now have a tangible project with a need =
for this=20
protocol,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>which=20
would NOT be catered to with the current requirements -&nbsp;if we can=20
<STRONG>ever </STRONG>get this thing to fly?</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>The matter=20
of authentication was up earlier; now consider this: If you require =
strong=20
mutual</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001>authentication and scalability to a MILLIONS =
of hosts,=20
you are talking about MILLIONS</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>SQUARED=20
number of pairwise security associations. To no tangible use. Until we =
get=20
teleportation,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>that is,=20
and can go to the neighbourhood of any access router on the earth=20
instantly.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN =
class=3D022064423-13112001>Please,=20
can we drop this?</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001>&nbsp;&nbsp;&nbsp; Henrik</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DGaramond><SPAN=20
class=3D022064423-13112001></SPAN></FONT>&nbsp;</DIV></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
owner-seamoby@diameter.org=20
  [mailto:owner-seamoby@diameter.org]<B>On Behalf Of </B>Cedric=20
  Westphal<BR><B>Sent:</B> Tuesday, November 13, 2001 10:38 =
PM<BR><B>To:</B>=20
  Gary Kenward<BR><B>Cc:</B> 'Shahrier, Sharif M.';=20
  seamoby@cdma-2000.org<BR><B>Subject:</B> Re: [seamoby] Some proposed =
changes=20
  to the requirements draft.<BR><BR></DIV></FONT>Gary, Sharif, John,=20
  <P>if the requirement is a given, then let's not argue about/against =
it. It=20
  cannot <BR>hurt to include it, and _technically_ there is consensus =
for it.=20
  <P>As far as how to phrase it, usually scalability is described as the =

  marginal increase <BR>in complexity induced by adding users. So =
something=20
  along the lines: <BR>the processing complexity at each AR (and the =
burden on=20
  the wired network) <BR>SHOULD increase linearly with the number of MNs =
or the=20
  number of CT requests.=20
  <P>Also, you can check conformance there.=20
  <P>Cedric. <BR>&nbsp; <BR>&nbsp; <BR>&nbsp; <BR>&nbsp;=20
  <P>Gary Kenward wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE"><LINK =
href=3D"cid:filelist.xml@01C16C37.27CD6DA0"=20
    rel=3DFile-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
    <STYLE>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
    <SPAN class=3D927120321-13112001><FONT face=3D"Comic Sans MS"><FONT=20
    color=3D#0000ff>Sharif:</FONT></FONT></SPAN>=20
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma><FONT=20
      size=3D-1>-----Original Message-----</FONT></FONT> <BR><FONT=20
      face=3DTahoma><FONT size=3D-1><B>From:</B> Shahrier, Sharif M. [<A =

      =
href=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@I=
nterDigital.com</A>]</FONT></FONT>=20
      <BR><FONT face=3DTahoma><FONT size=3D-1><B>Sent:</B> November 13, =
2001=20
      11:29</FONT></FONT> <BR><FONT face=3DTahoma><FONT =
size=3D-1><B>To:</B>=20
      Kenward, Gary [WDLN2:AN10:EXCH]; 'john.loughney@nokia.com'; =
Shahrier,=20
      Sharif M.; seamoby@cdma-2000.org</FONT></FONT> <BR><FONT =
face=3DTahoma><FONT=20
      size=3D-1><B>Subject:</B> RE: [seamoby] Some proposed changes to =
the=20
      requirements draft.</FONT></FONT> <BR>&nbsp;</DIV>
      <DIV class=3DSection1><SPAN=20
      style=3D"COLOR: navy; FONT-SIZE: 12pt; FONT-WEIGHT: bold; =
mso-bidi-font-size: 10.0pt"><B><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000080><FONT=20
      size=3D+0>Gary,</FONT></FONT></FONT></B></SPAN><SPAN=20
      style=3D"COLOR: navy; FONT-WEIGHT: bold; mso-bidi-font-size: =
10.0pt; mso-color-alt: windowtext"><O:P></O:P></SPAN>=20

      <P><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000000><FONT=20
      size=3D-1>&gt;&nbsp;</FONT></FONT></FONT></SPAN><SPAN =
style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>&gt; &gt; 4.16 "The context =
transfer protocol=20
      MUST be scalable. It MUST be&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>&gt; &gt; scalable to millions of=20
      hosts".</FONT></FONT></SPAN><SPAN style=3D"COLOR: black"> =
<BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>&gt;&nbsp;</FONT></FONT></SPAN><SPAN style=3D"COLOR: =
black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>&gt; This is 'motherhood &amp; =
apple pie' text=20
      (i.e. - noone would really</FONT></FONT></SPAN><SPAN =
style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>&gt; disagree). I don't know how =
this adds=20
      anything to the text.&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>&gt; Additionally, I would suggest SHOULD rather than =
MUST=20
      is</FONT></FONT></SPAN><SPAN style=3D"COLOR: black"> =
<BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>&gt; what you mean.</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>&gt;&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000000><FONT =
size=3D-1>Myself, I do not=20
      know what "scaleable to millions of=20
      hosts"</FONT></FONT></FONT></SPAN><SPAN style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>really means. If the concern is in =
regards to=20
      the ability for the context</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>transfer solution to support a real wireless mobile =
network and=20
      one of the</FONT></FONT></SPAN><SPAN style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>constraining factors is the number =
of ct's=20
      that can be handled per time period,</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>then both the number of terminals *and* the number of =
handoffs per=20
      time period</FONT></FONT></SPAN><SPAN style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>are at issue (is trivial to say =
that any ct=20
      solution can handle an infinite number</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT size=3D-1>of=20
      terminals if the handoff rate is zero</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; FONT-SIZE: 10pt; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20

      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>I agree with =
this. Number of=20
      ct&#8217;s handled per time period and the number of handoffs per=20
      time</FONT></FONT></FONT><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>Period are both =
good cases to=20
      support the scalability requirement. The other point is the =
quantity of=20
      context information</FONT></FONT></FONT><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>Being =
transferred for each=20
      mobile over a given time. This bandwidth must be=20
      scalable.</FONT></FONT></FONT><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000000><FONT size=3D-1>It =
is not clear=20
      to me how we would define the scaleability of ct in any=20
      real</FONT></FONT></FONT></SPAN><SPAN style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>terms. We know that it must be =
applicable to=20
      within an administrative domain,</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT=20
      size=3D-1>and thus, the top limit would be the IP address space, =
but that is=20
      a greatest</FONT></FONT></SPAN><SPAN style=3D"COLOR: black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>upper bound and not very useful. =
Usually, in=20
      these situations, people resort</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR></SPAN><SPAN=20
      style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT =
color=3D#000000><FONT size=3D-1>to=20
      rate of complexity measures to define=20
      scaleability.</FONT></FONT></SPAN><SPAN style=3D"COLOR: =
black"></SPAN><SPAN=20
      style=3D"COLOR: black; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>I agree that =
the scalability=20
      of the CT must be applicabile within an administrative domain; =
scalability=20
      must also</FONT></FONT></FONT><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>Be applicable =
across=20
      different operator networks as=20
      well.</FONT></FONT></FONT><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><FONT=20
      face=3DArial><FONT color=3D#000080><FONT size=3D-1>I don&#8217;t =
see how the IPv4=20
      address space affects the scalability of CT. Could you please=20
      explain?</FONT></FONT></FONT> <BR><SPAN =
class=3D927120321-13112001><FONT=20
      face=3D"Comic Sans MS"><FONT color=3D#0000ff><FONT size=3D+0>[gwk] =
I doesn't,=20
      other then it puts "a" limit on the possible number of mobiles =
within=20
      an&nbsp;</FONT></FONT></FONT></SPAN></SPAN></SPAN><SPAN=20
      class=3DEmailStyle19><SPAN=20
      style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D927120321-13112001> <BR><FONT face=3D"Comic Sans MS"><FONT =

      color=3D#0000ff><FONT size=3D+0>administrative domain. An very =
high limit.=20
      Even higher if the domain uses=20
      IPv6.&nbsp;</FONT></FONT></FONT></SPAN><O:P></O:P></SPAN></SPAN>=20
      <P><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000000><FONT =
size=3D-1>Finally,=20
      scaleability is desireable, as long as the requirement is for=20
      scaleability</FONT></FONT></FONT></SPAN><SPAN style=3D"COLOR: =
black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>at an acceptable=20
      cost.&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000000><FONT =
size=3D-1>Other then this,=20
      I do not know how one would word a requirement around=20
      scaleability</FONT></FONT></FONT></SPAN><SPAN style=3D"COLOR: =
black">=20
      <BR></SPAN><SPAN style=3D"COLOR: black; FONT-SIZE: 10pt"><FONT=20
      color=3D#000000><FONT size=3D-1>other then the motherhood of "ct =
must be=20
      scaleable at an acceptable cost".</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"></SPAN><SPAN=20
      style=3D"COLOR: black; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000080>I agree. Perhaps =
something=20
      like:</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><FONT=20
      face=3D"Times New Roman"><FONT color=3D#000080>4.16 The context =
transfer=20
      protocol MUST be scalable at an acceptable =
cost.</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
      style=3D"mso-spacerun: yes"></SPAN><FONT face=3D"Times New =
Roman"><FONT=20
      color=3D#000080>The context transfer protocol MUST be ale to =
handle a large=20
      number of&nbsp;<SPAN style=3D"mso-spacerun: yes"></SPAN>of context =
transfers=20
      per second, and MUST</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
      style=3D"mso-spacerun: yes"></SPAN><FONT face=3D"Times New =
Roman"><FONT=20
      color=3D#000080>Be able to support a large number of handoffs per =
second.=20
      The quantity of context information being transferred for=20
      each&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
      style=3D"mso-spacerun: yes"></SPAN><FONT face=3D"Times New =
Roman"><FONT=20
      color=3D#000080>Mobile per second MUST be scalable, i.e. the =
bandwidth of=20
      the context transfer MUST be scalable.</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
      style=3D"mso-spacerun: yes"></SPAN><FONT face=3D"Times New =
Roman"><FONT=20
      color=3D#000080>The context transfers MAY be within the same =
administrative=20
      domain, or they MAY be across =
different&nbsp;</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: navy; mso-color-alt: =
windowtext"><O:P></O:P></SPAN>=20
      <P><SPAN style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
      style=3D"mso-spacerun: yes"></SPAN><FONT face=3D"Times New =
Roman"><FONT=20
      color=3D#000080>administrative domains.</FONT></FONT></SPAN><SPAN=20
      style=3D"COLOR: black"> <BR><SPAN class=3D927120321-13112001><FONT =

      face=3D"Comic Sans MS"><FONT color=3D#0000ff>[gwk] This is =
actually 7=20
      requirements. And, there is no way to ensure conformance to&nbsp; =
a number=20
      of them</FONT></FONT></SPAN></SPAN><SPAN style=3D"COLOR: =
black"><SPAN=20
      class=3D927120321-13112001> <BR><FONT face=3D"Comic Sans MS"><FONT =

      color=3D#0000ff>as written.&nbsp;</SPAN></SPAN><SPAN=20
      style=3D"COLOR: black"><SPAN class=3D927120321-13112001>While =
there are=20
      requirements in the existing draft that will be difficult to =
ensure=20
      conformance,&nbsp;</SPAN></SPAN><SPAN style=3D"COLOR: black"><SPAN =

      class=3D927120321-13112001>the wg</FONT></FONT></SPAN></SPAN><SPAN =

      style=3D"COLOR: black"><SPAN class=3D927120321-13112001> <BR><FONT =

      face=3D"Comic Sans MS"><FONT color=3D#0000ff>has made an effort to =
stay away=20
      from requirements which could not be tested (e.g. there is no "ct =
must be=20
      fast"</FONT></FONT></SPAN></SPAN><SPAN style=3D"COLOR: =
black"><SPAN=20
      class=3D927120321-13112001> <BR><FONT face=3D"Comic Sans MS"><FONT =

      color=3D#0000ff>requirement).&nbsp;</FONT></FONT></SPAN></SPAN>=20
      <P><SPAN class=3D927120321-13112001><FONT face=3D"Comic Sans =
MS"><FONT=20
      color=3D#0000ff>My personal opinion is in line with what John =
stated, that=20
      scalability is a given. Arguably, many stated =
requirements</FONT></FONT>=20
      <BR><FONT face=3D"Comic Sans MS"><FONT color=3D#0000ff>are =
"givens", but are=20
      stated for reinforcement. On the other hand, many givens are not =
stated as=20
      requirements simply to</FONT></FONT> <BR><FONT face=3D"Comic Sans =
MS"><FONT=20
      color=3D#0000ff>keep the number of requirements and the scope of =
the=20
      document to a manageable level. I would put "saleability" =
in</FONT></FONT>=20
      <BR><FONT face=3D"Comic Sans MS"><FONT color=3D#0000ff>the latter =
category,=20
      particularly with all the caveats that must go along with any =
saleability=20
      requirement for ct.</FONT></FONT></SPAN>=20
      <P><SPAN style=3D"COLOR: black"><SPAN =
class=3D927120321-13112001><FONT=20
      face=3D"Comic Sans MS"><FONT color=3D#0000ff>I hope this =
helps.</FONT></FONT>=20
      <BR><FONT face=3D"Comic Sans MS"><FONT=20
      =
color=3D#0000ff>Gary</FONT></FONT></SPAN></SPAN></P></DIV></BLOCKQUOTE></=
BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00E7_01C16CE7.25932510--



From owner-seamoby@diameter.org  Wed Nov 14 02:54:34 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15772
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 02:54:33 -0500 (EST)
Received: (qmail 28305 invoked by alias); 14 Nov 2001 08:25:48 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28299 invoked by uid 200); 14 Nov 2001 08:25:48 -0000
Received: (qmail 28291 invoked from network); 14 Nov 2001 08:25:43 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 08:25:43 -0000
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAE7cIA03946
	for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:38:18 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5736a0bb43ac158f22077@esvir02nok.nokia.com>;
 Wed, 14 Nov 2001 09:37:38 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWVD7Z>; Wed, 14 Nov 2001 09:37:38 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D905C@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: henrik@levkowetz.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:37:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16CDF.3476F16C"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16CDF.3476F16C
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Henrik,
 
 >  Please, can we drop this ?
 
Out of the darkness, a voice of reason appears.  I support this, let's not
add this requirement.
 
John
 
 

------_=_NextPart_001_01C16CDF.3476F16C
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.50.4611.1300" name=GENERATOR></HEAD>
<BODY lang=EN-US style="tab-interval: .5in" vLink=#0000ff link=#0000ff>
<DIV><SPAN class=965463407-14112001><FONT face=Arial color=#0000ff size=2>Hi 
Henrik,</FONT></SPAN></DIV>
<DIV><SPAN class=965463407-14112001></SPAN>&nbsp;</DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT color=#0000ff><SPAN 
class=965463407-14112001><FONT face=Arial size=2>&nbsp;&gt; 
&nbsp;</FONT></SPAN>Please, can we drop this<SPAN class=965463407-14112001><FONT 
face=Arial size=2>&nbsp;?</FONT></SPAN></FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001></SPAN></FONT></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001>Out of the darkness, a voice of reason appears.&nbsp; I 
support this, let's not add this 
requirement.</SPAN></FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001></SPAN></FONT></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001>John</SPAN></FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001></SPAN></FONT></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=Garamond><FONT face=Garamond><SPAN 
class=022064423-13112001><FONT face=Arial color=#0000ff size=2><SPAN 
class=965463407-14112001></SPAN><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]--></FONT></SPAN></FONT></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C16CDF.3476F16C--


From owner-seamoby@diameter.org  Wed Nov 14 09:35:28 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24636
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 09:35:27 -0500 (EST)
Received: (qmail 784 invoked by alias); 14 Nov 2001 15:21:37 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 778 invoked by uid 200); 14 Nov 2001 15:21:36 -0000
Received: (qmail 773 invoked from network); 14 Nov 2001 15:21:34 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 15:21:34 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951H2>; Wed, 14 Nov 2001 09:32:12 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99C@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        kempf@docomolabs-usa.com,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:32:03 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


The centralized approach to context transfer was dismissed
very early on. Is this still an issues?


For 5.6.2 I am not quite sure if some non-IETF protocols even
have the same definition for context as we do (PDP context is one
example), any idea??

Majid,

	The PDP context is used in the UMTS systems. A "global" PDP context
resides in the GGSN, and a "local" PDP context resides at each SGSN. The
context parameters at each SGSN is a subset of all those stored at the GGSN.
The MN's, of course, are attached to the SGSNs and send their datagrams to
the GGSN via the GTP (Generic Tunnel Protocol). 

Thus, the GGSN maintains a "central" context directory, while the SGSNs each
maintain a "local" context directory. 

The UMTS system is slated to use the IPv6 protocol, and hopefully, a lot of
the protocols that we develop in the IETF will find its way into this
architecture.

Aside from the UMTS, there are other wireless systems that will use context
transfer protocols with a combination of local/centralized directory
structure.

With this viewpoint, I strongly believe that the context transfer protocol
should support a combination of local and central context memory.

-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 09:40:00 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24882
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 09:39:59 -0500 (EST)
Received: (qmail 1214 invoked by alias); 14 Nov 2001 15:25:09 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1206 invoked by uid 200); 14 Nov 2001 15:25:08 -0000
Received: (qmail 1182 invoked from network); 14 Nov 2001 15:25:03 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 15:25:03 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951H8>; Wed, 14 Nov 2001 09:35:41 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99D@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Madjid.Nakhjiri@motorola.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:35:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


> The centralized approach to context transfer was dismissed
> very early on. Is this still an issues?

I don't think so.  However, if someone wants to invent
a way to do context transfer via a centralized server,
they can ... I don't think that any changes are needed
to the draft.

If this is the case then that is fine. The requirements draft did not
explicitly spell this out.

-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 09:54:09 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25642
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 09:53:08 -0500 (EST)
Received: (qmail 1228 invoked by alias); 14 Nov 2001 15:25:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1221 invoked by uid 200); 14 Nov 2001 15:25:09 -0000
Received: (qmail 1184 invoked from network); 14 Nov 2001 15:25:03 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 15:25:03 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951H7>; Wed, 14 Nov 2001 09:35:41 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D02D81272@idcpa4.pa.interdigital.com>
From: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:35:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16D19.A11718E0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D19.A11718E0
Content-Type: text/plain;
	charset="iso-8859-1"

Madjid,
 
I have some questions for clarifications.  First and before going into the
details, I would like to understand the focus of the work.  Is it only
concentrated on the context transfer?  or It involves the hooks that are
necessary to ensure that right contexts are at the right ARs serving the
right MNs?
 
I would agree with you that the authentication will take place between the
ARs before any CT takes place, may be as in wireless environment there is a
trust relationship between certain ARs where there is no need for
authorization.
 
However, if the MN is not involved in the CT.  How does the target AR ensure
that it is using the right context to serve the right MN? 
 
Regards,
 
Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Sherif,
 
First I think the chairs closed this thread. Authentication has to happen
between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context
reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed
authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open
issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once
for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT
data can be
authenticated if necessary. The receiving AR, will check the authentication
of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that
only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16D19.A11718E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16C5F.71909C00" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle20 {
	COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle21 {
	COLOR: #993366; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle22 {
	COLOR: #003300; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle23 {
	COLOR: olive; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue =
link=3Dblue>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Madjid,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>I have=20
some questions for clarifications.&nbsp; First and before going into =
the=20
details, I would like to understand the focus of the work.&nbsp; Is it =
only=20
concentrated on the context transfer?&nbsp;&nbsp;or&nbsp;It involves =
the hooks=20
that are necessary&nbsp;to ensure that right contexts are at the right =
ARs=20
serving the right MNs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D953211614-14112001></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
would agree with you that the&nbsp;authentication will take place =
between the=20
ARs before any CT takes place, may be as in wireless environment there =
is a=20
trust relationship between&nbsp;certain ARs&nbsp;where there is no need =
for=20
authorization.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953211614-14112001></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>However, if the MN is not involved in the CT.&nbsp; =
How&nbsp;does the=20
target AR ensure that it is using the right context&nbsp;to =
serve&nbsp;the right=20
MN?</FONT>&nbsp;</SPAN></DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953211614-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Kamel</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Nakhjiri =
Madjid-MNAKHJI1=20
  [mailto:Madjid.Nakhjiri@motorola.com]<BR><B>Sent:</B> Tue, November =
13, 2001=20
  7:42 PM<BR><B>To:</B> 'Shahrier, Sharif M.'; Nakhjiri =
Madjid-MNAKHJI1; 'Gary=20
  Kenward'<BR><B>Cc:</B> seamoby@cdma-2000.org<BR><B>Subject:</B> RE: =
[seamoby]=20
  Some proposed changes to the requirements draft.<BR><BR></FONT></DIV>
  <DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Sherif,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>First I think the chairs closed this thread. Authentication =
has to=20
  happen between ARs, since</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>CT=20
  happens between ARs. If the MN was supposed to be involved in context =

  reestablishment,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>we=20
  wouldn't be here in the first place.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Second, there are a lot of things that can go wrong with CT, =
and failed=20
  authentication is one</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>of=20
  them. Reliability for CT and the backup mechanisms for CT are still =
open=20
  issues, but for sure</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>a=20
  failed authentication at MN is not one of these issues and here is=20
  why:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>after the two ARs have authenticated themselves to each =
other (maybe=20
  once for all or maybe</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>before a CT, I don't inject my opinion here), then they =
engage in CT.=20
  The CT data can be</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>authenticated if necessary. The receiving AR, will check the =

  authentication of context data.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Architecture-wise, this is the only way to do it,&nbsp; =
based on the=20
  fact that only ARs do CT.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>And=20
  MN is not in this picture.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>Hope=20
  this clears things out.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D390533500-14112001><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Madjid</FONT></SPAN></DIV></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, =
Sharif M.=20
    [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> Tuesday, =
November=20
    13, 2001 3:17 PM<BR><B>To:</B> 'Nakhjiri Madjid-MNAKHJI1'; =
Shahrier, Sharif=20
    M.; 'Gary Kenward'<BR><B>Cc:</B> =
seamoby@cdma-2000.org<BR><B>Subject:</B>=20
    RE: [seamoby] Some proposed changes to the requirements=20
    draft.<BR><BR></FONT></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>Consider the case where the context transfer occurs before =
handover.=20
    So, the context will arrive at the newAR before</SPAN></FONT><FONT=20
    color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>The mobile node does. What if something goes wrong &#8211; =
the context is=20
    not correctly received by the newAR.</SPAN></FONT><FONT =
color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>When the MN arrives at the newAR, it needs to know this =
fact. So, the=20
    MN should authenticate the received context, =
just</SPAN></FONT><FONT=20
    color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>To make sure that its context was successfully received by =
the=20
    newAR.</SPAN></FONT><FONT color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
    color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dolive =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: olive">-Sharif.</SPAN></FONT><FONT =

    color=3Dblack><SPAN style=3D"COLOR: =
black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dolive><SPAN=20
    style=3D"COLOR: olive; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle23><FONT face=3DArial =
color=3Dolive=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Maybe =
you mean that=20
    the MN should authenticate the received context data, =
but</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">then why =
does the=20
    MN should do this. The context is going to the new AR,=20
    anyway.</SPAN></FONT><FONT color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If =
authentication=20
    of data is needed, new AR does it on behalf of =
MN.</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Why are =
we dragging=20
    MN into the authentication process.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">these =
issues are=20
    attacking the basic framework of CT, IMHO</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Madjid</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal=20
    style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; =
mso-margin-top-alt: auto"><FONT=20
    face=3DTahoma color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma">-----Or=
iginal=20
    Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
    Shahrier, Sharif M. =
[mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 10:44=20
    AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Gary =
Kenward';=20
    Shahrier, Sharif M.<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Cc:</SPAN></B>=20
    seamoby@cdma-2000.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
    changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>Understood. However, the requirements contains nothing (?) =
about the=20
    mobile authenticating with its context, after the context=20
    <o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">Has=20
    been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">I=20
    think a requirement should be there for this, otherwise, without=20
    authentication, the MN can &#8220;get at&#8221; any context, or =
context feature that its=20
    not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">How=20
    about:<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
    style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
    </SPAN><B><SPAN style=3D"FONT-WEIGHT: bold">There MUST be mutual=20
    authentication between the MN and its context, after the context =
transfer=20
    has occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN=20
    class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN=20
    class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle22><FONT=20
    face=3DArial color=3D#003300 size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3DTahoma color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
    Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B> Gary=20
    Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 11:07=20
    AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
'Shahrier, Sharif=20
    M.'<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
    'seamoby@cdma-2000.org'<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
    changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Times New Roman"=20
    color=3Dblack size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3DArial color=3Dblue=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sharif:</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Times New Roman"=20
    color=3Dblack size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3DArial color=3Dblue=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;=20
    This requirement is for the ARs to authenticate each other so that =
a ct=20
    exchange can</SPAN></FONT><FONT color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3DArial color=3Dblue=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">be=20
    trusted. It has nothing to do with the MN and handoff per=20
    se.</SPAN></FONT><FONT color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Times New Roman"=20
    color=3Dblack size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3DArial color=3Dblue=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Gary</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; MARGIN-BOTTOM: 12pt; PADDING-BOTTOM: =
0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none; mso-margin-top-alt: auto; =
mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in =
4.0pt"><FONT=20
    face=3DTahoma color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
    Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
    Shahrier, Sharif M. =
[mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001=20
    09:51<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Shahrier, Sharif=20
    M.<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
    'seamoby@cdma-2000.org'<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
    changes to the requirements draft.</SPAN></FONT><FONT face=3DTahoma =

    color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
    face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
    face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
    face=3D"Times New Roman" color=3D#993366 size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt; COLOR: #993366">I have some issues with =
the=20
    following requirement in the CT draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">4.9=20
    The entities transferring context MUST have completed a mutual=20
    authentication process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>initiating=20
    the transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
    don&#8217;t support this =
requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">It=20
    appears to me this may not fit the case for &#8220;break-before-make=
&#8221; handover=20
    .<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For instance, the =
mobile may=20
    break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">AP,=20
    and re-establish connection with the new AP.=20
    <o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Assuming=20
    that the context is transferred prior to re-establishing the new=20
    connection.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">The=20
    mobile will need to re-authenticate after it makes a new connection =
at its=20
    new AP.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
    have seen several practical cases that supports this scanario, thus =
I feel=20
    it is necessary for authentication after the transfer of context=20
    <o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">in=20
    =
&#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
    class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQ=
UOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16D19.A11718E0--


From owner-seamoby@diameter.org  Wed Nov 14 10:13:48 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27338
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 10:13:45 -0500 (EST)
Received: (qmail 1995 invoked by alias); 14 Nov 2001 15:33:37 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1989 invoked by uid 200); 14 Nov 2001 15:33:37 -0000
Received: (qmail 1984 invoked from network); 14 Nov 2001 15:33:33 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 15:33:33 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951JL>; Wed, 14 Nov 2001 09:44:02 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99E@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Henrik Levkowetz'" <henrik@levkowetz.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:43:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16D1A.CBC64330"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D1A.CBC64330
Content-Type: text/plain;
	charset="iso-8859-1"

Hello,
 
No, it is not a given that there's a requirement that the protocol MUST be
scalable to millions
of hosts. It SHOULD be scalable to the number of hosts that a MN may
reasonably have as
candidate access routers for a handover. 
 
In the paging requirements draft, section 4.2. explicitly spells out that:
 
            The IP paging protocol MUST be scalable to millions of Hosts.
 
This was agreed to earlier within this same WG. 
 
Since this was acceptable for both functional requirement and for
conformance testing, I can see no reason why it (or some version of it)
cannot be valid as well for the context transfer protocol requirements
draft.
 
-Sharif.
 
 

------_=_NextPart_001_01C16D1A.CBC64330
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16CF1.A81E7110">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Garamond;
	panose-1:2 2 4 4 3 3 1 1 8 3;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3D"#993366" =
face=3DGaramond><span
style=3D'font-size:12.0pt;font-family:Garamond;color:#993366'>Hello,</sp=
an></font><font
color=3D"#993366" face=3DGaramond><span =
style=3D'font-family:Garamond;color:#993366;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3D"#993366" =
face=3DGaramond><span
style=3D'font-size:12.0pt;font-family:Garamond;color:#993366'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3D"#993366" face=3DGaramond><span =
style=3D'font-family:Garamond;color:#993366;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DGaramond><span
style=3D'font-size:12.0pt;font-family:Garamond;color:blue'>No, it is =
not a given
that there's a requirement that the protocol MUST be scalable to =
millions<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DGaramond><span
style=3D'font-size:12.0pt;font-family:Garamond;color:blue'>of hosts. It =
SHOULD be
scalable to the number of hosts that a MN may reasonably have =
as<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DGaramond><span
style=3D'font-size:12.0pt;font-family:Garamond;color:blue'>candidate =
access
routers for a handover. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>In the paging requirements draft, section 4.2. explicitly spells =
out
that:<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>The
IP paging protocol MUST be scalable to millions of =
Hosts.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>This was agreed to earlier within this same WG. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Since this was acceptable for both functional requirement and =
for
conformance testing, I can see no reason why it (or some version of it) =
cannot
be valid as well for the context transfer protocol requirements =
draft.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

</div>

</body>

</html>

------_=_NextPart_001_01C16D1A.CBC64330--


From owner-seamoby@diameter.org  Wed Nov 14 10:31:03 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28109
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 10:29:27 -0500 (EST)
Received: (qmail 2216 invoked by alias); 14 Nov 2001 15:42:33 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2210 invoked by uid 200); 14 Nov 2001 15:42:32 -0000
Received: (qmail 2200 invoked from network); 14 Nov 2001 15:42:12 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 15:42:12 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951KN>; Wed, 14 Nov 2001 09:52:32 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F99F@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:52:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16D1B.F8C26AC0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D1B.F8C26AC0
Content-Type: text/plain;
	charset="iso-8859-1"

Majid,
 
            To add to points Kamel had made, I would also like to add
another point. 
 
            Given that there is a trust relationship between AR's in a
specific domain, where there is no need for authorization. If the MN then
were to "roam" to a different administrative domain, where there may be no
trust relationship between the AR's in the previous domain and the new
domain, how does the target AR in the new domain ensure that it is using the
right context to serve the right MN?
 
-Sharif.
 
-----Original Message-----
From: Shaheen, Kamel M. 
Sent: Wednesday, November 14, 2001 9:36 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Madjid,
 
I have some questions for clarifications.  First and before going into the
details, I would like to understand the focus of the work.  Is it only
concentrated on the context transfer?  or It involves the hooks that are
necessary to ensure that right contexts are at the right ARs serving the
right MNs?
 
I would agree with you that the authentication will take place between the
ARs before any CT takes place, may be as in wireless environment there is a
trust relationship between certain ARs where there is no need for
authorization.
 
However, if the MN is not involved in the CT.  How does the target AR ensure
that it is using the right context to serve the right MN? 
 
Regards,
 
Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Sherif,
 
First I think the chairs closed this thread. Authentication has to happen
between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context
reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed
authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open
issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once
for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT
data can be
authenticated if necessary. The receiving AR, will check the authentication
of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that
only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16D1B.F8C26AC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16CF2.D5189CD0">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:teal;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>M=
ajid,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>To
add to points Kamel had made, I would also like to add another point. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>Given
that there is a trust relationship between AR&#8217;s in a specific =
domain, where
there is no need for authorization. If the MN then were to =
&#8220;roam&#8221; to a
different administrative domain, where there may be no trust =
relationship
between the AR&#8217;s in the previous domain and the new domain, how =
does the target
AR in the new domain ensure that it is using the right context to serve =
the
right MN?<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle24><font size=3D2 =
color=3Dteal face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shaheen, Kamel M. =
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, =
November 14, 2001
9:36 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Nakhjiri =
Madjid-MNAKHJI1';
Shahrier, Sharif M.; 'Gary Kenward'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
seamoby@cdma-2000.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Madjid,</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I have some questions for
clarifications.&nbsp; First and before going into the details, I would =
like to
understand the focus of the work.&nbsp; Is it only concentrated on the =
context
transfer?&nbsp;&nbsp;or&nbsp;It involves the hooks that are =
necessary&nbsp;to
ensure that right contexts are at the right ARs serving the right =
MNs?</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I would agree with you that
the&nbsp;authentication will take place between the ARs before any CT =
takes
place, may be as in wireless environment there is a trust relationship
between&nbsp;certain ARs&nbsp;where there is no need for =
authorization.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>However, if the MN is not involved =
in the
CT.&nbsp; How&nbsp;does the target AR ensure that it is using the right
context&nbsp;to serve&nbsp;the right MN?</span></font><font =
color=3Dblack><span
style=3D'color:black'>&nbsp;</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Regards,</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Kamel</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:.5in'><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Nakhjiri =
Madjid-MNAKHJI1
[mailto:Madjid.Nakhjiri@motorola.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tue, November 13, =
2001 7:42
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.';
Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
seamoby@cdma-2000.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Sherif,</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>First I think the chairs closed =
this
thread. Authentication has to happen between ARs, =
since</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>CT happens between ARs. If the MN =
was
supposed to be involved in context reestablishment,</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>we wouldn't be here in the first =
place.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Second, there are a lot of things =
that can
go wrong with CT, and failed authentication is one</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>of them. Reliability for CT and =
the backup
mechanisms for CT are still open issues, but for =
sure</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>a failed authentication at MN is =
not one
of these issues and here is why:</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>after the two ARs have =
authenticated
themselves to each other (maybe once for all or =
maybe</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>before a CT, I don't inject my =
opinion
here), then they engage in CT. The CT data can be</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>authenticated if necessary. The =
receiving
AR, will check the authentication of context data.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Architecture-wise, this is the =
only way to
do it,&nbsp; based on the fact that only ARs do CT.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>And MN is not in this =
picture.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hope this clears things =
out.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Madjid</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:1.0in'><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
3:17 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Nakhjiri =
Madjid-MNAKHJI1';
Shahrier, Sharif M.; 'Gary Kenward'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
seamoby@cdma-2000.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><span =
class=3DEmailStyle23><font
size=3D2 color=3Dolive face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Majid,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><span =
class=3DEmailStyle23><font
size=3D2 color=3Dolive face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>Consider
the case where the context transfer occurs before handover. So, the =
context
will arrive at the newAR before</span></font><font color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>The
mobile node does. What if something goes wrong &#8211; the context is =
not correctly
received by the newAR.</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>When
the MN arrives at the newAR, it needs to know this fact. So, the MN =
should
authenticate the received context, just</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>To
make sure that its context was successfully received by the =
newAR.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dolive
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:olive'>-Sharif.</span></font><font
color=3Dblack><span style=3D'color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><span =
class=3DEmailStyle23><font
size=3D2 color=3Dolive face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Maybe
you mean that the MN should authenticate the received context data, =
but</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>then why
does the MN should do this. The context is going to the new AR, =
anyway.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>If
authentication of data is needed, new AR does it on behalf of =
MN.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Why are
we dragging MN into the authentication process.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>these
issues are attacking the basic framework of CT, IMHO</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Madjid</span></f=
ont><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:1.5in'><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
10:44 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Gary Kenward'; =
Shahrier,
Sharif M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
seamoby@cdma-2000.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>Gary,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Understood.
However, the requirements contains nothing (?) about the mobile =
authenticating
with its context, after the context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>Has been =
transferred.
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>I think a =
requirement
should be there for this, otherwise, without authentication, the MN can =
&#8220;get
at&#8221; any context, or context feature that its not authorized =
access to.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>How =
about:<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'><span
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><b><span
style=3D'font-weight:bold'>There MUST be mutual authentication between =
the MN and
its context, after the context transfer has =
occurred.<o:p></o:p></span></b></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><b><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman";font-weight:bold'>&nbsp;<o:p></o:p></span></font></b></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><b><font
size=3D2 color=3D"#003300" face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New =
Roman";font-weight:bold'>-Sharif.<o:p></o:p></span></font></b></span></p=
>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><span =
class=3DEmailStyle22><font
size=3D2 color=3D"#003300" face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Gary Kenward
[mailto:gkenward@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
13, 2001
11:07 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Sharif:</span></=
font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>&nbsp;
This requirement is for the ARs to authenticate each other so that a ct
exchange can</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>be
trusted. It has nothing to do with the MN and handoff per =
se.</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Gary</span></fon=
t><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;
margin-left:111.75pt;border:none;mso-border-left-alt:solid blue 1.5pt;
padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Shahrier, Sharif =
M.
[mailto:Sharif.Shahrier@InterDigital.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> November 13, 2001 =
09:51<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahrier, Sharif =
M.<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'seamoby@cdma-2000.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby] =
Some
proposed changes to the requirements draft.</span></font><font size=3D2
color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3D"#993366" face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:#993366'>I have some issues with the following requirement in the =
CT
draft.</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>4=
.9 The
entities transferring context MUST have completed a mutual =
authentication
process prior to<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" face=3DArial><span=

style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
span
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>initiating the
transfer.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 don&#8217;t
support this requirement.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
t appears
to me this may not fit the case for &#8220;break-before-make&#8221; =
handover .<span
style=3D"mso-spacerun: yes">&nbsp; </span>For instance, the mobile may =
break
connection with the old<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
P, and
re-establish connection with the new AP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
ssuming
that the context is transferred prior to re-establishing the new =
connection.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
he mobile
will need to re-authenticate after it makes a new connection at its new =
AP.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 have
seen several practical cases that supports this scanario, thus I feel =
it is
necessary for authentication after the transfer of context =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>i=
n
&#8220;break-before-make&#8221;.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>&=
nbsp;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:111.75pt;border:none;mso-border-left-alt:
solid blue 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle21><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C16D1B.F8C26AC0--


From owner-seamoby@diameter.org  Wed Nov 14 11:13:03 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA00555
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 11:12:46 -0500 (EST)
Received: (qmail 3839 invoked by alias); 14 Nov 2001 16:32:02 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 3833 invoked by uid 200); 14 Nov 2001 16:32:02 -0000
Received: (qmail 3821 invoked from network); 14 Nov 2001 16:31:40 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 16:31:40 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAEFgMS27335
	for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 10:42:22 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 14 Nov 2001 10:42:19 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W329FG5T>; Wed, 14 Nov 2001 10:40:19 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA464B@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:40:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16D22.A7EFA2A0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D22.A7EFA2A0
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:
 
   One thing that I am pretty sure Seamoby is not going to get into, is
exploring the world of
internetwork authentication. CT needs it, yes, but will Seamoby be defining
the solution?
As far as I know, it's not in our charter. Just as defining new security
protocols for CT was
place out of scope very early on in the discussions.
 
  You have valid points, many were discussed last spring. It doesn't hurt to
revisit issues, for
we are constantly expanding our understanding of this problem domain (or, at
least I hope so).
However, in my delusional view, we all need some real solution proposals to
chew on in order to
really progress.
 
  I realize that for you, the situation is very different. You have a real
system with real issues
to resolve. It is only one of many networks however, and perhaps a better
way to get the wg up
to speed on the specific requirements of UMTS (and other networks) is to
schedule some presentations
at the next IETF on existing context transfer problems/solutions. What say
you Pat and James?
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 14, 2001 09:52
To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
[WDLN2:AN10:EXCH]
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            To add to points Kamel had made, I would also like to add
another point. 
 
            Given that there is a trust relationship between AR's in a
specific domain, where there is no need for authorization. If the MN then
were to "roam" to a different administrative domain, where there may be no
trust relationship between the AR's in the previous domain and the new
domain, how does the target AR in the new domain ensure that it is using the
right context to serve the right MN?
 
-Sharif.
 
-----Original Message-----
From: Shaheen, Kamel M. 
Sent: Wednesday, November 14, 2001 9:36 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Madjid,
 
I have some questions for clarifications.  First and before going into the
details, I would like to understand the focus of the work.  Is it only
concentrated on the context transfer?  or It involves the hooks that are
necessary to ensure that right contexts are at the right ARs serving the
right MNs?
 
I would agree with you that the authentication will take place between the
ARs before any CT takes place, may be as in wireless environment there is a
trust relationship between certain ARs where there is no need for
authorization.
 
However, if the MN is not involved in the CT.  How does the target AR ensure
that it is using the right context to serve the right MN? 
 
Regards,
 
Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Sherif,
 
First I think the chairs closed this thread. Authentication has to happen
between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context
reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed
authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open
issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once
for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT
data can be
authenticated if necessary. The receiving AR, will check the authentication
of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that
only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16D22.A7EFA2A0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements draft.</TITLE>

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3315.2869" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK 
href="cid:filelist.xml@01C16CF2.D5189CD0" rel=File-List><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:teal;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>Sharif:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>&nbsp;&nbsp; One thing that I am pretty sure Seamoby is 
not going to get into, is exploring the world of</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>internetwork authentication. CT needs it, yes, but will 
Seamoby be defining the solution?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=766133815-14112001>As 
far as I know, it's not in our charter. Just as defining new security protocols 
for CT was</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>place out of scope very early on in the 
discussions.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>&nbsp; You have valid points, many were discussed last 
spring. It doesn't hurt to revisit issues, for</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=766133815-14112001>we 
are constantly expanding our understanding of this problem domain (or, at least 
I hope so).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><FONT face="Comic Sans MS"><SPAN 
class=766133815-14112001>However, in my delusional view, </SPAN>w<SPAN 
class=766133815-14112001>e all need some real solution proposals to chew on in 
order to</SPAN></FONT></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>really progress.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>&nbsp; I realize that for you, the situation is very 
different. You have a real system with real issues</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=766133815-14112001>to 
resolve. It is only one of many networks however, and perhaps a better way to 
get the wg up</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=766133815-14112001>to 
speed on the specific requirements of UMTS (and other networks) is to schedule 
some presentations</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN class=766133815-14112001>at 
the next IETF on existing context transfer problems/solutions. What say you Pat 
and James?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face="Comic Sans MS"><SPAN 
class=766133815-14112001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif M. 
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November 14, 2001 
  09:52<BR><B>To:</B> Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, 
  Gary [WDLN2:AN10:EXCH]<BR><B>Cc:</B> 
  'seamoby@cdma-2000.org'<BR><B>Subject:</B> RE: [seamoby] Some proposed changes 
  to the requirements draft.<BR><BR></DIV></FONT>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>To add to points Kamel had made, I would also like to add another 
  point. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Given that there is a trust relationship between AR&#8217;s in a specific 
  domain, where there is no need for authorization. If the MN then were to 
  &#8220;roam&#8221; to a different administrative domain, where there may be no trust 
  relationship between the AR&#8217;s in the previous domain and the new domain, how 
  does the target AR in the new domain ensure that it is using the right context 
  to serve the right MN?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><SPAN class=EmailStyle24><FONT color=teal face=Arial 
  size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal><FONT color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shaheen, 
  Kamel M. <BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, 
  November 14, 2001 9:36 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 
  'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> seamoby@cdma-2000.org<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
  style="FONT-SIZE: 12pt"><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Madjid,</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">I have some questions 
  for clarifications.&nbsp; First and before going into the details, I would 
  like to understand the focus of the work.&nbsp; Is it only concentrated on the 
  context transfer?&nbsp;&nbsp;or&nbsp;It involves the hooks that are 
  necessary&nbsp;to ensure that right contexts are at the right ARs serving the 
  right MNs?</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">I would agree with 
  you that the&nbsp;authentication will take place between the ARs before any CT 
  takes place, may be as in wireless environment there is a trust relationship 
  between&nbsp;certain ARs&nbsp;where there is no need for 
  authorization.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">However, if the MN is 
  not involved in the CT.&nbsp; How&nbsp;does the target AR ensure that it is 
  using the right context&nbsp;to serve&nbsp;the right MN?</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Regards,</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Kamel</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Nakhjiri 
  Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tue, November 13, 2001 7:42 
  PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif M.'; 
  Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> seamoby@cdma-2000.org<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Sherif,</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">First I think the 
  chairs closed this thread. Authentication has to happen between ARs, 
  since</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">CT happens between 
  ARs. If the MN was supposed to be involved in context 
  reestablishment,</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">we wouldn't be here 
  in the first place.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Second, there are a 
  lot of things that can go wrong with CT, and failed authentication is 
  one</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">of them. Reliability 
  for CT and the backup mechanisms for CT are still open issues, but for 
  sure</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">a failed 
  authentication at MN is not one of these issues and here is 
  why:</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">after the two ARs 
  have authenticated themselves to each other (maybe once for all or 
  maybe</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">before a CT, I don't 
  inject my opinion here), then they engage in CT. The CT data can 
  be</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">authenticated if 
  necessary. The receiving AR, will check the authentication of context 
  data.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Architecture-wise, 
  this is the only way to do it,&nbsp; based on the fact that only ARs do 
  CT.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">And MN is not in this 
  picture.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Hope this clears 
  things out.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT 
  color=blue face=Arial size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Madjid</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 1in; mso-margin-top-alt: auto"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 3:17 
  PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Nakhjiri 
  Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> seamoby@cdma-2000.org<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><SPAN class=EmailStyle23><FONT 
  color=olive face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><SPAN class=EmailStyle23><FONT 
  color=olive face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Consider the case where the context transfer occurs before handover. 
  So, the context will arrive at the newAR before</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>The mobile node does. What if something goes wrong &#8211; the context is not 
  correctly received by the newAR.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>When the MN arrives at the newAR, it needs to know this fact. So, the 
  MN should authenticate the received context, just</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>To make sure that its context was successfully received by the 
  newAR.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=olive 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: olive; FONT-SIZE: 12pt">-Sharif.</SPAN></FONT><FONT 
  color=black><SPAN style="COLOR: black">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><SPAN class=EmailStyle23><FONT 
  color=olive face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Maybe 
  you mean that the MN should authenticate the received context data, 
  but</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">then why 
  does the MN should do this. The context is going to the new AR, 
  anyway.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">If 
  authentication of data is needed, new AR does it on behalf of 
  MN.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Why are 
  we dragging MN into the authentication process.</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">these 
  issues are attacking the basic framework of CT, IMHO</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT color=blue face=Arial 
  size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Madjid</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 1.5in; mso-margin-top-alt: auto"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 10:44 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Gary Kenward'; 
  Shahrier, Sharif M.<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  seamoby@cdma-2000.org<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN>Understood. However, the requirements contains nothing (?) about the 
  mobile authenticating with its context, after the context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">Has 
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">I 
  think a requirement should be there for this, otherwise, without 
  authentication, the MN can &#8220;get at&#8221; any context, or context feature that its 
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">How 
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN 
  style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN><B><SPAN style="FONT-WEIGHT: bold">There MUST be mutual authentication 
  between the MN and its context, after the context transfer has 
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN 
  class=EmailStyle22><B><FONT color=#003300 face="Times New Roman" size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-WEIGHT: bold; mso-bidi-font-size: 12.0pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><SPAN class=EmailStyle22><FONT 
  color=#003300 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Gary 
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, 2001 11:07 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, Sharif 
  M.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=blue face=Arial 
  size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Sharif:</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">&nbsp; 
  This requirement is for the ARs to authenticate each other so that a ct 
  exchange can</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=blue face=Arial 
  size=2><SPAN style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">be 
  trusted. It has nothing to do with the MN and handoff per 
  se.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=black 
  face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 1.5in"><FONT color=blue face=Arial 
  size=2><SPAN 
  style="COLOR: blue; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Gary</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; BORDER-RIGHT: medium none; BORDER-TOP: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; PADDING-TOP: 0in">
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-margin-top-alt: auto; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face=Tahoma size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Shahrier, 
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 09:51<BR><B><SPAN 
  style="FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif M.<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Cc:</SPAN></B> 'seamoby@cdma-2000.org'<BR><B><SPAN 
  style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some proposed 
  changes to the requirements draft.</SPAN></FONT><FONT color=black face=Tahoma 
  size=2><SPAN 
  style="COLOR: black; FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=black face="Times New Roman" size=3><SPAN 
  style="COLOR: black; FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT 
  color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT 
  color=#993366 face="Times New Roman" size=3><SPAN 
  style="COLOR: #993366; FONT-SIZE: 12pt">I have some issues with the following 
  requirement in the CT draft.</SPAN></FONT><FONT color=black><SPAN 
  style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">4.9 
  The entities transferring context MUST have completed a mutual authentication 
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt"><SPAN 
  style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>initiating the 
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I 
  don&#8217;t support this requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">It 
  appears to me this may not fit the case for &#8220;break-before-make&#8221; handover 
  .<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>For instance, the mobile may 
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">AP, 
  and re-establish connection with the new AP. 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Assuming 
  that the context is transferred prior to re-establishing the new 
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The 
  mobile will need to re-authenticate after it makes a new connection at its new 
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">I have 
  seen several practical cases that supports this scanario, thus I feel it is 
  necessary for authentication after the transfer of context 
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">in 
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=MsoNormal 
  style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 111.75pt; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; PADDING-TOP: 0in; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN 
  class=EmailStyle21><FONT color=#993366 face=Arial size=2><SPAN 
  style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C16D22.A7EFA2A0--


From owner-seamoby@diameter.org  Wed Nov 14 11:37:22 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02138
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 11:37:20 -0500 (EST)
Received: (qmail 4113 invoked by alias); 14 Nov 2001 16:39:34 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4107 invoked by uid 200); 14 Nov 2001 16:39:33 -0000
Received: (qmail 4098 invoked from network); 14 Nov 2001 16:39:30 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 16:39:30 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0951QH>; Wed, 14 Nov 2001 10:50:04 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A0@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:49:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16D24.02A5B8F0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D24.02A5B8F0
Content-Type: text/plain;
	charset="iso-8859-1"

 
  I realize that for you, the situation is very different. You have a real
system with real issues
to resolve. It is only one of many networks however, and perhaps a better
way to get the wg up
to speed on the specific requirements of UMTS (and other networks) is to
schedule some presentations
at the next IETF on existing context transfer problems/solutions. What say
you Pat and James?
 
Gary,
 
            I would support the presentation of existing context transfer
problems/solutions at the next IETF meeting. If Pat and James agree to this
suggestion, I would try and see if I can get something together on the PDP
context in the UMTS.
 
-Sharif.

------_=_NextPart_001_01C16D24.02A5B8F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16CFA.DF23E560">
<title>RE: [seamoby] Some proposed changes to the requirements =
draft.</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:script;
	mso-font-pitch:variable;
	mso-font-signature:647 0 0 0 159 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.EmailStyle22
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#003300;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:olive;}
span.EmailStyle24
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:teal;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:purple;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans =
MS";color:blue'>&nbsp; I
realize that for you, the situation is very different. You have a real =
system
with real issues</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>to =
resolve. It
is only one of many networks however, and perhaps a better way to get =
the wg up</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>to =
speed on the
specific requirements of UMTS (and other networks) is to schedule some
presentations</span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Comic Sans =
MS"><span
style=3D'font-size:12.0pt;font-family:"Comic Sans MS";color:blue'>at =
the next
IETF on existing context transfer problems/solutions. What say you Pat =
and
James?</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3Dpurple
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial;color:purple'>Gary,</span></font></span><span =
class=3DEmailStyle21><font
size=3D2 color=3Dpurple face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial;color:purple;mso-color-alt:windowtext'><o:p></o=
:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle25><font size=3D2 =
color=3Dpurple
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle25><font size=3D2 =
color=3Dpurple
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>I
would support the presentation of existing context transfer =
problems/solutions
at the next IETF meeting. If Pat and James agree to this suggestion, I =
would
try and see if I can get something together on the PDP context in the =
UMTS.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle25><font size=3D2 =
color=3Dpurple
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle25><font size=3D2 =
color=3Dpurple
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C16D24.02A5B8F0--


From owner-seamoby@diameter.org  Wed Nov 14 11:43:58 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02707
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 11:43:55 -0500 (EST)
Received: (qmail 4933 invoked by alias); 14 Nov 2001 16:58:11 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4927 invoked by uid 200); 14 Nov 2001 16:58:10 -0000
Received: (qmail 4920 invoked from network); 14 Nov 2001 16:58:06 -0000
Received: from ftpbox.mot.com (129.188.136.101)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 16:58:06 -0000
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id JAA24642 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:09:27 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id JAA18782 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:09:27 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4K50>; Wed, 14 Nov 2001 10:09:27 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB25@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shaheen, Kamel M.'" <Kamel.Shaheen@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:09:25 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Kamel, 

Please see my responses in line.

Regards,
Madjid

-----Original Message-----
From: Shaheen, Kamel M. [mailto:Kamel.Shaheen@InterDigital.com]
Sent: Wednesday, November 14, 2001 8:36 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Madjid,

I have some questions for clarifications.  First and before going into the
details, I would like to understand the focus of the work.  Is it only
concentrated on the context transfer?  or It involves the hooks that are
necessary to ensure that right contexts are at the right ARs serving the
right MNs?

Madjid>> Well If I may speak on the design team's behalf, others are welcome
to pitch in:
Yes, I think the consensus was that we only focus on transfer of context
not storage, dump, collection.... for the protocol standardization process.
However, for an implementation, you can't avoid the issues you mentioned.
We need to get into the specifics of each feature and see where the unit
that is processing that feature (say diffserv..) is located. 
Since this question is very feature specific, we decided to limit the scope
and say that we assume context resides at old (transmitting) AR prior to
transmission
and it will be received by one single unit (new AR) and it is "re-routed"
from there
to the feature processing unit.
If you assume otherwise, definition of a protocol without going into
specifics of 
each feature become very hard.

I would agree with you that the authentication will take place between the
ARs before any CT takes place, may be as in wireless environment there is a
trust relationship between certain ARs where there is no need for
authorization.

Madjid>> Authentication between ARs might happen once for all based on a
mutual trust (say an 
established SA). This would help timing and scalability of all future CTs
between those two
ARs regardless of which MN is involved. Don't know what you mean by
authorization here, but
authentication of the MN specific data can be a separate issues and might
require
more protection (maybe even encryption). So other measures are needed.
Please look at
our TEXT draft, 
http://www.ietf.org/internet-drafts/draft-nakhjiri-seamoby-text-ct-00.txt
for a bit more details on security issues (not quite mature yet).

However, if the MN is not involved in the CT.  

Madjid>> Depends what you call MN's involvement, is it sending the actual
context data
(this was ruled out), or is it just involved in trigger mechanism (we used
this one
in our draft). 

How does the target AR ensure that it is using the right context to serve
the right MN? 

Madjid>> This was why a standard formulation for context data and messaging
is needed.
An MN identifier and a microflow identifier and a feature identifier all
needed to make
sure the target AR understands what it needs to do with the data, please
take a look at
our draft for an example.



Regards,

Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Sherif,

First I think the chairs closed this thread. Authentication has to happen
between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context
reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed
authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open
issues, but for sure
a failed authentication at MN is not one of these issues and here is why:

after the two ARs have authenticated themselves to each other (maybe once
for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT
data can be
authenticated if necessary. The receiving AR, will check the authentication
of context data.

Architecture-wise, this is the only way to do it,  based on the fact that
only ARs do CT.
And MN is not in this picture.

Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            Consider the case where the context transfer occurs before
handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context
is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact.
So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the
newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data,
but
then why does the MN should do this. The context is going to the new AR,
anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?)
about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without
authentication, the MN can "get at" any context, or context feature that its
not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its
context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct
exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual
authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover
.  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new
connection.
 
The mobile will need to re-authenticate after it makes a new connection at
its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel
it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 12:04:20 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04004
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 12:03:05 -0500 (EST)
Received: (qmail 5210 invoked by alias); 14 Nov 2001 17:10:43 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 5204 invoked by uid 200); 14 Nov 2001 17:10:43 -0000
Received: (qmail 5196 invoked from network); 14 Nov 2001 17:10:29 -0000
Received: from motgate4.mot.com (144.189.100.102)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 17:10:29 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate4.mot.com (motgate4 2.1) with ESMTP id JAA25110 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:22:14 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id JAA01459 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:12:36 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8M6WF>; Wed, 14 Nov 2001 10:22:13 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB26@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:22:12 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16D28.8430BAB0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16D28.8430BAB0
Content-Type: text/plain;
	charset="iso-8859-1"

Sherif,
 
I think you are actually contradicting him, he says you need both.
To answer your question, not having a "trust relationship" ( I don't like this term: I call
it security association) is not a CT specific problem, it is a general mobility/ security problem.
You want secure communication, you need security association. NO SA, no security.
You want security AND seamless mobility, you need to establish SAs in advance
or just don't move.
 
 
If you have an actual problem for which you think requirements are blocking
 a solution for (assuming that it is within the scope), I suggest you write an ID and
state that problem, so we all understand your position. 
 
Otherwise,  We have discussed ALL of your issues in length, please look at the archives.
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Wednesday, November 14, 2001 8:52 AM
To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            To add to points Kamel had made, I would also like to add another point. 
 
            Given that there is a trust relationship between AR's in a specific domain, where there is no need for authorization. If the MN then were to "roam" to a different administrative domain, where there may be no trust relationship between the AR's in the previous domain and the new domain, how does the target AR in the new domain ensure that it is using the right context to serve the right MN?
 
-Sharif.
 
-----Original Message-----
From: Shaheen, Kamel M. 
Sent: Wednesday, November 14, 2001 9:36 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Madjid,
 
I have some questions for clarifications.  First and before going into the details, I would like to understand the focus of the work.  Is it only concentrated on the context transfer?  or It involves the hooks that are necessary to ensure that right contexts are at the right ARs serving the right MNs?
 
I would agree with you that the authentication will take place between the ARs before any CT takes place, may be as in wireless environment there is a trust relationship between certain ARs where there is no need for authorization.
 
However, if the MN is not involved in the CT.  How does the target AR ensure that it is using the right context to serve the right MN? 
 
Regards,
 
Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Sherif,
 
First I think the chairs closed this thread. Authentication has to happen between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT data can be
authenticated if necessary. The receiving AR, will check the authentication of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Majid,
 
            Consider the case where the context transfer occurs before handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact. So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data, but
then why does the MN should do this. The context is going to the new AR, anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?) about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without authentication, the MN can "get at" any context, or context feature that its not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover .  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new connection.
 
The mobile will need to re-authenticate after it makes a new connection at its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.

------_=_NextPart_001_01C16D28.8430BAB0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C16CF2.D5189CD0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; LINE-HEIGHT: =
200%; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle20 {
	COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle21 {
	COLOR: #993366; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle22 {
	COLOR: #003300; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle23 {
	COLOR: olive; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle24 {
	COLOR: teal; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue =
link=3Dblue>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Sherif,</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
think you are actually contradicting him, he says you need=20
both.</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>To=20
answer your question, not having a "trust relationship" ( I don't like =
this=20
term: I call</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>it=20
security association) is not a CT specific problem, it is a general =
mobility/=20
security&nbsp;problem.</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>You=20
want secure communication, you need security association. NO SA, no=20
security.</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>You=20
want security AND seamless mobility, you need to establish SAs in=20
advance</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>or=20
just don't move.</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff size=3D2>If you=20
have an actual problem for which </FONT></SPAN><SPAN=20
class=3D475191016-14112001><FONT face=3DArial color=3D#0000ff =
size=3D2>you think=20
requirements are blocking</FONT></SPAN></DIV>
<DIV><SPAN class=3D475191016-14112001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>&nbsp;a solution for (assuming that it is within the scope), I =
suggest=20
you write an ID and</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D475191016-14112001>state that problem, so we all understand =
your position.=20
</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D475191016-14112001></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D475191016-14112001>Otherwise,&nbsp;</SPAN><SPAN=20
class=3D475191016-14112001>&nbsp;<SPAN class=3D475191016-14112001><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>We have discussed&nbsp;ALL of your&nbsp;issues =
in length,=20
please look at the =
archives.</FONT></SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D475191016-14112001><SPAN=20
class=3D475191016-14112001></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DI=
V>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D475191016-14112001><SPAN=20
class=3D475191016-14112001>Madjid</SPAN></SPAN></FONT></FONT></FONT></DI=
V>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif =
M.=20
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> Wednesday, =
November=20
  14, 2001 8:52 AM<BR><B>To:</B> Shaheen, Kamel M.; 'Nakhjiri =
Madjid-MNAKHJI1';=20
  'Gary Kenward'<BR><B>Cc:</B> seamoby@cdma-2000.org<BR><B>Subject:</B> =
RE:=20
  [seamoby] Some proposed changes to the requirements=20
draft.<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>To add to points Kamel had made, I would also like to add =
another=20
  point. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Given that there is a trust relationship between AR&#8217;s in =
a specific=20
  domain, where there is no need for authorization. If the MN then were =
to=20
  &#8220;roam&#8221; to a different administrative domain, where there =
may be no trust=20
  relationship between the AR&#8217;s in the previous domain and the =
new domain, how=20
  does the target AR in the new domain ensure that it is using the =
right context=20
  to serve the right MN?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle24><FONT face=3DArial =
color=3Dteal=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><FONT face=3DTahoma color=3Dblack size=3D2><SPAN =

  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shaheen,=20
  Kamel M. <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Wednesday,=20
  November 14, 2001 9:36 AM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
  'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary =
Kenward'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
seamoby@cdma-2000.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Madjid,</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I have =
some questions=20
  for clarifications.&nbsp; First and before going into the details, I =
would=20
  like to understand the focus of the work.&nbsp; Is it only =
concentrated on the=20
  context transfer?&nbsp;&nbsp;or&nbsp;It involves the hooks that are=20
  necessary&nbsp;to ensure that right contexts are at the right ARs =
serving the=20
  right MNs?</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I would =
agree with=20
  you that the&nbsp;authentication will take place between the ARs =
before any CT=20
  takes place, may be as in wireless environment there is a trust =
relationship=20
  between&nbsp;certain ARs&nbsp;where there is no need for=20
  authorization.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">However, =
if the MN is=20
  not involved in the CT.&nbsp; How&nbsp;does the target AR ensure that =
it is=20
  using the right context&nbsp;to serve&nbsp;the right =
MN?</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Kamel</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; mso-margin-top-alt: =
auto"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Nakhjiri=20
  Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tue, November 13, 2001 =
7:42=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, =
Sharif M.';=20
  Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
seamoby@cdma-2000.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sherif,</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">First I =
think the=20
  chairs closed this thread. Authentication has to happen between ARs,=20
  since</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">CT happens =
between=20
  ARs. If the MN was supposed to be involved in context=20
  reestablishment,</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">we =
wouldn't be here=20
  in the first place.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Second, =
there are a=20
  lot of things that can go wrong with CT, and failed authentication is =

  one</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">of them. =
Reliability=20
  for CT and the backup mechanisms for CT are still open issues, but =
for=20
  sure</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">a failed=20
  authentication at MN is not one of these issues and here is=20
  why:</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">after the =
two ARs=20
  have authenticated themselves to each other (maybe once for all or=20
  maybe</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">before a =
CT, I don't=20
  inject my opinion here), then they engage in CT. The CT data can=20
  be</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">authenticated if=20
  necessary. The receiving AR, will check the authentication of context =

  data.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Architecture-wise,=20
  this is the only way to do it,&nbsp; based on the fact that only ARs =
do=20
  CT.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">And MN is =
not in this=20
  picture.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hope this =
clears=20
  things out.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto"><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Madjid</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 1in; mso-margin-top-alt: =
auto"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 3:17=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Nakhjiri=20
  Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
seamoby@cdma-2000.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle23><FONT=20
  face=3DArial color=3Dolive size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Majid,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle23><FONT=20
  face=3DArial color=3Dolive size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: =
olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Consider the case where the context transfer occurs before =
handover.=20
  So, the context will arrive at the newAR before</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: =
olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>The mobile node does. What if something goes wrong &#8211; the =
context is not=20
  correctly received by the newAR.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: =
olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>When the MN arrives at the newAR, it needs to know this fact. =
So, the=20
  MN should authenticate the received context, just</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: =
olive"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>To make sure that its context was successfully received by the =

  newAR.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dolive size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: olive">-Sharif.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle23><FONT=20
  face=3DArial color=3Dolive size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Maybe=20
  you mean that the MN should authenticate the received context data,=20
  but</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">then why=20
  does the MN should do this. The context is going to the new AR,=20
  anyway.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">If=20
  authentication of data is needed, new AR does it on behalf of=20
  MN.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT 
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Why are=20
  we dragging MN into the authentication process.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">these=20
  issues are attacking the basic framework of CT, =
IMHO</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Madjid</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 1.5in; mso-margin-top-alt: =
auto"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 10:44=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Gary =
Kenward';=20
  Shahrier, Sharif M.<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Cc:</SPAN></B>=20
  seamoby@cdma-2000.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">Gary,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>Understood. However, the requirements contains nothing (?) =
about the=20
  mobile authenticating with its context, after the context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">Has=20
  been transferred. <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">I=20
  think a requirement should be there for this, otherwise, without=20
  authentication, the MN can &#8220;get at&#8221; any context, or =
context feature that its=20
  not authorized access to.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'">How=20
  about:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3D"Times New Roman" color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New Roman'"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><B><SPAN style=3D"FONT-WEIGHT: bold">There MUST be mutual =
authentication=20
  between the MN and its context, after the context transfer has=20
  occurred.<o:p></o:p></SPAN></B></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN=20
  class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">&nbsp;<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN=20
  class=3DEmailStyle22><B><FONT face=3D"Times New Roman" =
color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">-Sharif.<o:p></o:p></SPAN></FONT></B></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle22><FONT=20
  face=3DArial color=3D#003300 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Gary=20
  Kenward [mailto:gkenward@nortelnetworks.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 13, =
2001 11:07=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Shahrier, =
Sharif=20
  M.'<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
  'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sharif:</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;=20
  This requirement is for the ARs to authenticate each other so that a =
ct=20
  exchange can</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">be=20
  trusted. It has nothing to do with the MN and handoff per=20
  se.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Gary</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; MARGIN-BOTTOM: 12pt; PADDING-BOTTOM: =
0in; MARGIN-LEFT: 111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none; mso-margin-top-alt: auto; =
mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: 0in 0in 0in =
4.0pt"><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Shahrier,=20
  Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> November 13, 2001 =
09:51<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Shahrier, Sharif =
M.<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
'seamoby@cdma-2000.org'<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [seamoby] Some =
proposed=20
  changes to the requirements draft.</SPAN></FONT><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><FONT=20
  face=3D"Times New Roman" color=3D#993366 size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: #993366">I have some issues with the =
following=20
  requirement in the CT draft.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">4.9=20
  The entities transferring context MUST have completed a mutual =
authentication=20
  process prior to<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>initiating the=20
  transfer.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
  don&#8217;t support this =
requirement.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">It=20
  appears to me this may not fit the case for =
&#8220;break-before-make&#8221; handover=20
  .<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For instance, the =
mobile may=20
  break connection with the old<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">AP,=20
  and re-establish connection with the new AP.=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Assuming=20
  that the context is transferred prior to re-establishing the new=20
  connection.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">The=20
  mobile will need to re-authenticate after it makes a new connection =
at its new=20
  AP.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I have=20
  seen several practical cases that supports this scanario, thus I feel =
it is=20
  necessary for authentication after the transfer of context=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">in=20
  &#8220;break-before-make&#8221;.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: =
111.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none; mso-border-left-alt: solid blue 1.5pt; mso-padding-alt: =
0in 0in 0in 4.0pt"><SPAN=20
  class=3DEmailStyle21><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-Sharif.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></DIV></BLOCKQ=
UOTE></BODY></HTML>

------_=_NextPart_001_01C16D28.8430BAB0--


From owner-seamoby@diameter.org  Wed Nov 14 12:29:36 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05799
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 12:29:34 -0500 (EST)
Received: (qmail 5301 invoked by alias); 14 Nov 2001 17:13:56 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 5295 invoked by uid 200); 14 Nov 2001 17:13:55 -0000
Received: (qmail 5287 invoked from network); 14 Nov 2001 17:13:50 -0000
Received: from motgate.mot.com (129.188.136.100)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 17:13:50 -0000
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate.mot.com (motgate 2.1) with ESMTP id JAB17534 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:25:42 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id JAA06702 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 09:25:41 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8M66T>; Wed, 14 Nov 2001 10:25:41 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB27@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:25:40 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Speaking of solution proposal, anybody has had a chance to look at our draft, I think
we tried to open up some issues there.

http://www.ietf.org/internet-drafts/draft-nakhjiri-seamoby-text-ct-00.txt

Regards,
Madjid

-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Wednesday, November 14, 2001 9:40 AM
To: 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Sharif:

   One thing that I am pretty sure Seamoby is not going to get into, is exploring the world of
internetwork authentication. CT needs it, yes, but will Seamoby be defining the solution?
As far as I know, it's not in our charter. Just as defining new security protocols for CT was
place out of scope very early on in the discussions.

  You have valid points, many were discussed last spring. It doesn't hurt to revisit issues, for
we are constantly expanding our understanding of this problem domain (or, at least I hope so).
However, in my delusional view, we all need some real solution proposals to chew on in order to
really progress.

  I realize that for you, the situation is very different. You have a real system with real issues
to resolve. It is only one of many networks however, and perhaps a better way to get the wg up
to speed on the specific requirements of UMTS (and other networks) is to schedule some presentations
at the next IETF on existing context transfer problems/solutions. What say you Pat and James?

Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 14, 2001 09:52
To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary [WDLN2:AN10:EXCH]
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Majid,
 
            To add to points Kamel had made, I would also like to add another point. 
 
            Given that there is a trust relationship between AR's in a specific domain, where there is no need for authorization. If the MN then were to "roam" to a different administrative domain, where there may be no trust relationship between the AR's in the previous domain and the new domain, how does the target AR in the new domain ensure that it is using the right context to serve the right MN?
 
-Sharif.
 
-----Original Message-----
From: Shaheen, Kamel M. 
Sent: Wednesday, November 14, 2001 9:36 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Madjid,
 
I have some questions for clarifications.  First and before going into the details, I would like to understand the focus of the work.  Is it only concentrated on the context transfer?  or It involves the hooks that are necessary to ensure that right contexts are at the right ARs serving the right MNs?
 
I would agree with you that the authentication will take place between the ARs before any CT takes place, may be as in wireless environment there is a trust relationship between certain ARs where there is no need for authorization.
 
However, if the MN is not involved in the CT.  How does the target AR ensure that it is using the right context to serve the right MN? 
 
Regards,
 
Kamel
-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Tue, November 13, 2001 7:42 PM
To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Sherif,
 
First I think the chairs closed this thread. Authentication has to happen between ARs, since
CT happens between ARs. If the MN was supposed to be involved in context reestablishment,
we wouldn't be here in the first place.
Second, there are a lot of things that can go wrong with CT, and failed authentication is one
of them. Reliability for CT and the backup mechanisms for CT are still open issues, but for sure
a failed authentication at MN is not one of these issues and here is why:
 
after the two ARs have authenticated themselves to each other (maybe once for all or maybe
before a CT, I don't inject my opinion here), then they engage in CT. The CT data can be
authenticated if necessary. The receiving AR, will check the authentication of context data.
 
Architecture-wise, this is the only way to do it,  based on the fact that only ARs do CT.
And MN is not in this picture.
 
Hope this clears things out.
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 3:17 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Majid,
 
            Consider the case where the context transfer occurs before handover. So, the context will arrive at the newAR before
            The mobile node does. What if something goes wrong - the context is not correctly received by the newAR.
            When the MN arrives at the newAR, it needs to know this fact. So, the MN should authenticate the received context, just
            To make sure that its context was successfully received by the newAR.
 
-Sharif. 
 
Maybe you mean that the MN should authenticate the received context data, but
then why does the MN should do this. The context is going to the new AR, anyway.
If authentication of data is needed, new AR does it on behalf of MN.
 
Why are we dragging MN into the authentication process.
 
these issues are attacking the basic framework of CT, IMHO
 
Madjid
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Tuesday, November 13, 2001 10:44 AM
To: 'Gary Kenward'; Shahrier, Sharif M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Gary,
 
                Understood. However, the requirements contains nothing (?) about the mobile authenticating with its context, after the context 
Has been transferred. 
 
I think a requirement should be there for this, otherwise, without authentication, the MN can "get at" any context, or context feature that its not authorized access to.
 
How about:
 
                There MUST be mutual authentication between the MN and its context, after the context transfer has occurred.
 
-Sharif.
 
-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Tuesday, November 13, 2001 11:07 AM
To: 'Shahrier, Sharif M.'
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
Sharif:
 
  This requirement is for the ARs to authenticate each other so that a ct exchange can
be trusted. It has nothing to do with the MN and handoff per se.
 
Gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 13, 2001 09:51
To: Shahrier, Sharif M.
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
 
 
I have some issues with the following requirement in the CT draft.
 
4.9 The entities transferring context MUST have completed a mutual authentication process prior to
      initiating the transfer.
 
I don't support this requirement.
 
It appears to me this may not fit the case for "break-before-make" handover .  For instance, the mobile may break connection with the old
AP, and re-establish connection with the new AP. 
 
Assuming that the context is transferred prior to re-establishing the new connection.
 
The mobile will need to re-authenticate after it makes a new connection at its new AP.
 
I have seen several practical cases that supports this scanario, thus I feel it is necessary for authentication after the transfer of context 
in "break-before-make".
 
-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 12:36:54 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06165
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 12:36:54 -0500 (EST)
Received: (qmail 7312 invoked by alias); 14 Nov 2001 18:10:18 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 7306 invoked by uid 200); 14 Nov 2001 18:10:17 -0000
Received: (qmail 7299 invoked from network); 14 Nov 2001 18:10:06 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 18:10:06 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAEHDL524522;
	Wed, 14 Nov 2001 09:13:21 -0800 (PST)
Message-ID: <001301c16d2f$701995e0$cc6ffea9@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>,
        "Gary Kenward" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
References: <35DBB8B7AC89D4118E98009027B1009B0464FB1C@IL27EXM10.cig.mot.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:11:45 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Well, how about "enclosing" then? I just think we need to clarify the
requirement text some, as I think it is unclear
as currently written.

        jak

----- Original Message -----
From: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Gary Kenward"
<gkenward@nortelnetworks.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Sent: Tuesday, November 13, 2001 4:22 PM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> can we not use the word "encapsulating" context information, it
> could be inpreted as tunneling, or maybe I am paranoid :)
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Monday, November 12, 2001 7:17 PM
> To: Gary Kenward; Shahrier, Sharif M.; seamoby
> Cc: Shahrier, Sharif M.
> Subject: Re: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Gary,
>
> > The wording may need to be fixed, but the requirement is not as you
> > are both interpreting it. The "standard representation"
> > referred to is the representation of the data chunks, or objects,
> > in the context transfer protocol that are used to contain the
context.
> > The actual context is encapsulated within these data chunks, and the
> > representation of that context is opaque to context transfer. What
is
> > needed is a standard representation for these containers.
> >
> > The words do say "a standard representation for *conveying*"; the
> > key words are "for conveying". They do not say "a standard
> representation
> > for the context" which is how you are both interpreting the
> requirement.
> >
> > Again, we can clarify the wording, but the requirement still makes
> sense.
> > As for James proposal, this would be a new requirement.
> >
>
> I misunderstood the requirement. I think you need to reword it to
avoid
> the possibility of misunderstanding. How about:
>
>     The context transfer protocol MUST define a standardized container
>     format for encapsulating and conveying context information.
> Interpretation
>     of the context information within the container is the domain of
the
> application
>     for which context is being transfered. Applications SHOULD define
an
> interoperable
>     format for context information if they want to use the context
> transfer protocol.
>
> Or, you can simply include the first sentence if you feel that the
rest
> is too controversial
> or would expand the requirement beyond what is currently agreed.
>
>             jak
>



From owner-seamoby@diameter.org  Wed Nov 14 12:48:16 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06875
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 12:48:12 -0500 (EST)
Received: (qmail 8676 invoked by alias); 14 Nov 2001 18:33:31 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8670 invoked by uid 200); 14 Nov 2001 18:33:30 -0000
Received: (qmail 8665 invoked from network); 14 Nov 2001 18:33:28 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 18:33:28 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAEHXo525459;
	Wed, 14 Nov 2001 09:33:50 -0800 (PST)
Message-ID: <008c01c16d32$4c8520b0$cc6ffea9@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
References: <9FBD322B7824D511B36900508BF93C9C01AA464B@zcard031.ca.nortel.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 09:32:13 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary/Sharif,

I certainly agree that we should not be tayloring our requirements for
existing UMTS/GPRS networks. The requirements should define the
properties of a desirable solution for the Internet.

Regarding the specific requirement, about authentication, as Majhid
indicated, the thread is closed. CT happens between ARs or other
entities involved in routing in the wired network. The MN isn't
involved. If you look at the problem statement (the latest draft of
which is on my disk ready to go), that's how it is defined. So the
authentication involved is between ARs.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
"Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 7:40 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Sharif:
>
>    One thing that I am pretty sure Seamoby is not going to get into,
is
> exploring the world of
> internetwork authentication. CT needs it, yes, but will Seamoby be
defining
> the solution?
> As far as I know, it's not in our charter. Just as defining new
security
> protocols for CT was
> place out of scope very early on in the discussions.
>
>   You have valid points, many were discussed last spring. It doesn't
hurt to
> revisit issues, for
> we are constantly expanding our understanding of this problem domain
(or, at
> least I hope so).
> However, in my delusional view, we all need some real solution
proposals to
> chew on in order to
> really progress.
>
>   I realize that for you, the situation is very different. You have a
real
> system with real issues
> to resolve. It is only one of many networks however, and perhaps a
better
> way to get the wg up
> to speed on the specific requirements of UMTS (and other networks) is
to
> schedule some presentations
> at the next IETF on existing context transfer problems/solutions. What
say
> you Pat and James?
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 14, 2001 09:52
> To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> [WDLN2:AN10:EXCH]
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Majid,
>
>             To add to points Kamel had made, I would also like to add
> another point.
>
>             Given that there is a trust relationship between AR's in a
> specific domain, where there is no need for authorization. If the MN
then
> were to "roam" to a different administrative domain, where there may
be no
> trust relationship between the AR's in the previous domain and the new
> domain, how does the target AR in the new domain ensure that it is
using the
> right context to serve the right MN?
>
> -Sharif.
>
> -----Original Message-----
> From: Shaheen, Kamel M.
> Sent: Wednesday, November 14, 2001 9:36 AM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Madjid,
>
> I have some questions for clarifications.  First and before going into
the
> details, I would like to understand the focus of the work.  Is it only
> concentrated on the context transfer?  or It involves the hooks that
are
> necessary to ensure that right contexts are at the right ARs serving
the
> right MNs?
>
> I would agree with you that the authentication will take place between
the
> ARs before any CT takes place, may be as in wireless environment there
is a
> trust relationship between certain ARs where there is no need for
> authorization.
>
> However, if the MN is not involved in the CT.  How does the target AR
ensure
> that it is using the right context to serve the right MN?
>
> Regards,
>
> Kamel
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Tue, November 13, 2001 7:42 PM
> To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Sherif,
>
> First I think the chairs closed this thread. Authentication has to
happen
> between ARs, since
> CT happens between ARs. If the MN was supposed to be involved in
context
> reestablishment,
> we wouldn't be here in the first place.
> Second, there are a lot of things that can go wrong with CT, and
failed
> authentication is one
> of them. Reliability for CT and the backup mechanisms for CT are still
open
> issues, but for sure
> a failed authentication at MN is not one of these issues and here is
why:
>
> after the two ARs have authenticated themselves to each other (maybe
once
> for all or maybe
> before a CT, I don't inject my opinion here), then they engage in CT.
The CT
> data can be
> authenticated if necessary. The receiving AR, will check the
authentication
> of context data.
>
> Architecture-wise, this is the only way to do it,  based on the fact
that
> only ARs do CT.
> And MN is not in this picture.
>
> Hope this clears things out.
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 3:17 PM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Majid,
>
>             Consider the case where the context transfer occurs before
> handover. So, the context will arrive at the newAR before
>             The mobile node does. What if something goes wrong - the
context
> is not correctly received by the newAR.
>             When the MN arrives at the newAR, it needs to know this
fact.
> So, the MN should authenticate the received context, just
>             To make sure that its context was successfully received by
the
> newAR.
>
> -Sharif.
>
> Maybe you mean that the MN should authenticate the received context
data,
> but
> then why does the MN should do this. The context is going to the new
AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>
> Why are we dragging MN into the authentication process.
>
> these issues are attacking the basic framework of CT, IMHO
>
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Gary,
>
>                 Understood. However, the requirements contains nothing
(?)
> about the mobile authenticating with its context, after the context
> Has been transferred.
>
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature
that its
> not authorized access to.
>
> How about:
>
>                 There MUST be mutual authentication between the MN and
its
> context, after the context transfer has occurred.
>
> -Sharif.
>
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Sharif:
>
>   This requirement is for the ARs to authenticate each other so that a
ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> I have some issues with the following requirement in the CT draft.
>
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>
> I don't support this requirement.
>
> It appears to me this may not fit the case for "break-before-make"
handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP.
>
> Assuming that the context is transferred prior to re-establishing the
new
> connection.
>
> The mobile will need to re-authenticate after it makes a new
connection at
> its new AP.
>
> I have seen several practical cases that supports this scanario, thus
I feel
> it is necessary for authentication after the transfer of context
> in "break-before-make".
>
> -Sharif.
>



From owner-seamoby@diameter.org  Wed Nov 14 13:32:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09887
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 13:32:16 -0500 (EST)
Received: (qmail 9583 invoked by alias); 14 Nov 2001 19:18:53 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9578 invoked by uid 200); 14 Nov 2001 19:18:52 -0000
Received: (qmail 9572 invoked from network); 14 Nov 2001 19:18:49 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 19:18:49 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate2.mot.com (motgate2 2.1) with ESMTP id LAA26618 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 11:29:43 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id LAA06726 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 11:20:05 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG430W>; Wed, 14 Nov 2001 12:29:42 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB2D@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 12:29:40 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Yes, without even seeing the entire text, I definitely
prefer enclosing over encapsulating :)

Madjid

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wednesday, November 14, 2001 11:12 AM
To: Nakhjiri Madjid-MNAKHJI1; Gary Kenward; Shahrier, Sharif M.; seamoby
Cc: Shahrier, Sharif M.
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


Well, how about "enclosing" then? I just think we need to clarify the
requirement text some, as I think it is unclear
as currently written.

        jak

----- Original Message -----
From: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Gary Kenward"
<gkenward@nortelnetworks.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "seamoby" <seamoby@cdma-2000.org>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Sent: Tuesday, November 13, 2001 4:22 PM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> can we not use the word "encapsulating" context information, it
> could be inpreted as tunneling, or maybe I am paranoid :)
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Monday, November 12, 2001 7:17 PM
> To: Gary Kenward; Shahrier, Sharif M.; seamoby
> Cc: Shahrier, Sharif M.
> Subject: Re: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Gary,
>
> > The wording may need to be fixed, but the requirement is not as you
> > are both interpreting it. The "standard representation"
> > referred to is the representation of the data chunks, or objects,
> > in the context transfer protocol that are used to contain the
context.
> > The actual context is encapsulated within these data chunks, and the
> > representation of that context is opaque to context transfer. What
is
> > needed is a standard representation for these containers.
> >
> > The words do say "a standard representation for *conveying*"; the
> > key words are "for conveying". They do not say "a standard
> representation
> > for the context" which is how you are both interpreting the
> requirement.
> >
> > Again, we can clarify the wording, but the requirement still makes
> sense.
> > As for James proposal, this would be a new requirement.
> >
>
> I misunderstood the requirement. I think you need to reword it to
avoid
> the possibility of misunderstanding. How about:
>
>     The context transfer protocol MUST define a standardized container
>     format for encapsulating and conveying context information.
> Interpretation
>     of the context information within the container is the domain of
the
> application
>     for which context is being transfered. Applications SHOULD define
an
> interoperable
>     format for context information if they want to use the context
> transfer protocol.
>
> Or, you can simply include the first sentence if you feel that the
rest
> is too controversial
> or would expand the requirement beyond what is currently agreed.
>
>             jak
>


From owner-seamoby@diameter.org  Wed Nov 14 13:37:55 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10211
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 13:37:52 -0500 (EST)
Received: (qmail 10006 invoked by alias); 14 Nov 2001 19:21:28 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9998 invoked by uid 200); 14 Nov 2001 19:21:28 -0000
Received: (qmail 9986 invoked from network); 14 Nov 2001 19:21:24 -0000
Received: from motgate4.mot.com (144.189.100.102)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 19:21:24 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate4.mot.com (motgate4 2.1) with ESMTP id LAA26677 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 11:33:33 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id LAA09212 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 11:23:55 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4PCJ>; Wed, 14 Nov 2001 12:33:32 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB2E@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 12:33:31 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Thanks, 

I agree. Our requirements can't look like UMTS requirements.

The UMTS/ GPRS need for context transfer is definitely
 a topic of interest, BUT in a separate ID. I will look forward to reading
it.

Madjid


-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wednesday, November 14, 2001 11:32 AM
To: Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri
Madjid-MNAKHJI1'
Cc: seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


Gary/Sharif,

I certainly agree that we should not be tayloring our requirements for
existing UMTS/GPRS networks. The requirements should define the
properties of a desirable solution for the Internet.

Regarding the specific requirement, about authentication, as Majhid
indicated, the thread is closed. CT happens between ARs or other
entities involved in routing in the wired network. The MN isn't
involved. If you look at the problem statement (the latest draft of
which is on my disk ready to go), that's how it is defined. So the
authentication involved is between ARs.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
"Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 7:40 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Sharif:
>
>    One thing that I am pretty sure Seamoby is not going to get into,
is
> exploring the world of
> internetwork authentication. CT needs it, yes, but will Seamoby be
defining
> the solution?
> As far as I know, it's not in our charter. Just as defining new
security
> protocols for CT was
> place out of scope very early on in the discussions.
>
>   You have valid points, many were discussed last spring. It doesn't
hurt to
> revisit issues, for
> we are constantly expanding our understanding of this problem domain
(or, at
> least I hope so).
> However, in my delusional view, we all need some real solution
proposals to
> chew on in order to
> really progress.
>
>   I realize that for you, the situation is very different. You have a
real
> system with real issues
> to resolve. It is only one of many networks however, and perhaps a
better
> way to get the wg up
> to speed on the specific requirements of UMTS (and other networks) is
to
> schedule some presentations
> at the next IETF on existing context transfer problems/solutions. What
say
> you Pat and James?
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 14, 2001 09:52
> To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> [WDLN2:AN10:EXCH]
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Majid,
>
>             To add to points Kamel had made, I would also like to add
> another point.
>
>             Given that there is a trust relationship between AR's in a
> specific domain, where there is no need for authorization. If the MN
then
> were to "roam" to a different administrative domain, where there may
be no
> trust relationship between the AR's in the previous domain and the new
> domain, how does the target AR in the new domain ensure that it is
using the
> right context to serve the right MN?
>
> -Sharif.
>
> -----Original Message-----
> From: Shaheen, Kamel M.
> Sent: Wednesday, November 14, 2001 9:36 AM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Madjid,
>
> I have some questions for clarifications.  First and before going into
the
> details, I would like to understand the focus of the work.  Is it only
> concentrated on the context transfer?  or It involves the hooks that
are
> necessary to ensure that right contexts are at the right ARs serving
the
> right MNs?
>
> I would agree with you that the authentication will take place between
the
> ARs before any CT takes place, may be as in wireless environment there
is a
> trust relationship between certain ARs where there is no need for
> authorization.
>
> However, if the MN is not involved in the CT.  How does the target AR
ensure
> that it is using the right context to serve the right MN?
>
> Regards,
>
> Kamel
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Tue, November 13, 2001 7:42 PM
> To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Sherif,
>
> First I think the chairs closed this thread. Authentication has to
happen
> between ARs, since
> CT happens between ARs. If the MN was supposed to be involved in
context
> reestablishment,
> we wouldn't be here in the first place.
> Second, there are a lot of things that can go wrong with CT, and
failed
> authentication is one
> of them. Reliability for CT and the backup mechanisms for CT are still
open
> issues, but for sure
> a failed authentication at MN is not one of these issues and here is
why:
>
> after the two ARs have authenticated themselves to each other (maybe
once
> for all or maybe
> before a CT, I don't inject my opinion here), then they engage in CT.
The CT
> data can be
> authenticated if necessary. The receiving AR, will check the
authentication
> of context data.
>
> Architecture-wise, this is the only way to do it,  based on the fact
that
> only ARs do CT.
> And MN is not in this picture.
>
> Hope this clears things out.
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 3:17 PM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Majid,
>
>             Consider the case where the context transfer occurs before
> handover. So, the context will arrive at the newAR before
>             The mobile node does. What if something goes wrong - the
context
> is not correctly received by the newAR.
>             When the MN arrives at the newAR, it needs to know this
fact.
> So, the MN should authenticate the received context, just
>             To make sure that its context was successfully received by
the
> newAR.
>
> -Sharif.
>
> Maybe you mean that the MN should authenticate the received context
data,
> but
> then why does the MN should do this. The context is going to the new
AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>
> Why are we dragging MN into the authentication process.
>
> these issues are attacking the basic framework of CT, IMHO
>
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Gary,
>
>                 Understood. However, the requirements contains nothing
(?)
> about the mobile authenticating with its context, after the context
> Has been transferred.
>
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature
that its
> not authorized access to.
>
> How about:
>
>                 There MUST be mutual authentication between the MN and
its
> context, after the context transfer has occurred.
>
> -Sharif.
>
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Sharif:
>
>   This requirement is for the ARs to authenticate each other so that a
ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> I have some issues with the following requirement in the CT draft.
>
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>
> I don't support this requirement.
>
> It appears to me this may not fit the case for "break-before-make"
handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP.
>
> Assuming that the context is transferred prior to re-establishing the
new
> connection.
>
> The mobile will need to re-authenticate after it makes a new
connection at
> its new AP.
>
> I have seen several practical cases that supports this scanario, thus
I feel
> it is necessary for authentication after the transfer of context
> in "break-before-make".
>
> -Sharif.
>


From owner-seamoby@diameter.org  Wed Nov 14 13:49:24 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10729
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 13:49:20 -0500 (EST)
Received: (qmail 10781 invoked by alias); 14 Nov 2001 19:34:33 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 10775 invoked by uid 200); 14 Nov 2001 19:34:33 -0000
Received: (qmail 10769 invoked from network); 14 Nov 2001 19:34:30 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 19:34:30 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095FFC>; Wed, 14 Nov 2001 13:45:08 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D02D81273@idcpa4.pa.interdigital.com>
From: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 13:45:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I would respectfully disagree.  I think it would be beneficial to this work
to understand and to take previous work into consideration (not necessarily
to duplicate) if we would like wider acceptance and more generalized
solution.  Specially given the current drive toward global more harmonized
kind of interworking.

Regards,

Kamel 

-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Wed, November 14, 2001 1:34 PM
To: 'James Kempf'; Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel
M.; Nakhjiri Madjid-MNAKHJI1
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Thanks, 

I agree. Our requirements can't look like UMTS requirements.

The UMTS/ GPRS need for context transfer is definitely
 a topic of interest, BUT in a separate ID. I will look forward to reading
it.

Madjid


-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wednesday, November 14, 2001 11:32 AM
To: Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri
Madjid-MNAKHJI1'
Cc: seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


Gary/Sharif,

I certainly agree that we should not be tayloring our requirements for
existing UMTS/GPRS networks. The requirements should define the
properties of a desirable solution for the Internet.

Regarding the specific requirement, about authentication, as Majhid
indicated, the thread is closed. CT happens between ARs or other
entities involved in routing in the wired network. The MN isn't
involved. If you look at the problem statement (the latest draft of
which is on my disk ready to go), that's how it is defined. So the
authentication involved is between ARs.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
"Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 7:40 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Sharif:
>
>    One thing that I am pretty sure Seamoby is not going to get into,
is
> exploring the world of
> internetwork authentication. CT needs it, yes, but will Seamoby be
defining
> the solution?
> As far as I know, it's not in our charter. Just as defining new
security
> protocols for CT was
> place out of scope very early on in the discussions.
>
>   You have valid points, many were discussed last spring. It doesn't
hurt to
> revisit issues, for
> we are constantly expanding our understanding of this problem domain
(or, at
> least I hope so).
> However, in my delusional view, we all need some real solution
proposals to
> chew on in order to
> really progress.
>
>   I realize that for you, the situation is very different. You have a
real
> system with real issues
> to resolve. It is only one of many networks however, and perhaps a
better
> way to get the wg up
> to speed on the specific requirements of UMTS (and other networks) is
to
> schedule some presentations
> at the next IETF on existing context transfer problems/solutions. What
say
> you Pat and James?
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 14, 2001 09:52
> To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> [WDLN2:AN10:EXCH]
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Majid,
>
>             To add to points Kamel had made, I would also like to add
> another point.
>
>             Given that there is a trust relationship between AR's in a
> specific domain, where there is no need for authorization. If the MN
then
> were to "roam" to a different administrative domain, where there may
be no
> trust relationship between the AR's in the previous domain and the new
> domain, how does the target AR in the new domain ensure that it is
using the
> right context to serve the right MN?
>
> -Sharif.
>
> -----Original Message-----
> From: Shaheen, Kamel M.
> Sent: Wednesday, November 14, 2001 9:36 AM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Madjid,
>
> I have some questions for clarifications.  First and before going into
the
> details, I would like to understand the focus of the work.  Is it only
> concentrated on the context transfer?  or It involves the hooks that
are
> necessary to ensure that right contexts are at the right ARs serving
the
> right MNs?
>
> I would agree with you that the authentication will take place between
the
> ARs before any CT takes place, may be as in wireless environment there
is a
> trust relationship between certain ARs where there is no need for
> authorization.
>
> However, if the MN is not involved in the CT.  How does the target AR
ensure
> that it is using the right context to serve the right MN?
>
> Regards,
>
> Kamel
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Tue, November 13, 2001 7:42 PM
> To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Sherif,
>
> First I think the chairs closed this thread. Authentication has to
happen
> between ARs, since
> CT happens between ARs. If the MN was supposed to be involved in
context
> reestablishment,
> we wouldn't be here in the first place.
> Second, there are a lot of things that can go wrong with CT, and
failed
> authentication is one
> of them. Reliability for CT and the backup mechanisms for CT are still
open
> issues, but for sure
> a failed authentication at MN is not one of these issues and here is
why:
>
> after the two ARs have authenticated themselves to each other (maybe
once
> for all or maybe
> before a CT, I don't inject my opinion here), then they engage in CT.
The CT
> data can be
> authenticated if necessary. The receiving AR, will check the
authentication
> of context data.
>
> Architecture-wise, this is the only way to do it,  based on the fact
that
> only ARs do CT.
> And MN is not in this picture.
>
> Hope this clears things out.
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 3:17 PM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Majid,
>
>             Consider the case where the context transfer occurs before
> handover. So, the context will arrive at the newAR before
>             The mobile node does. What if something goes wrong - the
context
> is not correctly received by the newAR.
>             When the MN arrives at the newAR, it needs to know this
fact.
> So, the MN should authenticate the received context, just
>             To make sure that its context was successfully received by
the
> newAR.
>
> -Sharif.
>
> Maybe you mean that the MN should authenticate the received context
data,
> but
> then why does the MN should do this. The context is going to the new
AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>
> Why are we dragging MN into the authentication process.
>
> these issues are attacking the basic framework of CT, IMHO
>
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Gary,
>
>                 Understood. However, the requirements contains nothing
(?)
> about the mobile authenticating with its context, after the context
> Has been transferred.
>
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature
that its
> not authorized access to.
>
> How about:
>
>                 There MUST be mutual authentication between the MN and
its
> context, after the context transfer has occurred.
>
> -Sharif.
>
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Sharif:
>
>   This requirement is for the ARs to authenticate each other so that a
ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> I have some issues with the following requirement in the CT draft.
>
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>
> I don't support this requirement.
>
> It appears to me this may not fit the case for "break-before-make"
handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP.
>
> Assuming that the context is transferred prior to re-establishing the
new
> connection.
>
> The mobile will need to re-authenticate after it makes a new
connection at
> its new AP.
>
> I have seen several practical cases that supports this scanario, thus
I feel
> it is necessary for authentication after the transfer of context
> in "break-before-make".
>
> -Sharif.
>


From owner-seamoby@diameter.org  Wed Nov 14 14:07:41 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11784
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 14:07:16 -0500 (EST)
Received: (qmail 11462 invoked by alias); 14 Nov 2001 19:52:00 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11456 invoked by uid 200); 14 Nov 2001 19:52:00 -0000
Received: (qmail 11451 invoked from network); 14 Nov 2001 19:51:58 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 19:51:58 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAEIxm529447;
	Wed, 14 Nov 2001 10:59:48 -0800 (PST)
Message-ID: <013801c16d3e$4ea09030$cc6ffea9@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Gary Kenward" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D02D81273@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 10:58:11 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Kamel,

This issue came up last spring. The IETF is specifically concerned with
standards for the Internet, it is the Standards Development Organization
(SDO) for the Internet. Working groups can consider the experience of
other standards development organizations when developing Internet
standards, that is simple common sense and good engineering practice. We
can also consider the needs of othe standards bodies for Internet
standards, just as we consider the needs of companies and individuals.
But any requirements or protocols we develop should be focused on the
Internet, not on standards developed by other standards bodies.

Hope that's clear.

            jak

----- Original Message -----
From: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>; "'James
Kempf'" <kempf@docomolabs-usa.com>; "Gary Kenward"
<gkenward@nortelnetworks.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "Shaheen, Kamel M."
<Kamel.Shaheen@InterDigital.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 10:45 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> I would respectfully disagree.  I think it would be beneficial to this
work
> to understand and to take previous work into consideration (not
necessarily
> to duplicate) if we would like wider acceptance and more generalized
> solution.  Specially given the current drive toward global more
harmonized
> kind of interworking.
>
> Regards,
>
> Kamel
>
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Wed, November 14, 2001 1:34 PM
> To: 'James Kempf'; Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel
> M.; Nakhjiri Madjid-MNAKHJI1
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Thanks,
>
> I agree. Our requirements can't look like UMTS requirements.
>
> The UMTS/ GPRS need for context transfer is definitely
>  a topic of interest, BUT in a separate ID. I will look forward to
reading
> it.
>
> Madjid
>
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, November 14, 2001 11:32 AM
> To: Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri
> Madjid-MNAKHJI1'
> Cc: seamoby@cdma-2000.org
> Subject: Re: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Gary/Sharif,
>
> I certainly agree that we should not be tayloring our requirements for
> existing UMTS/GPRS networks. The requirements should define the
> properties of a desirable solution for the Internet.
>
> Regarding the specific requirement, about authentication, as Majhid
> indicated, the thread is closed. CT happens between ARs or other
> entities involved in routing in the wired network. The MN isn't
> involved. If you look at the problem statement (the latest draft of
> which is on my disk ready to go), that's how it is defined. So the
> authentication involved is between ARs.
>
>             jak
>
> ----- Original Message -----
> From: "Gary Kenward" <gkenward@nortelnetworks.com>
> To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
> "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
> Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Wednesday, November 14, 2001 7:40 AM
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> > Sharif:
> >
> >    One thing that I am pretty sure Seamoby is not going to get into,
> is
> > exploring the world of
> > internetwork authentication. CT needs it, yes, but will Seamoby be
> defining
> > the solution?
> > As far as I know, it's not in our charter. Just as defining new
> security
> > protocols for CT was
> > place out of scope very early on in the discussions.
> >
> >   You have valid points, many were discussed last spring. It doesn't
> hurt to
> > revisit issues, for
> > we are constantly expanding our understanding of this problem domain
> (or, at
> > least I hope so).
> > However, in my delusional view, we all need some real solution
> proposals to
> > chew on in order to
> > really progress.
> >
> >   I realize that for you, the situation is very different. You have
a
> real
> > system with real issues
> > to resolve. It is only one of many networks however, and perhaps a
> better
> > way to get the wg up
> > to speed on the specific requirements of UMTS (and other networks)
is
> to
> > schedule some presentations
> > at the next IETF on existing context transfer problems/solutions.
What
> say
> > you Pat and James?
> >
> > Gary
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: November 14, 2001 09:52
> > To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> > [WDLN2:AN10:EXCH]
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> >
> > Majid,
> >
> >             To add to points Kamel had made, I would also like to
add
> > another point.
> >
> >             Given that there is a trust relationship between AR's in
a
> > specific domain, where there is no need for authorization. If the MN
> then
> > were to "roam" to a different administrative domain, where there may
> be no
> > trust relationship between the AR's in the previous domain and the
new
> > domain, how does the target AR in the new domain ensure that it is
> using the
> > right context to serve the right MN?
> >
> > -Sharif.
> >
> > -----Original Message-----
> > From: Shaheen, Kamel M.
> > Sent: Wednesday, November 14, 2001 9:36 AM
> > To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> > Madjid,
> >
> > I have some questions for clarifications.  First and before going
into
> the
> > details, I would like to understand the focus of the work.  Is it
only
> > concentrated on the context transfer?  or It involves the hooks that
> are
> > necessary to ensure that right contexts are at the right ARs serving
> the
> > right MNs?
> >
> > I would agree with you that the authentication will take place
between
> the
> > ARs before any CT takes place, may be as in wireless environment
there
> is a
> > trust relationship between certain ARs where there is no need for
> > authorization.
> >
> > However, if the MN is not involved in the CT.  How does the target
AR
> ensure
> > that it is using the right context to serve the right MN?
> >
> > Regards,
> >
> > Kamel
> > -----Original Message-----
> > From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> > Sent: Tue, November 13, 2001 7:42 PM
> > To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Sherif,
> >
> > First I think the chairs closed this thread. Authentication has to
> happen
> > between ARs, since
> > CT happens between ARs. If the MN was supposed to be involved in
> context
> > reestablishment,
> > we wouldn't be here in the first place.
> > Second, there are a lot of things that can go wrong with CT, and
> failed
> > authentication is one
> > of them. Reliability for CT and the backup mechanisms for CT are
still
> open
> > issues, but for sure
> > a failed authentication at MN is not one of these issues and here is
> why:
> >
> > after the two ARs have authenticated themselves to each other (maybe
> once
> > for all or maybe
> > before a CT, I don't inject my opinion here), then they engage in
CT.
> The CT
> > data can be
> > authenticated if necessary. The receiving AR, will check the
> authentication
> > of context data.
> >
> > Architecture-wise, this is the only way to do it,  based on the fact
> that
> > only ARs do CT.
> > And MN is not in this picture.
> >
> > Hope this clears things out.
> > Madjid
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: Tuesday, November 13, 2001 3:17 PM
> > To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Majid,
> >
> >             Consider the case where the context transfer occurs
before
> > handover. So, the context will arrive at the newAR before
> >             The mobile node does. What if something goes wrong - the
> context
> > is not correctly received by the newAR.
> >             When the MN arrives at the newAR, it needs to know this
> fact.
> > So, the MN should authenticate the received context, just
> >             To make sure that its context was successfully received
by
> the
> > newAR.
> >
> > -Sharif.
> >
> > Maybe you mean that the MN should authenticate the received context
> data,
> > but
> > then why does the MN should do this. The context is going to the new
> AR,
> > anyway.
> > If authentication of data is needed, new AR does it on behalf of MN.
> >
> > Why are we dragging MN into the authentication process.
> >
> > these issues are attacking the basic framework of CT, IMHO
> >
> > Madjid
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: Tuesday, November 13, 2001 10:44 AM
> > To: 'Gary Kenward'; Shahrier, Sharif M.
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Gary,
> >
> >                 Understood. However, the requirements contains
nothing
> (?)
> > about the mobile authenticating with its context, after the context
> > Has been transferred.
> >
> > I think a requirement should be there for this, otherwise, without
> > authentication, the MN can "get at" any context, or context feature
> that its
> > not authorized access to.
> >
> > How about:
> >
> >                 There MUST be mutual authentication between the MN
and
> its
> > context, after the context transfer has occurred.
> >
> > -Sharif.
> >
> > -----Original Message-----
> > From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> > Sent: Tuesday, November 13, 2001 11:07 AM
> > To: 'Shahrier, Sharif M.'
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> > Sharif:
> >
> >   This requirement is for the ARs to authenticate each other so that
a
> ct
> > exchange can
> > be trusted. It has nothing to do with the MN and handoff per se.
> >
> > Gary
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: November 13, 2001 09:51
> > To: Shahrier, Sharif M.
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> >
> > I have some issues with the following requirement in the CT draft.
> >
> > 4.9 The entities transferring context MUST have completed a mutual
> > authentication process prior to
> >       initiating the transfer.
> >
> > I don't support this requirement.
> >
> > It appears to me this may not fit the case for "break-before-make"
> handover
> > .  For instance, the mobile may break connection with the old
> > AP, and re-establish connection with the new AP.
> >
> > Assuming that the context is transferred prior to re-establishing
the
> new
> > connection.
> >
> > The mobile will need to re-authenticate after it makes a new
> connection at
> > its new AP.
> >
> > I have seen several practical cases that supports this scanario,
thus
> I feel
> > it is necessary for authentication after the transfer of context
> > in "break-before-make".
> >
> > -Sharif.
> >
>



From owner-seamoby@diameter.org  Wed Nov 14 14:30:11 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13026
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 14:30:05 -0500 (EST)
Received: (qmail 12169 invoked by alias); 14 Nov 2001 20:14:34 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 12163 invoked by uid 200); 14 Nov 2001 20:14:34 -0000
Received: (qmail 12158 invoked from network); 14 Nov 2001 20:14:31 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 20:14:31 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095FJC>; Wed, 14 Nov 2001 14:25:09 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A1@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 14:25:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

James,

James,

I don't disagree that protocols developed within the IETF should be focused
on the Internet, as that is the main charter of the IETF. 
However, I do think that in the wider interests of global harmonization with
other networks, the IETF's protocols should interwork with them. 

[In fact, I have noted that many companies are currently using Mobile IP to
interconnect many different types of networks.]

Thus, it was good to note that the CT requirements draft contained:

4.15 "The context transfer solution MAY include methods for interworking
with non-IETF mobility solution".

In the same notion, I had proposed that:

"The context transfer solution MAY include methods for interworking with
non-IETF handover solutions."

I hope that people will agree.

Thanks.

-Sharif.


 -----Original Message-----
From: 	James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent:	Wednesday, November 14, 2001 1:58 PM
To:	Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Gary Kenward;
Shahrier, Sharif M.
Cc:	seamoby@cdma-2000.org
Subject:	Re: [seamoby] Some proposed changes to the requirements
draft.

Kamel,

This issue came up last spring. The IETF is specifically concerned with
standards for the Internet, it is the Standards Development Organization
(SDO) for the Internet. Working groups can consider the experience of
other standards development organizations when developing Internet
standards, that is simple common sense and good engineering practice. We
can also consider the needs of othe standards bodies for Internet
standards, just as we consider the needs of companies and individuals.
But any requirements or protocols we develop should be focused on the
Internet, not on standards developed by other standards bodies.

Hope that's clear.

            jak

----- Original Message -----
From: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>; "'James
Kempf'" <kempf@docomolabs-usa.com>; "Gary Kenward"
<gkenward@nortelnetworks.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "Shaheen, Kamel M."
<Kamel.Shaheen@InterDigital.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 10:45 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> I would respectfully disagree.  I think it would be beneficial to this
work
> to understand and to take previous work into consideration (not
necessarily
> to duplicate) if we would like wider acceptance and more generalized
> solution.  Specially given the current drive toward global more
harmonized
> kind of interworking.
>
> Regards,
>
> Kamel
>
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Wed, November 14, 2001 1:34 PM
> To: 'James Kempf'; Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel
> M.; Nakhjiri Madjid-MNAKHJI1
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Thanks,
>
> I agree. Our requirements can't look like UMTS requirements.
>
> The UMTS/ GPRS need for context transfer is definitely
>  a topic of interest, BUT in a separate ID. I will look forward to
reading
> it.
>
> Madjid
>
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, November 14, 2001 11:32 AM
> To: Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri
> Madjid-MNAKHJI1'
> Cc: seamoby@cdma-2000.org
> Subject: Re: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Gary/Sharif,
>
> I certainly agree that we should not be tayloring our requirements for
> existing UMTS/GPRS networks. The requirements should define the
> properties of a desirable solution for the Internet.
>
> Regarding the specific requirement, about authentication, as Majhid
> indicated, the thread is closed. CT happens between ARs or other
> entities involved in routing in the wired network. The MN isn't
> involved. If you look at the problem statement (the latest draft of
> which is on my disk ready to go), that's how it is defined. So the
> authentication involved is between ARs.
>
>             jak
>
> ----- Original Message -----
> From: "Gary Kenward" <gkenward@nortelnetworks.com>
> To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
> "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
> Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Wednesday, November 14, 2001 7:40 AM
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> > Sharif:
> >
> >    One thing that I am pretty sure Seamoby is not going to get into,
> is
> > exploring the world of
> > internetwork authentication. CT needs it, yes, but will Seamoby be
> defining
> > the solution?
> > As far as I know, it's not in our charter. Just as defining new
> security
> > protocols for CT was
> > place out of scope very early on in the discussions.
> >
> >   You have valid points, many were discussed last spring. It doesn't
> hurt to
> > revisit issues, for
> > we are constantly expanding our understanding of this problem domain
> (or, at
> > least I hope so).
> > However, in my delusional view, we all need some real solution
> proposals to
> > chew on in order to
> > really progress.
> >
> >   I realize that for you, the situation is very different. You have
a
> real
> > system with real issues
> > to resolve. It is only one of many networks however, and perhaps a
> better
> > way to get the wg up
> > to speed on the specific requirements of UMTS (and other networks)
is
> to
> > schedule some presentations
> > at the next IETF on existing context transfer problems/solutions.
What
> say
> > you Pat and James?
> >
> > Gary
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: November 14, 2001 09:52
> > To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> > [WDLN2:AN10:EXCH]
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> >
> > Majid,
> >
> >             To add to points Kamel had made, I would also like to
add
> > another point.
> >
> >             Given that there is a trust relationship between AR's in
a
> > specific domain, where there is no need for authorization. If the MN
> then
> > were to "roam" to a different administrative domain, where there may
> be no
> > trust relationship between the AR's in the previous domain and the
new
> > domain, how does the target AR in the new domain ensure that it is
> using the
> > right context to serve the right MN?
> >
> > -Sharif.
> >
> > -----Original Message-----
> > From: Shaheen, Kamel M.
> > Sent: Wednesday, November 14, 2001 9:36 AM
> > To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> > Madjid,
> >
> > I have some questions for clarifications.  First and before going
into
> the
> > details, I would like to understand the focus of the work.  Is it
only
> > concentrated on the context transfer?  or It involves the hooks that
> are
> > necessary to ensure that right contexts are at the right ARs serving
> the
> > right MNs?
> >
> > I would agree with you that the authentication will take place
between
> the
> > ARs before any CT takes place, may be as in wireless environment
there
> is a
> > trust relationship between certain ARs where there is no need for
> > authorization.
> >
> > However, if the MN is not involved in the CT.  How does the target
AR
> ensure
> > that it is using the right context to serve the right MN?
> >
> > Regards,
> >
> > Kamel
> > -----Original Message-----
> > From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> > Sent: Tue, November 13, 2001 7:42 PM
> > To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Sherif,
> >
> > First I think the chairs closed this thread. Authentication has to
> happen
> > between ARs, since
> > CT happens between ARs. If the MN was supposed to be involved in
> context
> > reestablishment,
> > we wouldn't be here in the first place.
> > Second, there are a lot of things that can go wrong with CT, and
> failed
> > authentication is one
> > of them. Reliability for CT and the backup mechanisms for CT are
still
> open
> > issues, but for sure
> > a failed authentication at MN is not one of these issues and here is
> why:
> >
> > after the two ARs have authenticated themselves to each other (maybe
> once
> > for all or maybe
> > before a CT, I don't inject my opinion here), then they engage in
CT.
> The CT
> > data can be
> > authenticated if necessary. The receiving AR, will check the
> authentication
> > of context data.
> >
> > Architecture-wise, this is the only way to do it,  based on the fact
> that
> > only ARs do CT.
> > And MN is not in this picture.
> >
> > Hope this clears things out.
> > Madjid
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: Tuesday, November 13, 2001 3:17 PM
> > To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Majid,
> >
> >             Consider the case where the context transfer occurs
before
> > handover. So, the context will arrive at the newAR before
> >             The mobile node does. What if something goes wrong - the
> context
> > is not correctly received by the newAR.
> >             When the MN arrives at the newAR, it needs to know this
> fact.
> > So, the MN should authenticate the received context, just
> >             To make sure that its context was successfully received
by
> the
> > newAR.
> >
> > -Sharif.
> >
> > Maybe you mean that the MN should authenticate the received context
> data,
> > but
> > then why does the MN should do this. The context is going to the new
> AR,
> > anyway.
> > If authentication of data is needed, new AR does it on behalf of MN.
> >
> > Why are we dragging MN into the authentication process.
> >
> > these issues are attacking the basic framework of CT, IMHO
> >
> > Madjid
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: Tuesday, November 13, 2001 10:44 AM
> > To: 'Gary Kenward'; Shahrier, Sharif M.
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> > Gary,
> >
> >                 Understood. However, the requirements contains
nothing
> (?)
> > about the mobile authenticating with its context, after the context
> > Has been transferred.
> >
> > I think a requirement should be there for this, otherwise, without
> > authentication, the MN can "get at" any context, or context feature
> that its
> > not authorized access to.
> >
> > How about:
> >
> >                 There MUST be mutual authentication between the MN
and
> its
> > context, after the context transfer has occurred.
> >
> > -Sharif.
> >
> > -----Original Message-----
> > From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> > Sent: Tuesday, November 13, 2001 11:07 AM
> > To: 'Shahrier, Sharif M.'
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> > Sharif:
> >
> >   This requirement is for the ARs to authenticate each other so that
a
> ct
> > exchange can
> > be trusted. It has nothing to do with the MN and handoff per se.
> >
> > Gary
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: November 13, 2001 09:51
> > To: Shahrier, Sharif M.
> > Cc: 'seamoby@cdma-2000.org'
> > Subject: RE: [seamoby] Some proposed changes to the requirements
> draft.
> >
> >
> > I have some issues with the following requirement in the CT draft.
> >
> > 4.9 The entities transferring context MUST have completed a mutual
> > authentication process prior to
> >       initiating the transfer.
> >
> > I don't support this requirement.
> >
> > It appears to me this may not fit the case for "break-before-make"
> handover
> > .  For instance, the mobile may break connection with the old
> > AP, and re-establish connection with the new AP.
> >
> > Assuming that the context is transferred prior to re-establishing
the
> new
> > connection.
> >
> > The mobile will need to re-authenticate after it makes a new
> connection at
> > its new AP.
> >
> > I have seen several practical cases that supports this scanario,
thus
> I feel
> > it is necessary for authentication after the transfer of context
> > in "break-before-make".
> >
> > -Sharif.
> >
>


From owner-seamoby@diameter.org  Wed Nov 14 15:02:57 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14240
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 15:02:56 -0500 (EST)
Received: (qmail 13047 invoked by alias); 14 Nov 2001 20:49:43 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13041 invoked by uid 200); 14 Nov 2001 20:49:43 -0000
Received: (qmail 13036 invoked from network); 14 Nov 2001 20:49:40 -0000
Received: from softdnserror (HELO meshpdc.meshnetworks.com) (205.245.27.196)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 20:49:40 -0000
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)
	id <WN1MSCNR>; Wed, 14 Nov 2001 15:01:44 -0500
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E04861662B@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@MeshNetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        Gary Kenward <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 15:01:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Shahrier,

In the formative months of SeaMoby we were bandying about the
notion of heterogeneous handovers, i.e.  how would one perform
an IP friendly handover from IS-95 to Bluetooth or 802.11b for
example.  This was written out of the SeaMoby charter by the
IESG.  I think it is still  a noble goal.  However, I am not
sure how practical it is anymore.  In retrospect that was 
probably a bit too idealistic proposition.

Also, I have come around to recognize the importance of an
abstract CT mechanism that improves mobile IP handovers that
remains as radio agnostic as possible.  Not sure if this make
YOU feel any better though.... :-)

Best regards,

Phil

> I don't disagree that protocols developed within the IETF 
> should be focused
> on the Internet, as that is the main charter of the IETF. 
> However, I do think that in the wider interests of global 
> harmonization with
> other networks, the IETF's protocols should interwork with them. 
> 
> [In fact, I have noted that many companies are currently 
> using Mobile IP to
> interconnect many different types of networks.]
> 
> Thus, it was good to note that the CT requirements draft contained:
> 
> 4.15 "The context transfer solution MAY include methods for 
> interworking
> with non-IETF mobility solution".
> 
> In the same notion, I had proposed that:
> 
> "The context transfer solution MAY include methods for 
> interworking with
> non-IETF handover solutions."
> 
> I hope that people will agree.
> 

****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures. 


From owner-seamoby@diameter.org  Wed Nov 14 15:14:53 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14630
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 15:14:47 -0500 (EST)
Received: (qmail 13734 invoked by alias); 14 Nov 2001 20:59:43 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13728 invoked by uid 200); 14 Nov 2001 20:59:43 -0000
Received: (qmail 13722 invoked from network); 14 Nov 2001 20:59:40 -0000
Received: from motgate3.mot.com (144.189.100.103)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 20:59:40 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate3.mot.com (motgate3 2.1) with ESMTP id NAA18772 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 13:02:41 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id NAA11957 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 13:02:12 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <WTNG4RY9>; Wed, 14 Nov 2001 14:11:50 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB30@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shaheen, Kamel M.'" <Kamel.Shaheen@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 14:11:48 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I guess I owe you a correction, instead of 

"Our requirements can't look like UMTS requirements"

I should say, "we cannot comply with UMTS requirements only and
forget everything else" what about
CDMA2000 or 802.11a/b or hyperlan?

I second James comments on this. I invite you to write a draft
on UMTS requirements and inform us about them, so we can make
better generic protocols. I personally am very interested to 
make CT, UMTS friendly, A draft would be a good start :)

Madjid



-----Original Message-----
From: Shaheen, Kamel M. [mailto:Kamel.Shaheen@InterDigital.com]
Sent: Wednesday, November 14, 2001 12:45 PM
To: 'Nakhjiri Madjid-MNAKHJI1'; 'James Kempf'; Gary Kenward; Shahrier,
Sharif M.; Shaheen, Kamel M.
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


I would respectfully disagree.  I think it would be beneficial to this work
to understand and to take previous work into consideration (not necessarily
to duplicate) if we would like wider acceptance and more generalized
solution.  Specially given the current drive toward global more harmonized
kind of interworking.

Regards,

Kamel 

-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Wed, November 14, 2001 1:34 PM
To: 'James Kempf'; Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel
M.; Nakhjiri Madjid-MNAKHJI1
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Thanks, 

I agree. Our requirements can't look like UMTS requirements.

The UMTS/ GPRS need for context transfer is definitely
 a topic of interest, BUT in a separate ID. I will look forward to reading
it.

Madjid


-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wednesday, November 14, 2001 11:32 AM
To: Gary Kenward; 'Shahrier, Sharif M.'; Shaheen, Kamel M.; 'Nakhjiri
Madjid-MNAKHJI1'
Cc: seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.


Gary/Sharif,

I certainly agree that we should not be tayloring our requirements for
existing UMTS/GPRS networks. The requirements should define the
properties of a desirable solution for the Internet.

Regarding the specific requirement, about authentication, as Majhid
indicated, the thread is closed. CT happens between ARs or other
entities involved in routing in the wired network. The MN isn't
involved. If you look at the problem statement (the latest draft of
which is on my disk ready to go), that's how it is defined. So the
authentication involved is between ARs.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
"Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>; "'Nakhjiri
Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 7:40 AM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Sharif:
>
>    One thing that I am pretty sure Seamoby is not going to get into,
is
> exploring the world of
> internetwork authentication. CT needs it, yes, but will Seamoby be
defining
> the solution?
> As far as I know, it's not in our charter. Just as defining new
security
> protocols for CT was
> place out of scope very early on in the discussions.
>
>   You have valid points, many were discussed last spring. It doesn't
hurt to
> revisit issues, for
> we are constantly expanding our understanding of this problem domain
(or, at
> least I hope so).
> However, in my delusional view, we all need some real solution
proposals to
> chew on in order to
> really progress.
>
>   I realize that for you, the situation is very different. You have a
real
> system with real issues
> to resolve. It is only one of many networks however, and perhaps a
better
> way to get the wg up
> to speed on the specific requirements of UMTS (and other networks) is
to
> schedule some presentations
> at the next IETF on existing context transfer problems/solutions. What
say
> you Pat and James?
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 14, 2001 09:52
> To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
> [WDLN2:AN10:EXCH]
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> Majid,
>
>             To add to points Kamel had made, I would also like to add
> another point.
>
>             Given that there is a trust relationship between AR's in a
> specific domain, where there is no need for authorization. If the MN
then
> were to "roam" to a different administrative domain, where there may
be no
> trust relationship between the AR's in the previous domain and the new
> domain, how does the target AR in the new domain ensure that it is
using the
> right context to serve the right MN?
>
> -Sharif.
>
> -----Original Message-----
> From: Shaheen, Kamel M.
> Sent: Wednesday, November 14, 2001 9:36 AM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Madjid,
>
> I have some questions for clarifications.  First and before going into
the
> details, I would like to understand the focus of the work.  Is it only
> concentrated on the context transfer?  or It involves the hooks that
are
> necessary to ensure that right contexts are at the right ARs serving
the
> right MNs?
>
> I would agree with you that the authentication will take place between
the
> ARs before any CT takes place, may be as in wireless environment there
is a
> trust relationship between certain ARs where there is no need for
> authorization.
>
> However, if the MN is not involved in the CT.  How does the target AR
ensure
> that it is using the right context to serve the right MN?
>
> Regards,
>
> Kamel
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Tue, November 13, 2001 7:42 PM
> To: 'Shahrier, Sharif M.'; Nakhjiri Madjid-MNAKHJI1; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Sherif,
>
> First I think the chairs closed this thread. Authentication has to
happen
> between ARs, since
> CT happens between ARs. If the MN was supposed to be involved in
context
> reestablishment,
> we wouldn't be here in the first place.
> Second, there are a lot of things that can go wrong with CT, and
failed
> authentication is one
> of them. Reliability for CT and the backup mechanisms for CT are still
open
> issues, but for sure
> a failed authentication at MN is not one of these issues and here is
why:
>
> after the two ARs have authenticated themselves to each other (maybe
once
> for all or maybe
> before a CT, I don't inject my opinion here), then they engage in CT.
The CT
> data can be
> authenticated if necessary. The receiving AR, will check the
authentication
> of context data.
>
> Architecture-wise, this is the only way to do it,  based on the fact
that
> only ARs do CT.
> And MN is not in this picture.
>
> Hope this clears things out.
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 3:17 PM
> To: 'Nakhjiri Madjid-MNAKHJI1'; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Majid,
>
>             Consider the case where the context transfer occurs before
> handover. So, the context will arrive at the newAR before
>             The mobile node does. What if something goes wrong - the
context
> is not correctly received by the newAR.
>             When the MN arrives at the newAR, it needs to know this
fact.
> So, the MN should authenticate the received context, just
>             To make sure that its context was successfully received by
the
> newAR.
>
> -Sharif.
>
> Maybe you mean that the MN should authenticate the received context
data,
> but
> then why does the MN should do this. The context is going to the new
AR,
> anyway.
> If authentication of data is needed, new AR does it on behalf of MN.
>
> Why are we dragging MN into the authentication process.
>
> these issues are attacking the basic framework of CT, IMHO
>
> Madjid
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Tuesday, November 13, 2001 10:44 AM
> To: 'Gary Kenward'; Shahrier, Sharif M.
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
> Gary,
>
>                 Understood. However, the requirements contains nothing
(?)
> about the mobile authenticating with its context, after the context
> Has been transferred.
>
> I think a requirement should be there for this, otherwise, without
> authentication, the MN can "get at" any context, or context feature
that its
> not authorized access to.
>
> How about:
>
>                 There MUST be mutual authentication between the MN and
its
> context, after the context transfer has occurred.
>
> -Sharif.
>
> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Tuesday, November 13, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
> Sharif:
>
>   This requirement is for the ARs to authenticate each other so that a
ct
> exchange can
> be trusted. It has nothing to do with the MN and handoff per se.
>
> Gary
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 13, 2001 09:51
> To: Shahrier, Sharif M.
> Cc: 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
> I have some issues with the following requirement in the CT draft.
>
> 4.9 The entities transferring context MUST have completed a mutual
> authentication process prior to
>       initiating the transfer.
>
> I don't support this requirement.
>
> It appears to me this may not fit the case for "break-before-make"
handover
> .  For instance, the mobile may break connection with the old
> AP, and re-establish connection with the new AP.
>
> Assuming that the context is transferred prior to re-establishing the
new
> connection.
>
> The mobile will need to re-authenticate after it makes a new
connection at
> its new AP.
>
> I have seen several practical cases that supports this scanario, thus
I feel
> it is necessary for authentication after the transfer of context
> in "break-before-make".
>
> -Sharif.
>


From owner-seamoby@diameter.org  Wed Nov 14 15:21:38 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15022
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 15:21:35 -0500 (EST)
Received: (qmail 14255 invoked by alias); 14 Nov 2001 21:06:41 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 14249 invoked by uid 200); 14 Nov 2001 21:06:40 -0000
Received: (qmail 14240 invoked from network); 14 Nov 2001 21:06:36 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 21:06:36 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095FP7>; Wed, 14 Nov 2001 15:17:11 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D02D81274@idcpa4.pa.interdigital.com>
From: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
To: "'Phillip Neumiller'" <PNeumiller@MeshNetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        Gary Kenward <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 15:17:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Phil,

In 3GPP, there is a WI for interworking between UMTS and HIPERLAN/802.11 and
the work has already started with several proposals on the table. This
effort (WI) has been pushed mainly by the service provider.  I am assuming
that a similar push is in the work for IS-95/3GPP2 (I am not sure though!).


The current practice in UMTS (3GPP)is to refer to IETF RFCs and I am sure
the practice will continue if such RFC (potential RFC) exists for context
transfer.

Regards,

Kamel 

-----Original Message-----
From: Phillip Neumiller [mailto:PNeumiller@MeshNetworks.com]
Sent: Wed, November 14, 2001 3:02 PM
To: 'Shahrier, Sharif M.'; 'James Kempf'; Shaheen, Kamel M.; 'Nakhjiri
Madjid-MNAKHJI1'; Gary Kenward
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hi Shahrier,

In the formative months of SeaMoby we were bandying about the
notion of heterogeneous handovers, i.e.  how would one perform
an IP friendly handover from IS-95 to Bluetooth or 802.11b for
example.  This was written out of the SeaMoby charter by the
IESG.  I think it is still  a noble goal.  However, I am not
sure how practical it is anymore.  In retrospect that was 
probably a bit too idealistic proposition.

Also, I have come around to recognize the importance of an
abstract CT mechanism that improves mobile IP handovers that
remains as radio agnostic as possible.  Not sure if this make
YOU feel any better though.... :-)

Best regards,

Phil

> I don't disagree that protocols developed within the IETF 
> should be focused
> on the Internet, as that is the main charter of the IETF. 
> However, I do think that in the wider interests of global 
> harmonization with
> other networks, the IETF's protocols should interwork with them. 
> 
> [In fact, I have noted that many companies are currently 
> using Mobile IP to
> interconnect many different types of networks.]
> 
> Thus, it was good to note that the CT requirements draft contained:
> 
> 4.15 "The context transfer solution MAY include methods for 
> interworking
> with non-IETF mobility solution".
> 
> In the same notion, I had proposed that:
> 
> "The context transfer solution MAY include methods for 
> interworking with
> non-IETF handover solutions."
> 
> I hope that people will agree.
> 

****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures. 


From owner-seamoby@diameter.org  Wed Nov 14 16:50:31 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18097
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 16:50:30 -0500 (EST)
Received: (qmail 16146 invoked by alias); 14 Nov 2001 22:18:42 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 16138 invoked by uid 200); 14 Nov 2001 22:18:41 -0000
Received: (qmail 16078 invoked from network); 14 Nov 2001 22:18:14 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 22:18:14 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095FZ3>; Wed, 14 Nov 2001 16:28:53 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A2@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: [seamoby] CT requirements
Date: Wed, 14 Nov 2001 16:28:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Everyone:

	There hasn't been any "consensus" against the requirements that I'm
indicating below. There had been a couple of comments, to which I responded,
but I did not get anything back.

I would like to point them out again, and if there is no real WG consensus
against them, I see no reason why they should not be in the CT requirements
draft.

5.5.2 A context update MUST preserve the integrity, and thus the meaning, of
the context at each receiving AR.

   The context at the AR actually supporting an MN's traffic will change
with time. For example, the MN may initiate new microflow(s),
   or discontinue existing microflows. Any change of context at the
supporting AR must be replicated at those ARs that have already
   received context for that MN.

   I don't see what the paragraph above has to do with data integrity, and
thus I recommend that it should be rewritten or removed altogether. Unless I
am wrong, I had thought that data integrity refers to the "correctness" of
data.

4.17 "The context transfer protocol MUST minimize the number of 
       signaling messages at the sending and receiving Access Routers".


Minimizing signaling messages have several benefits: (a) reduces load on the
Internet by signaling messages, (b) increases the bandwidth afforded to data
traffic, (c) improves the effective utilization of data traffic, (d)
improves reliability, (e) improves scalability.

I've seen one comment on this, but did not get a response after I replied.

Now, the centralized/local context storage caused some issues. Thus, I would
like to re-word it and hope that it would be more acceptable.

The context transfer protocol MUST support localized storage of context at
the ARs.

The context transfer protocol MAY also support a centralized storage of
context belonging to  the ARs in the sub-net.

I think that keeping a "back up" of context information in a central
directory will help will fault-tolerence, i.e. reliability, and it provides
consistency with some of the current implementations in wireless networks.
It also broadens the solution space ............

5.6.1 "The context transfer protocol MUST include methods for interworking
with any IETF IP handover solutions".

The IETF have several handover solutions, and unless the objective is to
come up with a different context transfer solution to fit a specific
handover protocol, it should make sense to include this requirement.

Personally, I think it is good practice to have a single CT solution and
design it for the worst-case.


	-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 18:02:01 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20659
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 18:02:00 -0500 (EST)
Received: (qmail 18804 invoked by alias); 14 Nov 2001 23:48:11 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 18798 invoked by uid 200); 14 Nov 2001 23:48:11 -0000
Received: (qmail 18793 invoked from network); 14 Nov 2001 23:48:09 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 23:48:09 -0000
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (motgate2 2.1) with ESMTP id QAA08530 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 16:00:18 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id QAA21438 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 16:00:18 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <4K0CAPGH>; Wed, 14 Nov 2001 17:00:18 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB32@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shaheen, Kamel M.'" <Kamel.Shaheen@InterDigital.com>,
        "'Phillip Neumiller'" <PNeumiller@MeshNetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        Gary Kenward <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 17:00:17 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kamel,

Could you send me the WI description or the document. I am interested
in knowing what is out there in 3GPP.

Well, there are 2 problems here:

1-CT does not have a solution RFC.
2-I feel that the differences between definitions of
context in 3GPP and IETF needs to be hashed out, so 
we make sure we talk about the same thing, when we say
"context" (I will talk about it in my email to Sherif).

Madjid

-----Original Message-----
From: Shaheen, Kamel M. [mailto:Kamel.Shaheen@InterDigital.com]
Sent: Wednesday, November 14, 2001 2:17 PM
To: 'Phillip Neumiller'; Shahrier, Sharif M.; 'James Kempf'; Shaheen,
Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Gary Kenward
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hi Phil,

In 3GPP, there is a WI for interworking between UMTS and HIPERLAN/802.11 and
the work has already started with several proposals on the table. This
effort (WI) has been pushed mainly by the service provider.  I am assuming
that a similar push is in the work for IS-95/3GPP2 (I am not sure though!).


The current practice in UMTS (3GPP)is to refer to IETF RFCs and I am sure
the practice will continue if such RFC (potential RFC) exists for context
transfer.

Regards,

Kamel 

-----Original Message-----
From: Phillip Neumiller [mailto:PNeumiller@MeshNetworks.com]
Sent: Wed, November 14, 2001 3:02 PM
To: 'Shahrier, Sharif M.'; 'James Kempf'; Shaheen, Kamel M.; 'Nakhjiri
Madjid-MNAKHJI1'; Gary Kenward
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


Hi Shahrier,

In the formative months of SeaMoby we were bandying about the
notion of heterogeneous handovers, i.e.  how would one perform
an IP friendly handover from IS-95 to Bluetooth or 802.11b for
example.  This was written out of the SeaMoby charter by the
IESG.  I think it is still  a noble goal.  However, I am not
sure how practical it is anymore.  In retrospect that was 
probably a bit too idealistic proposition.

Also, I have come around to recognize the importance of an
abstract CT mechanism that improves mobile IP handovers that
remains as radio agnostic as possible.  Not sure if this make
YOU feel any better though.... :-)

Best regards,

Phil

> I don't disagree that protocols developed within the IETF 
> should be focused
> on the Internet, as that is the main charter of the IETF. 
> However, I do think that in the wider interests of global 
> harmonization with
> other networks, the IETF's protocols should interwork with them. 
> 
> [In fact, I have noted that many companies are currently 
> using Mobile IP to
> interconnect many different types of networks.]
> 
> Thus, it was good to note that the CT requirements draft contained:
> 
> 4.15 "The context transfer solution MAY include methods for 
> interworking
> with non-IETF mobility solution".
> 
> In the same notion, I had proposed that:
> 
> "The context transfer solution MAY include methods for 
> interworking with
> non-IETF handover solutions."
> 
> I hope that people will agree.
> 

****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures. 


From owner-seamoby@diameter.org  Wed Nov 14 18:10:28 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20846
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 18:10:27 -0500 (EST)
Received: (qmail 19377 invoked by alias); 14 Nov 2001 23:57:15 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 19371 invoked by uid 200); 14 Nov 2001 23:57:15 -0000
Received: (qmail 19366 invoked from network); 14 Nov 2001 23:57:13 -0000
Received: from ftpbox.mot.com (129.188.136.101)
  by c900656-a.plstn1.sfba.home.com with SMTP; 14 Nov 2001 23:57:13 -0000
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id QAA18593 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 16:09:23 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id PAA03702 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 15:59:45 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8NKD3>; Wed, 14 Nov 2001 17:09:22 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB33@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        john.loughney@nokia.com, kempf@docomolabs-usa.com,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 17:09:22 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Ok, It is clear that storage issue is out of scope. So I am 
not going to debate on central versus localized context, that
would be a specific issue for UMTS to solve if part of "context"
is at SGSN and part of it in GGSN (which are both edge routers essentially,
pointing at different edges of GPRS network, i.e. radio versus internet).

What troubles me is that although I don't know much about UMTS and PDP,
I have a feeling that PDP contexts are not quite the same as feature
contexts that we are talking about here in IETF. PDP contexts are more like
links than protocol states. You set up a virtual link, 
you activate a PDP context. You talk about prefix per PDP context and 
interface identifier per PDP context.... 

So we have an incompatibility in definition of "context" when we talk about
"context transfer" in IETF and 3GPP. and the concepts are not "transferable"!!
Am I not correct?

Regards,
Madjid

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Wednesday, November 14, 2001 8:32 AM
To: 'Nakhjiri Madjid-MNAKHJI1'; john.loughney@nokia.com;
kempf@docomolabs-usa.com; Shahrier, Sharif M.; seamoby@cdma-2000.org
Cc: Shahrier, Sharif M.
Subject: RE: [seamoby] Some proposed changes to the requirements draft.



The centralized approach to context transfer was dismissed
very early on. Is this still an issues?


For 5.6.2 I am not quite sure if some non-IETF protocols even
have the same definition for context as we do (PDP context is one
example), any idea??

Majid,

	The PDP context is used in the UMTS systems. A "global" PDP context
resides in the GGSN, and a "local" PDP context resides at each SGSN. The
context parameters at each SGSN is a subset of all those stored at the GGSN.
The MN's, of course, are attached to the SGSNs and send their datagrams to
the GGSN via the GTP (Generic Tunnel Protocol). 

Thus, the GGSN maintains a "central" context directory, while the SGSNs each
maintain a "local" context directory. 

The UMTS system is slated to use the IPv6 protocol, and hopefully, a lot of
the protocols that we develop in the IETF will find its way into this
architecture.

Aside from the UMTS, there are other wireless systems that will use context
transfer protocols with a combination of local/centralized directory
structure.

With this viewpoint, I strongly believe that the context transfer protocol
should support a combination of local and central context memory.

-Sharif.


From owner-seamoby@diameter.org  Wed Nov 14 18:14:47 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20907
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 18:14:44 -0500 (EST)
Received: (qmail 19935 invoked by alias); 15 Nov 2001 00:01:30 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 19929 invoked by uid 200); 15 Nov 2001 00:01:29 -0000
Received: (qmail 19924 invoked from network); 15 Nov 2001 00:01:28 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 00:01:28 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAEND4511193;
	Wed, 14 Nov 2001 15:13:04 -0800 (PST)
Message-ID: <02ca01c16d61$aff3cb90$cc6ffea9@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9A2@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] CT requirements
Date: Wed, 14 Nov 2001 15:11:27 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

With the exception of 5.6.1, I am opposed to the other requirements.

        jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 1:28 PM
Subject: [seamoby] CT requirements


> Everyone:
>
> There hasn't been any "consensus" against the requirements that I'm
> indicating below. There had been a couple of comments, to which I
responded,
> but I did not get anything back.
>
> I would like to point them out again, and if there is no real WG
consensus
> against them, I see no reason why they should not be in the CT
requirements
> draft.
>
> 5.5.2 A context update MUST preserve the integrity, and thus the
meaning, of
> the context at each receiving AR.
>
>    The context at the AR actually supporting an MN's traffic will
change
> with time. For example, the MN may initiate new microflow(s),
>    or discontinue existing microflows. Any change of context at the
> supporting AR must be replicated at those ARs that have already
>    received context for that MN.
>
>    I don't see what the paragraph above has to do with data integrity,
and
> thus I recommend that it should be rewritten or removed altogether.
Unless I
> am wrong, I had thought that data integrity refers to the
"correctness" of
> data.
>
> 4.17 "The context transfer protocol MUST minimize the number of
>        signaling messages at the sending and receiving Access
Routers".
>
>
> Minimizing signaling messages have several benefits: (a) reduces load
on the
> Internet by signaling messages, (b) increases the bandwidth afforded
to data
> traffic, (c) improves the effective utilization of data traffic, (d)
> improves reliability, (e) improves scalability.
>
> I've seen one comment on this, but did not get a response after I
replied.
>
> Now, the centralized/local context storage caused some issues. Thus, I
would
> like to re-word it and hope that it would be more acceptable.
>
> The context transfer protocol MUST support localized storage of
context at
> the ARs.
>
> The context transfer protocol MAY also support a centralized storage
of
> context belonging to  the ARs in the sub-net.
>
> I think that keeping a "back up" of context information in a central
> directory will help will fault-tolerence, i.e. reliability, and it
provides
> consistency with some of the current implementations in wireless
networks.
> It also broadens the solution space ............
>
> 5.6.1 "The context transfer protocol MUST include methods for
interworking
> with any IETF IP handover solutions".
>
> The IETF have several handover solutions, and unless the objective is
to
> come up with a different context transfer solution to fit a specific
> handover protocol, it should make sense to include this requirement.
>
> Personally, I think it is good practice to have a single CT solution
and
> design it for the worst-case.
>
>
> -Sharif.
>



From owner-seamoby@diameter.org  Wed Nov 14 18:18:49 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20978
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 18:18:47 -0500 (EST)
Received: (qmail 20512 invoked by alias); 15 Nov 2001 00:05:29 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 20506 invoked by uid 200); 15 Nov 2001 00:05:29 -0000
Received: (qmail 20501 invoked from network); 15 Nov 2001 00:05:27 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 00:05:27 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAENH4511411;
	Wed, 14 Nov 2001 15:17:04 -0800 (PST)
Message-ID: <02ea01c16d62$3f205270$cc6ffea9@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        <john.loughney@nokia.com>, <seamoby@cdma-2000.org>
References: <35DBB8B7AC89D4118E98009027B1009B0464FB33@IL27EXM10.cig.mot.com>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Date: Wed, 14 Nov 2001 15:15:27 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Madjid,

Yes. PDP context is like a PPP context. CT could apply, but we shouldn't
specifically engineer the CT protocol for it.

        jak

----- Original Message -----
From: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>;
"Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>;
<john.loughney@nokia.com>; <kempf@docomolabs-usa.com>;
<seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 3:09 PM
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


> Ok, It is clear that storage issue is out of scope. So I am
> not going to debate on central versus localized context, that
> would be a specific issue for UMTS to solve if part of "context"
> is at SGSN and part of it in GGSN (which are both edge routers
essentially,
> pointing at different edges of GPRS network, i.e. radio versus
internet).
>
> What troubles me is that although I don't know much about UMTS and
PDP,
> I have a feeling that PDP contexts are not quite the same as feature
> contexts that we are talking about here in IETF. PDP contexts are more
like
> links than protocol states. You set up a virtual link,
> you activate a PDP context. You talk about prefix per PDP context and
> interface identifier per PDP context....
>
> So we have an incompatibility in definition of "context" when we talk
about
> "context transfer" in IETF and 3GPP. and the concepts are not
"transferable"!!
> Am I not correct?
>
> Regards,
> Madjid
>
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Wednesday, November 14, 2001 8:32 AM
> To: 'Nakhjiri Madjid-MNAKHJI1'; john.loughney@nokia.com;
> kempf@docomolabs-usa.com; Shahrier, Sharif M.; seamoby@cdma-2000.org
> Cc: Shahrier, Sharif M.
> Subject: RE: [seamoby] Some proposed changes to the requirements
draft.
>
>
>
> The centralized approach to context transfer was dismissed
> very early on. Is this still an issues?
>
>
> For 5.6.2 I am not quite sure if some non-IETF protocols even
> have the same definition for context as we do (PDP context is one
> example), any idea??
>
> Majid,
>
> The PDP context is used in the UMTS systems. A "global" PDP context
> resides in the GGSN, and a "local" PDP context resides at each SGSN.
The
> context parameters at each SGSN is a subset of all those stored at the
GGSN.
> The MN's, of course, are attached to the SGSNs and send their
datagrams to
> the GGSN via the GTP (Generic Tunnel Protocol).
>
> Thus, the GGSN maintains a "central" context directory, while the
SGSNs each
> maintain a "local" context directory.
>
> The UMTS system is slated to use the IPv6 protocol, and hopefully, a
lot of
> the protocols that we develop in the IETF will find its way into this
> architecture.
>
> Aside from the UMTS, there are other wireless systems that will use
context
> transfer protocols with a combination of local/centralized directory
> structure.
>
> With this viewpoint, I strongly believe that the context transfer
protocol
> should support a combination of local and central context memory.
>
> -Sharif.
>



From owner-seamoby@diameter.org  Wed Nov 14 19:06:34 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22234
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Nov 2001 19:06:32 -0500 (EST)
Received: (qmail 21266 invoked by alias); 15 Nov 2001 00:52:02 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21260 invoked by uid 200); 15 Nov 2001 00:52:02 -0000
Received: (qmail 21255 invoked from network); 15 Nov 2001 00:52:00 -0000
Received: from ftpbox.mot.com (129.188.136.101)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 00:52:00 -0000
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id RAA19094 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 17:04:07 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id RAA16787 for <seamoby@cdma-2000.org>; Wed, 14 Nov 2001 17:04:06 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8NLN8>; Wed, 14 Nov 2001 18:04:06 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB3A@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] CT requirements
Date: Wed, 14 Nov 2001 18:04:05 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I second James opinion. 
Furthermore what is referred to as "data integrity" is covered
as reliability in the existing requirement doc (see 4.13).
Maybe it needs to be spelled out??

Madjid



-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wednesday, November 14, 2001 5:11 PM
To: Shahrier, Sharif M.; seamoby@cdma-2000.org
Subject: Re: [seamoby] CT requirements


With the exception of 5.6.1, I am opposed to the other requirements.

        jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <seamoby@cdma-2000.org>
Sent: Wednesday, November 14, 2001 1:28 PM
Subject: [seamoby] CT requirements


> Everyone:
>
> There hasn't been any "consensus" against the requirements that I'm
> indicating below. There had been a couple of comments, to which I
responded,
> but I did not get anything back.
>
> I would like to point them out again, and if there is no real WG
consensus
> against them, I see no reason why they should not be in the CT
requirements
> draft.
>
> 5.5.2 A context update MUST preserve the integrity, and thus the
meaning, of
> the context at each receiving AR.
>
>    The context at the AR actually supporting an MN's traffic will
change
> with time. For example, the MN may initiate new microflow(s),
>    or discontinue existing microflows. Any change of context at the
> supporting AR must be replicated at those ARs that have already
>    received context for that MN.
>
>    I don't see what the paragraph above has to do with data integrity,
and
> thus I recommend that it should be rewritten or removed altogether.
Unless I
> am wrong, I had thought that data integrity refers to the
"correctness" of
> data.
>
> 4.17 "The context transfer protocol MUST minimize the number of
>        signaling messages at the sending and receiving Access
Routers".
>
>
> Minimizing signaling messages have several benefits: (a) reduces load
on the
> Internet by signaling messages, (b) increases the bandwidth afforded
to data
> traffic, (c) improves the effective utilization of data traffic, (d)
> improves reliability, (e) improves scalability.
>
> I've seen one comment on this, but did not get a response after I
replied.
>
> Now, the centralized/local context storage caused some issues. Thus, I
would
> like to re-word it and hope that it would be more acceptable.
>
> The context transfer protocol MUST support localized storage of
context at
> the ARs.
>
> The context transfer protocol MAY also support a centralized storage
of
> context belonging to  the ARs in the sub-net.
>
> I think that keeping a "back up" of context information in a central
> directory will help will fault-tolerence, i.e. reliability, and it
provides
> consistency with some of the current implementations in wireless
networks.
> It also broadens the solution space ............
>
> 5.6.1 "The context transfer protocol MUST include methods for
interworking
> with any IETF IP handover solutions".
>
> The IETF have several handover solutions, and unless the objective is
to
> come up with a different context transfer solution to fit a specific
> handover protocol, it should make sense to include this requirement.
>
> Personally, I think it is good practice to have a single CT solution
and
> design it for the worst-case.
>
>
> -Sharif.
>


From owner-seamoby@diameter.org  Thu Nov 15 01:44:23 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03680
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 01:44:22 -0500 (EST)
Received: (qmail 23841 invoked by alias); 15 Nov 2001 07:27:50 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 23835 invoked by uid 200); 15 Nov 2001 07:27:50 -0000
Received: (qmail 23830 invoked from network); 15 Nov 2001 07:27:47 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 07:27:47 -0000
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAF6ecA26813
	for <seamoby@cdma-2000.org>; Thu, 15 Nov 2001 08:40:39 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T573b9248b0ac158f22077@esvir02nok.nokia.com>;
 Thu, 15 Nov 2001 08:39:57 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <WQAWWGKZ>; Thu, 15 Nov 2001 08:39:57 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D906D@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] CT requirements
Date: Thu, 15 Nov 2001 08:39:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

> With the exception of 5.6.1, I am opposed to the other requirements.

I agree with James.  5.6.1 is OK, the others I oppose.

John


From owner-seamoby@diameter.org  Thu Nov 15 09:23:30 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24710
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 09:23:29 -0500 (EST)
Received: (qmail 25396 invoked by alias); 15 Nov 2001 15:10:30 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 25390 invoked by uid 200); 15 Nov 2001 15:10:30 -0000
Received: (qmail 25385 invoked from network); 15 Nov 2001 15:10:28 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 15:10:28 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095HF0>; Thu, 15 Nov 2001 09:21:09 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A3@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        john.loughney@nokia.com, kempf@docomolabs-usa.com,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Thu, 15 Nov 2001 09:21:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Hello Majid, everyone:

	I don't think the requirements document prevents any solutions from
maintaining a centralized centext storage, as well as a local context
storage at the ARs, is there?

Also, there is nothing to prevent context transfer via a "triangular" route,
i.e. from the oldAR's local context --> to central context database -->
newAR's local context, is there, as per the current requirements document?

-Sharif.

Ok, It is clear that storage issue is out of scope. So I am 
not going to debate on central versus localized context, that
would be a specific issue for UMTS to solve if part of "context"
is at SGSN and part of it in GGSN (which are both edge routers essentially,
pointing at different edges of GPRS network, i.e. radio versus internet).




From owner-seamoby@diameter.org  Thu Nov 15 10:30:38 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28219
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 10:30:34 -0500 (EST)
Received: (qmail 26035 invoked by alias); 15 Nov 2001 16:15:16 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26029 invoked by uid 200); 15 Nov 2001 16:15:16 -0000
Received: (qmail 26024 invoked from network); 15 Nov 2001 16:15:14 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 16:15:14 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAFFQBS01929
	for <seamoby@cdma-2000.org>; Thu, 15 Nov 2001 10:26:11 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 15 Nov 2001 10:23:57 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W329F673>; Thu, 15 Nov 2001 10:20:29 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4657@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] CT requirements
Date: Thu, 15 Nov 2001 10:20:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16DE9.0FF2C320"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16DE9.0FF2C320
Content-Type: text/plain;
	charset="iso-8859-1"

Sharif:

> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 14, 2001 16:29
> To: 'seamoby@cdma-2000.org'
> Subject: [seamoby] CT requirements
> 
> 
> Everyone:
> 

*snip*

> 
> 5.5.2 A context update MUST preserve the integrity, and thus 
> the meaning, of
> the context at each receiving AR.
> 
>    The context at the AR actually supporting an MN's traffic 
> will change
> with time. For example, the MN may initiate new microflow(s),
>    or discontinue existing microflows. Any change of context at the
> supporting AR must be replicated at those ARs that have already
>    received context for that MN.
> 
>    I don't see what the paragraph above has to do with data 
> integrity, and
> thus I recommend that it should be rewritten or removed 
> altogether. Unless I
> am wrong, I had thought that data integrity refers to the 
> "correctness" of
> data.

Define correctness. Then maybe you will understand the meaning
of the paragraph.

> 
> 4.17 "The context transfer protocol MUST minimize the number of 
>        signaling messages at the sending and receiving Access 
> Routers".
> 
> 
> Minimizing signaling messages have several benefits: (a) 
> reduces load on the
> Internet by signaling messages, (b) increases the bandwidth 
> afforded to data
> traffic, (c) improves the effective utilization of data traffic, (d)
> improves reliability, (e) improves scalability.
> 
> I've seen one comment on this, but did not get a response 
> after I replied.

I have no idea what you are proposing here. More words? Is the change
really necessary, or does everyone already understand what the requirement
means and what the benefits are?

> 
> Now, the centralized/local context storage caused some 
> issues. Thus, I would
> like to re-word it and hope that it would be more acceptable.

Not really. The discussions at the beginning of the
year explicitly ruled out a centralized repository or server
approach to ct. There was (as far as I recall) very little support
for a "ct server" type of approach. The preference was for ct to 
be peer to peer.

> 
> The context transfer protocol MUST support localized storage 
> of context at
> the ARs.
> 
> The context transfer protocol MAY also support a centralized 
> storage of
> context belonging to  the ARs in the sub-net.
> 
> I think that keeping a "back up" of context information in a central
> directory will help will fault-tolerence, i.e. reliability, 
> and it provides
> consistency with some of the current implementations in 
> wireless networks.
> It also broadens the solution space ............

It also has absolutely nothing to do with seamlessness. Which is 
why we are here. CT is not about maintaining RABs, etc. it is about
quickly and efficiently re-creating the forwarding support for an
MNs traffic at a new AR. 

> 
> 5.6.1 "The context transfer protocol MUST include methods for 
> interworking
> with any IETF IP handover solutions".
> 
> The IETF have several handover solutions, and unless the 
> objective is to
> come up with a different context transfer solution to fit a specific
> handover protocol, it should make sense to include this requirement.

The requirement for interworking with mobility solutions encompasses
handover.
I realize that over the years people have built up specific connotations of
mobility and handover, but in *english*, mobility means the MN is mobile.

Said in a different manner, if interpretation is that the requirements state
that ct will work with any IETF *mobility* solution but only one *handover*
solution.
Pretty bizarre, don't you think?

> 
> Personally, I think it is good practice to have a single CT 
> solution and
> design it for the worst-case.

The worse case might be AMPs. Or how about mobile radio telephony service.


Gary
> 
> 
> 	-Sharif.
> 

------_=_NextPart_001_01C16DE9.0FF2C320
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [seamoby] CT requirements</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Sharif:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Shahrier, Sharif M. [<A =
HREF=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: November 14, 2001 16:29</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'seamoby@cdma-2000.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [seamoby] CT requirements</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Everyone:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>*snip*</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 5.5.2 A context update MUST preserve the =
integrity, and thus </FONT>
<BR><FONT SIZE=3D2>&gt; the meaning, of</FONT>
<BR><FONT SIZE=3D2>&gt; the context at each receiving AR.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; The context at the AR =
actually supporting an MN's traffic </FONT>
<BR><FONT SIZE=3D2>&gt; will change</FONT>
<BR><FONT SIZE=3D2>&gt; with time. For example, the MN may initiate new =
microflow(s),</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; or discontinue existing =
microflows. Any change of context at the</FONT>
<BR><FONT SIZE=3D2>&gt; supporting AR must be replicated at those ARs =
that have already</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; received context for that =
MN.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; I don't see what the =
paragraph above has to do with data </FONT>
<BR><FONT SIZE=3D2>&gt; integrity, and</FONT>
<BR><FONT SIZE=3D2>&gt; thus I recommend that it should be rewritten or =
removed </FONT>
<BR><FONT SIZE=3D2>&gt; altogether. Unless I</FONT>
<BR><FONT SIZE=3D2>&gt; am wrong, I had thought that data integrity =
refers to the </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;correctness&quot; of</FONT>
<BR><FONT SIZE=3D2>&gt; data.</FONT>
</P>

<P><FONT SIZE=3D2>Define correctness. Then maybe you will understand =
the meaning</FONT>
<BR><FONT SIZE=3D2>of the paragraph.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 4.17 &quot;The context transfer protocol MUST =
minimize the number of </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signaling messages at the sending and receiving Access </FONT>
<BR><FONT SIZE=3D2>&gt; Routers&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Minimizing signaling messages have several =
benefits: (a) </FONT>
<BR><FONT SIZE=3D2>&gt; reduces load on the</FONT>
<BR><FONT SIZE=3D2>&gt; Internet by signaling messages, (b) increases =
the bandwidth </FONT>
<BR><FONT SIZE=3D2>&gt; afforded to data</FONT>
<BR><FONT SIZE=3D2>&gt; traffic, (c) improves the effective utilization =
of data traffic, (d)</FONT>
<BR><FONT SIZE=3D2>&gt; improves reliability, (e) improves =
scalability.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I've seen one comment on this, but did not get =
a response </FONT>
<BR><FONT SIZE=3D2>&gt; after I replied.</FONT>
</P>

<P><FONT SIZE=3D2>I have no idea what you are proposing here. More =
words? Is the change</FONT>
<BR><FONT SIZE=3D2>really necessary, or does everyone already =
understand what the requirement</FONT>
<BR><FONT SIZE=3D2>means and what the benefits are?</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Now, the centralized/local context storage =
caused some </FONT>
<BR><FONT SIZE=3D2>&gt; issues. Thus, I would</FONT>
<BR><FONT SIZE=3D2>&gt; like to re-word it and hope that it would be =
more acceptable.</FONT>
</P>

<P><FONT SIZE=3D2>Not really. The discussions at the beginning of =
the</FONT>
<BR><FONT SIZE=3D2>year explicitly ruled out a centralized repository =
or server</FONT>
<BR><FONT SIZE=3D2>approach to ct. There was (as far as I recall) very =
little support</FONT>
<BR><FONT SIZE=3D2>for a &quot;ct server&quot; type of approach. The =
preference was for ct to </FONT>
<BR><FONT SIZE=3D2>be peer to peer.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The context transfer protocol MUST support =
localized storage </FONT>
<BR><FONT SIZE=3D2>&gt; of context at</FONT>
<BR><FONT SIZE=3D2>&gt; the ARs.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The context transfer protocol MAY also support =
a centralized </FONT>
<BR><FONT SIZE=3D2>&gt; storage of</FONT>
<BR><FONT SIZE=3D2>&gt; context belonging to&nbsp; the ARs in the =
sub-net.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think that keeping a &quot;back up&quot; of =
context information in a central</FONT>
<BR><FONT SIZE=3D2>&gt; directory will help will fault-tolerence, i.e. =
reliability, </FONT>
<BR><FONT SIZE=3D2>&gt; and it provides</FONT>
<BR><FONT SIZE=3D2>&gt; consistency with some of the current =
implementations in </FONT>
<BR><FONT SIZE=3D2>&gt; wireless networks.</FONT>
<BR><FONT SIZE=3D2>&gt; It also broadens the solution space =
............</FONT>
</P>

<P><FONT SIZE=3D2>It also has absolutely nothing to do with =
seamlessness. Which is </FONT>
<BR><FONT SIZE=3D2>why we are here. CT is not about maintaining RABs, =
etc. it is about</FONT>
<BR><FONT SIZE=3D2>quickly and efficiently re-creating the forwarding =
support for an</FONT>
<BR><FONT SIZE=3D2>MNs traffic at a new AR. </FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 5.6.1 &quot;The context transfer protocol MUST =
include methods for </FONT>
<BR><FONT SIZE=3D2>&gt; interworking</FONT>
<BR><FONT SIZE=3D2>&gt; with any IETF IP handover =
solutions&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The IETF have several handover solutions, and =
unless the </FONT>
<BR><FONT SIZE=3D2>&gt; objective is to</FONT>
<BR><FONT SIZE=3D2>&gt; come up with a different context transfer =
solution to fit a specific</FONT>
<BR><FONT SIZE=3D2>&gt; handover protocol, it should make sense to =
include this requirement.</FONT>
</P>

<P><FONT SIZE=3D2>The requirement for interworking with mobility =
solutions encompasses handover.</FONT>
<BR><FONT SIZE=3D2>I realize that over the years people have built up =
specific connotations of</FONT>
<BR><FONT SIZE=3D2>mobility and handover, but in *english*, mobility =
means the MN is mobile.</FONT>
</P>

<P><FONT SIZE=3D2>Said in a different manner, if interpretation is that =
the requirements state</FONT>
<BR><FONT SIZE=3D2>that ct will work with any IETF *mobility* solution =
but only one *handover* solution.</FONT>
<BR><FONT SIZE=3D2>Pretty bizarre, don't you think?</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Personally, I think it is good practice to have =
a single CT </FONT>
<BR><FONT SIZE=3D2>&gt; solution and</FONT>
<BR><FONT SIZE=3D2>&gt; design it for the worst-case.</FONT>
</P>

<P><FONT SIZE=3D2>The worse case might be AMPs. Or how about mobile =
radio telephony service.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Gary</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -Sharif.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16DE9.0FF2C320--


From owner-seamoby@diameter.org  Thu Nov 15 10:37:14 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28596
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 10:37:13 -0500 (EST)
Received: (qmail 26261 invoked by alias); 15 Nov 2001 16:18:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26254 invoked by uid 200); 15 Nov 2001 16:18:25 -0000
Received: (qmail 26248 invoked from network); 15 Nov 2001 16:18:22 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 16:18:22 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAFFTJS02740
	for <seamoby@cdma-2000.org>; Thu, 15 Nov 2001 10:29:19 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Thu, 15 Nov 2001 10:29:33 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W329F7DY>; Thu, 15 Nov 2001 10:26:31 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4658@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Some proposed changes to the requirements draft.
Date: Thu, 15 Nov 2001 10:26:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16DE9.E6D52360"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16DE9.E6D52360
Content-Type: text/plain;
	charset="iso-8859-1"


-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 14, 2001 09:52
To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; Kenward, Gary
[WDLN2:AN10:EXCH]
Cc: 'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Some proposed changes to the requirements draft.


*snip*

However, if the MN is not involved in the CT.  How does the target AR ensure
that it is using the right context to serve the right MN? 

[gwk] It's called the 5-tuple. source address identifies the MN, other
fields identify
the microflow.

If you are concerned about spoofing, etc., that's handled by securing the
transfer process. 
 
Regards,
 
Kamel
-----Original Message--
*snip* *snip* *snip* 

------_=_NextPart_001_01C16DE9.E6D52360
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [seamoby] Some proposed changes to the requirements =
draft.</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Shahrier, Sharif M. [<A =
HREF=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: November 14, 2001 09:52</FONT>
<BR><FONT SIZE=3D2>To: Shaheen, Kamel M.; 'Nakhjiri Madjid-MNAKHJI1'; =
Kenward, Gary [WDLN2:AN10:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: 'seamoby@cdma-2000.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [seamoby] Some proposed changes to the =
requirements draft.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>*snip*</FONT>
</P>

<P><FONT SIZE=3D2>However, if the MN is not involved in the CT.&nbsp; =
How does the target AR ensure that it is using the right context to =
serve the right MN? </FONT></P>

<P><FONT SIZE=3D2>[gwk] It's called the 5-tuple. source address =
identifies the MN, other fields identify</FONT>
<BR><FONT SIZE=3D2>the microflow.</FONT>
</P>

<P><FONT SIZE=3D2>If you are concerned about spoofing, etc., that's =
handled by securing the transfer process. </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Kamel</FONT>
<BR><FONT SIZE=3D2>-----Original Message--</FONT>
<BR><FONT SIZE=3D2>*snip* *snip* *snip* </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16DE9.E6D52360--


From owner-seamoby@diameter.org  Thu Nov 15 10:41:15 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28816
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 10:41:14 -0500 (EST)
Received: (qmail 26322 invoked by alias); 15 Nov 2001 16:19:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26313 invoked by uid 200); 15 Nov 2001 16:19:10 -0000
Received: (qmail 26306 invoked from network); 15 Nov 2001 16:19:07 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 16:19:07 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAFFU6S02893
	for <seamoby@cdma-2000.org>; Thu, 15 Nov 2001 10:30:06 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 15 Nov 2001 10:30:26 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W329F7FG>; Thu, 15 Nov 2001 10:27:40 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4659@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        kempf@docomolabs-usa.com, Sharif.Shahrier@InterDigital.com,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] CT requirements
Date: Thu, 15 Nov 2001 10:27:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16DEA.104DE600"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16DEA.104DE600
Content-Type: text/plain;
	charset="iso-8859-1"

To clarify my previous comment, 5.6.1 is also "ok" in my view, just
not necessary.

gary

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: November 15, 2001 01:40
> To: kempf@docomolabs-usa.com; Sharif.Shahrier@InterDigital.com;
> seamoby@cdma-2000.org
> Subject: RE: [seamoby] CT requirements
> 
> 
> Hi James,
> 
> > With the exception of 5.6.1, I am opposed to the other requirements.
> 
> I agree with James.  5.6.1 is OK, the others I oppose.
> 
> John
> 

------_=_NextPart_001_01C16DEA.104DE600
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [seamoby] CT requirements</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>To clarify my previous comment, 5.6.1 is also &quot;ok&quot; in my view, just</FONT>
<BR><FONT SIZE=2>not necessary.</FONT>
</P>

<P><FONT SIZE=2>gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: john.loughney@nokia.com [<A HREF="mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: November 15, 2001 01:40</FONT>
<BR><FONT SIZE=2>&gt; To: kempf@docomolabs-usa.com; Sharif.Shahrier@InterDigital.com;</FONT>
<BR><FONT SIZE=2>&gt; seamoby@cdma-2000.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] CT requirements</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hi James,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; With the exception of 5.6.1, I am opposed to the other requirements.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I agree with James.&nbsp; 5.6.1 is OK, the others I oppose.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; John</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16DEA.104DE600--


From owner-seamoby@diameter.org  Thu Nov 15 12:11:29 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04886
	for <seamoby-archive@lists.ietf.org>; Thu, 15 Nov 2001 12:11:27 -0500 (EST)
Received: (qmail 27844 invoked by alias); 15 Nov 2001 17:56:41 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27838 invoked by uid 200); 15 Nov 2001 17:56:41 -0000
Received: (qmail 27833 invoked from network); 15 Nov 2001 17:56:39 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 17:56:39 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095HZF>; Thu, 15 Nov 2001 12:07:15 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A4@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] CT requirements
Date: Thu, 15 Nov 2001 12:07:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C16DF7.F53622C0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16DF7.F53622C0
Content-Type: text/plain;
	charset="iso-8859-1"

> 
> Now, the centralized/local context storage caused some 
> issues. Thus, I would 
> like to re-word it and hope that it would be more acceptable. 
Not really. The discussions at the beginning of the 
year explicitly ruled out a centralized repository or server 
approach to ct. There was (as far as I recall) very little support 
for a "ct server" type of approach. The preference was for ct to 
be peer to peer. 
Gary, everyone:
            I was not involved in those discussions, and  thus respectfully
ask to revisit this issue. 
I am not asking, in any way, to remove the mandatory requirement from the
draft for maintaining the context at the AR, for peer to peer context
transfer. I am  simply asking for an "optional" requirement by which there
MAY be a central database for storing the contexts of dormant sessions..
The "optional" clause would not force anybody use a central database in
their ct protocol design.
My thought was to maintain a "small" local directory at the AR, only
containing the context of sessions that are currently active. The contexts
for the dormant sessions could be stored in the central repository, and are
only brought into the local cache when the session is active.
If, instead, we are to keep every possible context at the ARs, whether or
not the sessions are active, the caches at the ARs may need to be very
large, and inefficient use of memory.
I am not asking for a mandatory requirement on the central database - nobody
has to change their designs to for this "MAY" requirement.
I can accept that the ARs will keep the active contexts. 
I am only asking for this "optional" requirement.
-Sharif. 

------_=_NextPart_001_01C16DF7.F53622C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C16DCE.D14E1350">
<title>RE: [seamoby] CT requirements</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Now, the centralized/local context storage caused =
some </span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; issues. Thus, I would</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; like to re-word it and hope that it would be more =
acceptable.</span></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>Not really. The discussions at the beginning of =
the</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>year explicitly ruled out a centralized repository or =
server</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>approach to ct. There was (as far as I recall) very little =
support</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>for a &quot;ct server&quot; type of approach. The =
preference was
for ct to </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>be peer to peer.</span></font><font color=3Dblack><span
style=3D'color:black'> </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>Gary, everyone:<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>I
was not involved in those discussions, and <span style=3D"mso-spacerun:
yes">&nbsp;</span>thus respectfully ask to revisit this issue. =
<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>I am not asking, in any way, to remove the mandatory =
requirement
from the draft for maintaining the context at the AR, for peer to peer =
context transfer.
I am <span style=3D"mso-spacerun: yes">&nbsp;</span>simply asking for =
an &#8220;optional&#8221;
requirement by which there MAY be a central database for storing the =
contexts
of <u>dormant sessions</u>..<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>The &#8220;optional&#8221; clause would not force anybody =
use a central
database in their ct protocol design.<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>My thought was to maintain a &#8220;small&#8221; local =
directory at the AR<u>,
only</u> containing the context of sessions that are <u>currently =
active</u>.
The contexts for the <u>dormant sessions</u> could be stored in the =
central repository,
and are only brought into the local cache when the session is =
active.<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>If, instead, we are to keep every possible context at the =
ARs,
whether or not the sessions are active, the caches at the ARs may need =
to be
very large, and inefficient use of memory.<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>I am not asking for a mandatory requirement on the central =
database
&#8211; nobody has to change their designs to for this =
&#8220;MAY&#8221; requirement.<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>I can accept that the ARs will keep the active contexts. =
<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>I am only asking for this &#8220;optional&#8221; =
requirement.<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>-Sharif.</span></font><font color=3Dblack><span =
style=3D'color:black'> </span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

</div>

</body>

</html>

------_=_NextPart_001_01C16DF7.F53622C0--


From owner-seamoby@diameter.org  Thu Nov 15 12:23:39 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05676
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Nov 2001 12:23:39 -0500 (EST)
Received: (qmail 28408 invoked by alias); 15 Nov 2001 18:10:21 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28402 invoked by uid 200); 15 Nov 2001 18:10:21 -0000
Received: (qmail 28397 invoked from network); 15 Nov 2001 18:10:19 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 15 Nov 2001 18:10:19 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAFHIi516304;
	Thu, 15 Nov 2001 09:18:44 -0800 (PST)
Message-ID: <00c501c16df9$5b09d5a0$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9A4@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] CT requirements
Date: Thu, 15 Nov 2001 09:17:08 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

We cannot make progress on completing the goal of getting the
requirements draft finished if we keep opening up issues that were
declared closed.

I would like to suggest that we keep the requriement as is with respect
to centralized v.s. local so that we can get the draft to the IESG,
since a clear majority of the working group members seem to support it.
If you and others feel that there is some need for centralized storage,
then write a draft prior next Seamoby working group laying out exactly
why you feel it is necessary and presenting a strong case, and the
working group can consider it on the list and at the meeting in
Minneapolis next March. If the working group agrees, the draft can be
published as an update to the requirements draft.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>; "Shahrier, Sharif
M." <Sharif.Shahrier@InterDigital.com>; <seamoby@cdma-2000.org>
Sent: Thursday, November 15, 2001 9:07 AM
Subject: RE: [seamoby] CT requirements


> >
> > Now, the centralized/local context storage caused some
> > issues. Thus, I would
> > like to re-word it and hope that it would be more acceptable.
> Not really. The discussions at the beginning of the
> year explicitly ruled out a centralized repository or server
> approach to ct. There was (as far as I recall) very little support
> for a "ct server" type of approach. The preference was for ct to
> be peer to peer.
> Gary, everyone:
>             I was not involved in those discussions, and  thus
respectfully
> ask to revisit this issue.
> I am not asking, in any way, to remove the mandatory requirement from
the
> draft for maintaining the context at the AR, for peer to peer context
> transfer. I am  simply asking for an "optional" requirement by which
there
> MAY be a central database for storing the contexts of dormant
sessions..
> The "optional" clause would not force anybody use a central database
in
> their ct protocol design.
> My thought was to maintain a "small" local directory at the AR, only
> containing the context of sessions that are currently active. The
contexts
> for the dormant sessions could be stored in the central repository,
and are
> only brought into the local cache when the session is active.
> If, instead, we are to keep every possible context at the ARs, whether
or
> not the sessions are active, the caches at the ARs may need to be very
> large, and inefficient use of memory.
> I am not asking for a mandatory requirement on the central database -
nobody
> has to change their designs to for this "MAY" requirement.
> I can accept that the ARs will keep the active contexts.
> I am only asking for this "optional" requirement.
> -Sharif.
>



From owner-seamoby@diameter.org  Thu Nov 15 23:46:35 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA06237
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Nov 2001 23:46:35 -0500 (EST)
Received: (qmail 30214 invoked by alias); 16 Nov 2001 05:33:19 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 30208 invoked by uid 200); 16 Nov 2001 05:33:19 -0000
Received: (qmail 30199 invoked by uid 500); 16 Nov 2001 05:33:16 -0000
Date: Thu, 15 Nov 2001 21:33:16 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011115213316.F30111@charizard.diameter.org>
Mail-Followup-To: Gary Kenward <gkenward@nortelnetworks.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	"Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
	'Nakhjiri Madjid-MNAKHJI1' <Madjid.Nakhjiri@motorola.com>,
	"'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
References: <9FBD322B7824D511B36900508BF93C9C01AA464B@zcard031.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <9FBD322B7824D511B36900508BF93C9C01AA464B@zcard031.ca.nortel.com>; from gkenward@nortelnetworks.com on Wed, Nov 14, 2001 at 10:40:15AM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

>   I realize that for you, the situation is very different. You have a real
> system with real issues
> to resolve. It is only one of many networks however, and perhaps a better
> way to get the wg up
> to speed on the specific requirements of UMTS (and other networks) is to
> schedule some presentations
> at the next IETF on existing context transfer problems/solutions. What say
> you Pat and James?

Allowing this would require that we entertain presentations from everyone's
favorite protocol. I would prefer that we keep our meetings focused around
the issues at hand. We will begin protocol eval hopefully soon after the
next IETF, so I think it can wait. If folks like, Sharif is welcomed to
send a URL pointing to information above, and the WG can educate themselves.

PatC



From owner-seamoby@diameter.org  Thu Nov 15 23:49:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA06279
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Nov 2001 23:49:26 -0500 (EST)
Received: (qmail 30747 invoked by alias); 16 Nov 2001 05:36:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 30741 invoked by uid 200); 16 Nov 2001 05:36:24 -0000
Received: (qmail 30731 invoked by uid 500); 16 Nov 2001 05:36:22 -0000
Date: Thu, 15 Nov 2001 21:36:22 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>
Cc: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        seamoby@cdma-2000.org
Subject: Re: [seamoby] Some proposed changes to the requirements draft.
Message-ID: <20011115213622.G30111@charizard.diameter.org>
Mail-Followup-To: "Shaheen, Kamel M." <Kamel.Shaheen@InterDigital.com>,
	'Nakhjiri Madjid-MNAKHJI1' <Madjid.Nakhjiri@motorola.com>,
	'James Kempf' <kempf@docomolabs-usa.com>,
	Gary Kenward <gkenward@nortelnetworks.com>,
	"Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
	seamoby@cdma-2000.org
References: <A1170612471BD21185B90008C7FA0A0D02D81273@idcpa4.pa.interdigital.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <A1170612471BD21185B90008C7FA0A0D02D81273@idcpa4.pa.interdigital.com>; from Kamel.Shaheen@InterDigital.com on Wed, Nov 14, 2001 at 01:45:04PM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

> I would respectfully disagree.  I think it would be beneficial to this work
> to understand and to take previous work into consideration (not necessarily
> to duplicate) if we would like wider acceptance and more generalized
> solution.  Specially given the current drive toward global more harmonized
> kind of interworking.

Perhaps you've misunderstood. It is considered inappropriate to "present"
technologies at IETF meetings. There is no way that people can make a
real assessment in a 20 minute presentation. It is much better to
provide to submit an Internet-Draft and allow people to read it.

PatC


From owner-seamoby@diameter.org  Fri Nov 16 12:18:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11870
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 12:18:17 -0500 (EST)
Received: (qmail 32509 invoked by alias); 16 Nov 2001 18:04:50 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 32503 invoked by uid 200); 16 Nov 2001 18:04:50 -0000
Received: (qmail 32498 invoked from network); 16 Nov 2001 18:04:48 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 16 Nov 2001 18:04:48 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAGHGX502882
	for <seamoby@diameter.org>; Fri, 16 Nov 2001 09:16:33 -0800 (PST)
Message-ID: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@diameter.org>
Subject: [seamoby] Author List on CT Requirements Doc
Date: Fri, 16 Nov 2001 09:14:56 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

The IESG is trying to cut down on long author lists, unless the authors
contributed substantial text to the document. In view
of the fact that Gary has done practically all of the writing on the CT
Requirements document, I would like to suggest that
the author list include his name as editor, and that the rest of the
contributors be listed in the acknowledgements section.
Note that there is no dishonor in being listed in the acknowledgements
section, if it is a vaild reflection of who was primarily responsible
for the wordsmithing and work on the body of the document.

Comments?

                jak



From owner-seamoby@diameter.org  Fri Nov 16 12:32:21 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12747
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 12:32:20 -0500 (EST)
Received: (qmail 695 invoked by alias); 16 Nov 2001 18:19:22 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 681 invoked by uid 200); 16 Nov 2001 18:19:21 -0000
Received: (qmail 674 invoked by uid 500); 16 Nov 2001 18:19:20 -0000
Date: Fri, 16 Nov 2001 10:19:19 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: James Kempf <kempf@docomolabs-usa.com>
Cc: seamoby@diameter.org
Subject: Re: [seamoby] Author List on CT Requirements Doc
Message-ID: <20011116101919.D620@charizard.diameter.org>
Mail-Followup-To: James Kempf <kempf@docomolabs-usa.com>,
	seamoby@diameter.org
References: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF>; from kempf@docomolabs-usa.com on Fri, Nov 16, 2001 at 09:14:56AM -0800
Sender: owner-seamoby@diameter.org
Precedence: bulk

yes, I have a comment. The IESG's position is that folks that participate
in providing large sections of text are in fact co-authors. However, people
that just participate in discussions are not. However, what the IESG REALLY
doesn't like is having authors on a document to show that a particular company
is backing a proposal. So adding authors purely for political reasons is a no-no.

Fortunately, that doesn't apply to any of our documents.

PatC
On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> Folks,
> 
> The IESG is trying to cut down on long author lists, unless the authors
> contributed substantial text to the document. In view
> of the fact that Gary has done practically all of the writing on the CT
> Requirements document, I would like to suggest that
> the author list include his name as editor, and that the rest of the
> contributors be listed in the acknowledgements section.
> Note that there is no dishonor in being listed in the acknowledgements
> section, if it is a vaild reflection of who was primarily responsible
> for the wordsmithing and work on the body of the document.
> 
> Comments?
> 
>                 jak
> 


From owner-seamoby@diameter.org  Fri Nov 16 12:55:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14149
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 12:55:17 -0500 (EST)
Received: (qmail 1299 invoked by alias); 16 Nov 2001 18:42:08 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1293 invoked by uid 200); 16 Nov 2001 18:42:08 -0000
Received: (qmail 1285 invoked from network); 16 Nov 2001 18:42:06 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 16 Nov 2001 18:42:06 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAGHrq504836;
	Fri, 16 Nov 2001 09:53:52 -0800 (PST)
Message-ID: <00c801c16ec7$6d4dd850$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Pat Calhoun" <pcalhoun@diameter.org>
Cc: <seamoby@diameter.org>
References: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF> <20011116101919.D620@charizard.diameter.org>
Subject: Re: [seamoby] Author List on CT Requirements Doc
Date: Fri, 16 Nov 2001 09:52:15 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pat,

OK, so I still have the question if all of the authors on the
current document have contributed text, or have any
just contributed to the discussion? I don't believe
that any are just on for political reasons.

Those that have contributed to the discussion should
go into the acknowledgements section, and those
that have contributed text should go on the author
list. Right?

        jak

----- Original Message -----
From: "Pat Calhoun" <pcalhoun@diameter.org>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <seamoby@diameter.org>
Sent: Friday, November 16, 2001 10:19 AM
Subject: Re: [seamoby] Author List on CT Requirements Doc


> yes, I have a comment. The IESG's position is that folks that
participate
> in providing large sections of text are in fact co-authors. However,
people
> that just participate in discussions are not. However, what the IESG
REALLY
> doesn't like is having authors on a document to show that a particular
company
> is backing a proposal. So adding authors purely for political reasons
is a no-no.
>
> Fortunately, that doesn't apply to any of our documents.
>
> PatC
> On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> > Folks,
> >
> > The IESG is trying to cut down on long author lists, unless the
authors
> > contributed substantial text to the document. In view
> > of the fact that Gary has done practically all of the writing on the
CT
> > Requirements document, I would like to suggest that
> > the author list include his name as editor, and that the rest of the
> > contributors be listed in the acknowledgements section.
> > Note that there is no dishonor in being listed in the
acknowledgements
> > section, if it is a vaild reflection of who was primarily
responsible
> > for the wordsmithing and work on the body of the document.
> >
> > Comments?
> >
> >                 jak
> >
>



From owner-seamoby@diameter.org  Fri Nov 16 13:07:31 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA14742
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 13:07:30 -0500 (EST)
Received: (qmail 1905 invoked by alias); 16 Nov 2001 18:54:14 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1899 invoked by uid 200); 16 Nov 2001 18:54:13 -0000
Received: (qmail 1891 invoked from network); 16 Nov 2001 18:54:12 -0000
Received: from motgate2.mot.com (136.182.1.10)
  by c900656-a.plstn1.sfba.home.com with SMTP; 16 Nov 2001 18:54:12 -0000
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id LAA16814; Fri, 16 Nov 2001 11:06:26 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA20596; Fri, 16 Nov 2001 11:06:26 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <4K0CBVQ1>; Fri, 16 Nov 2001 12:05:22 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB67@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Author List on CT Requirements Doc
Date: Fri, 16 Nov 2001 12:05:22 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

The original text that went into the first writing
might not match the current word by word, so that is
a tough question for both CT drafts (at least I speak for
myself). Many of us sent text (that is beside the list discussion)
and the text made it into the first version, and then later
the credit for bringing it to a presentable document must be
 given to the editor of course, but...

An option is just to put names without companies in front
of the draft, as I see in some recent documents.

Madjid

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Friday, November 16, 2001 11:52 AM
To: Pat Calhoun
Cc: seamoby@diameter.org
Subject: Re: [seamoby] Author List on CT Requirements Doc


Pat,

OK, so I still have the question if all of the authors on the
current document have contributed text, or have any
just contributed to the discussion? I don't believe
that any are just on for political reasons.

Those that have contributed to the discussion should
go into the acknowledgements section, and those
that have contributed text should go on the author
list. Right?

        jak

----- Original Message -----
From: "Pat Calhoun" <pcalhoun@diameter.org>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <seamoby@diameter.org>
Sent: Friday, November 16, 2001 10:19 AM
Subject: Re: [seamoby] Author List on CT Requirements Doc


> yes, I have a comment. The IESG's position is that folks that
participate
> in providing large sections of text are in fact co-authors. However,
people
> that just participate in discussions are not. However, what the IESG
REALLY
> doesn't like is having authors on a document to show that a particular
company
> is backing a proposal. So adding authors purely for political reasons
is a no-no.
>
> Fortunately, that doesn't apply to any of our documents.
>
> PatC
> On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> > Folks,
> >
> > The IESG is trying to cut down on long author lists, unless the
authors
> > contributed substantial text to the document. In view
> > of the fact that Gary has done practically all of the writing on the
CT
> > Requirements document, I would like to suggest that
> > the author list include his name as editor, and that the rest of the
> > contributors be listed in the acknowledgements section.
> > Note that there is no dishonor in being listed in the
acknowledgements
> > section, if it is a vaild reflection of who was primarily
responsible
> > for the wordsmithing and work on the body of the document.
> >
> > Comments?
> >
> >                 jak
> >
>


From owner-seamoby@diameter.org  Fri Nov 16 14:22:14 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19219
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 14:22:14 -0500 (EST)
Received: (qmail 2642 invoked by alias); 16 Nov 2001 20:09:06 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2636 invoked by uid 200); 16 Nov 2001 20:09:06 -0000
Received: (qmail 2631 invoked from network); 16 Nov 2001 20:09:04 -0000
Received: from bells.cs.ucl.ac.uk (128.16.5.31)
  by c900656-a.plstn1.sfba.home.com with SMTP; 16 Nov 2001 20:09:04 -0000
Received: from bohemian.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.21548-0@bells.cs.ucl.ac.uk>; Fri, 16 Nov 2001 19:21:06 +0000
Message-ID: <3BF56722.2728B532@cs.ucl.ac.uk>
Date: Fri, 16 Nov 2001 19:21:06 +0000
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: t.pagtzis@cs.ucl.ac.uk
Organization: UCL/Mobile Systems Group
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: seamoby <seamoby@diameter.org>
Subject: Re: [seamoby] Author List on CT Requirements Doc
References: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Kempf wrote:
> 
> Folks,
> 
> The IESG is trying to cut down on long author lists, unless the authors
> contributed substantial text to the document. In view
> of the fact that Gary has done practically all of the writing on the CT
> Requirements document, I would like to suggest that
> the author list include his name as editor, and that the rest of the
> contributors be listed in the acknowledgements section.
> Note that there is no dishonor in being listed in the acknowledgements
> section, if it is a vaild reflection of who was primarily responsible
> for the wordsmithing and work on the body of the document.
> 
> Comments?
> 
>                 jak

Jak,

  If you want to be fair and square with the mailing list which tends to
be an open book to pretty much everybody (author or not) I agree with
you..

Theo

UCL/Mobile Systems Group


From owner-seamoby@diameter.org  Fri Nov 16 15:18:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23746
	for <seamoby-archive@lists.ietf.org>; Fri, 16 Nov 2001 15:18:07 -0500 (EST)
Received: (qmail 3377 invoked by alias); 16 Nov 2001 21:04:56 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 3371 invoked by uid 200); 16 Nov 2001 21:04:56 -0000
Received: (qmail 3362 invoked by uid 500); 16 Nov 2001 21:04:54 -0000
Date: Fri, 16 Nov 2001 13:04:53 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: James Kempf <kempf@docomolabs-usa.com>
Cc: Pat Calhoun <pcalhoun@diameter.org>, seamoby@diameter.org
Subject: Re: [seamoby] Author List on CT Requirements Doc
Message-ID: <20011116130453.A3354@charizard.diameter.org>
Mail-Followup-To: James Kempf <kempf@docomolabs-usa.com>,
	Pat Calhoun <pcalhoun@diameter.org>, seamoby@diameter.org
References: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF> <20011116101919.D620@charizard.diameter.org> <00c801c16ec7$6d4dd850$0e02320a@T23KEMPF>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <00c801c16ec7$6d4dd850$0e02320a@T23KEMPF>; from kempf@docomolabs-usa.com on Fri, Nov 16, 2001 at 09:52:15AM -0800
Sender: owner-seamoby@diameter.org
Precedence: bulk

correct

PatC
On Fri, Nov 16, 2001 at 09:52:15AM -0800, James Kempf wrote:
> Pat,
> 
> OK, so I still have the question if all of the authors on the
> current document have contributed text, or have any
> just contributed to the discussion? I don't believe
> that any are just on for political reasons.
> 
> Those that have contributed to the discussion should
> go into the acknowledgements section, and those
> that have contributed text should go on the author
> list. Right?
> 
>         jak
> 
> ----- Original Message -----
> From: "Pat Calhoun" <pcalhoun@diameter.org>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <seamoby@diameter.org>
> Sent: Friday, November 16, 2001 10:19 AM
> Subject: Re: [seamoby] Author List on CT Requirements Doc
> 
> 
> > yes, I have a comment. The IESG's position is that folks that
> participate
> > in providing large sections of text are in fact co-authors. However,
> people
> > that just participate in discussions are not. However, what the IESG
> REALLY
> > doesn't like is having authors on a document to show that a particular
> company
> > is backing a proposal. So adding authors purely for political reasons
> is a no-no.
> >
> > Fortunately, that doesn't apply to any of our documents.
> >
> > PatC
> > On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> > > Folks,
> > >
> > > The IESG is trying to cut down on long author lists, unless the
> authors
> > > contributed substantial text to the document. In view
> > > of the fact that Gary has done practically all of the writing on the
> CT
> > > Requirements document, I would like to suggest that
> > > the author list include his name as editor, and that the rest of the
> > > contributors be listed in the acknowledgements section.
> > > Note that there is no dishonor in being listed in the
> acknowledgements
> > > section, if it is a vaild reflection of who was primarily
> responsible
> > > for the wordsmithing and work on the body of the document.
> > >
> > > Comments?
> > >
> > >                 jak
> > >
> >
> 


From owner-seamoby@diameter.org  Fri Nov 16 17:07:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA27011
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Nov 2001 17:07:17 -0500 (EST)
Received: (qmail 4211 invoked by alias); 16 Nov 2001 22:53:48 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4205 invoked by uid 200); 16 Nov 2001 22:53:47 -0000
Received: (qmail 4197 invoked from network); 16 Nov 2001 22:53:45 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 16 Nov 2001 22:53:45 -0000
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 OAA07131;
	Fri, 16 Nov 2001 14:05:31 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fAGM5UP02123;
	Fri, 16 Nov 2001 14:05:30 -0800
X-mProtect:  Fri, 16 Nov 2001 14:05:30 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdSFWIm5; Fri, 16 Nov 2001 14:05:28 PST
Message-ID: <3BF58DA8.28222291@iprg.nokia.com>
Date: Fri, 16 Nov 2001 14:05:28 -0800
From: Rajeev Koodli <rajeev@IPRG.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
CC: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Pat Calhoun <pcalhoun@diameter.org>, seamoby@diameter.org
Subject: Re: [seamoby] Author List on CT Requirements Doc
References: <35DBB8B7AC89D4118E98009027B1009B0464FB67@IL27EXM10.cig.mot.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


James,

I share Madjid's feelings..

Regards,

-Rajeev


Nakhjiri Madjid-MNAKHJI1 wrote:

> The original text that went into the first writing
> might not match the current word by word, so that is
> a tough question for both CT drafts (at least I speak for
> myself). Many of us sent text (that is beside the list discussion)
> and the text made it into the first version, and then later
> the credit for bringing it to a presentable document must be
>  given to the editor of course, but...
>
> An option is just to put names without companies in front
> of the draft, as I see in some recent documents.
>
> Madjid
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Friday, November 16, 2001 11:52 AM
> To: Pat Calhoun
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] Author List on CT Requirements Doc
>
> Pat,
>
> OK, so I still have the question if all of the authors on the
> current document have contributed text, or have any
> just contributed to the discussion? I don't believe
> that any are just on for political reasons.
>
> Those that have contributed to the discussion should
> go into the acknowledgements section, and those
> that have contributed text should go on the author
> list. Right?
>
>         jak
>
> ----- Original Message -----
> From: "Pat Calhoun" <pcalhoun@diameter.org>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <seamoby@diameter.org>
> Sent: Friday, November 16, 2001 10:19 AM
> Subject: Re: [seamoby] Author List on CT Requirements Doc
>
> > yes, I have a comment. The IESG's position is that folks that
> participate
> > in providing large sections of text are in fact co-authors. However,
> people
> > that just participate in discussions are not. However, what the IESG
> REALLY
> > doesn't like is having authors on a document to show that a particular
> company
> > is backing a proposal. So adding authors purely for political reasons
> is a no-no.
> >
> > Fortunately, that doesn't apply to any of our documents.
> >
> > PatC
> > On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> > > Folks,
> > >
> > > The IESG is trying to cut down on long author lists, unless the
> authors
> > > contributed substantial text to the document. In view
> > > of the fact that Gary has done practically all of the writing on the
> CT
> > > Requirements document, I would like to suggest that
> > > the author list include his name as editor, and that the rest of the
> > > contributors be listed in the acknowledgements section.
> > > Note that there is no dishonor in being listed in the
> acknowledgements
> > > section, if it is a vaild reflection of who was primarily
> responsible
> > > for the wordsmithing and work on the body of the document.
> > >
> > > Comments?
> > >
> > >                 jak
> > >
> >



From owner-seamoby@diameter.org  Fri Nov 16 18:50:48 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA29659
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Nov 2001 18:50:46 -0500 (EST)
Received: (qmail 4969 invoked by alias); 17 Nov 2001 00:36:09 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4963 invoked by uid 200); 17 Nov 2001 00:36:09 -0000
Received: (qmail 4955 invoked from network); 17 Nov 2001 00:36:06 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 17 Nov 2001 00:36:06 -0000
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAGNl6S26720;
	Fri, 16 Nov 2001 18:47:06 -0500 (EST)
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.ca.nortel.com; Fri, 16 Nov 2001 18:47:43 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W9X3B2AG>; Fri, 16 Nov 2001 18:46:50 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA467F@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Cc: seamoby <seamoby@diameter.org>
Subject: RE: [seamoby] Author List on CT Requirements Doc
Date: Fri, 16 Nov 2001 18:46:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C16EF8.F6817AB0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C16EF8.F6817AB0
Content-Type: text/plain;
	charset="iso-8859-1"

Since I put those author's on the list, I guess I would have
to say that I did so believing that each one contributed to
the draft. This was in compliance to the guidelines for wg
drafts as I understood them at the time.

For what it's worth.

Gary

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: November 16, 2001 12:52
> To: Pat Calhoun
> Cc: seamoby
> Subject: Re: [seamoby] Author List on CT Requirements Doc
> 
> 
> Pat,
> 
> OK, so I still have the question if all of the authors on the
> current document have contributed text, or have any
> just contributed to the discussion? I don't believe
> that any are just on for political reasons.
> 
> Those that have contributed to the discussion should
> go into the acknowledgements section, and those
> that have contributed text should go on the author
> list. Right?
> 
>         jak
> 
> ----- Original Message -----
> From: "Pat Calhoun" <pcalhoun@diameter.org>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <seamoby@diameter.org>
> Sent: Friday, November 16, 2001 10:19 AM
> Subject: Re: [seamoby] Author List on CT Requirements Doc
> 
> 
> > yes, I have a comment. The IESG's position is that folks that
> participate
> > in providing large sections of text are in fact co-authors. However,
> people
> > that just participate in discussions are not. However, what the IESG
> REALLY
> > doesn't like is having authors on a document to show that a 
> particular
> company
> > is backing a proposal. So adding authors purely for 
> political reasons
> is a no-no.
> >
> > Fortunately, that doesn't apply to any of our documents.
> >
> > PatC
> > On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:
> > > Folks,
> > >
> > > The IESG is trying to cut down on long author lists, unless the
> authors
> > > contributed substantial text to the document. In view
> > > of the fact that Gary has done practically all of the 
> writing on the
> CT
> > > Requirements document, I would like to suggest that
> > > the author list include his name as editor, and that the 
> rest of the
> > > contributors be listed in the acknowledgements section.
> > > Note that there is no dishonor in being listed in the
> acknowledgements
> > > section, if it is a vaild reflection of who was primarily
> responsible
> > > for the wordsmithing and work on the body of the document.
> > >
> > > Comments?
> > >
> > >                 jak
> > >
> >
> 
> 

------_=_NextPart_001_01C16EF8.F6817AB0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [seamoby] Author List on CT Requirements Doc</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Since I put those author's on the list, I guess I would have</FONT>
<BR><FONT SIZE=2>to say that I did so believing that each one contributed to</FONT>
<BR><FONT SIZE=2>the draft. This was in compliance to the guidelines for wg</FONT>
<BR><FONT SIZE=2>drafts as I understood them at the time.</FONT>
</P>

<P><FONT SIZE=2>For what it's worth.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:kempf@docomolabs-usa.com">mailto:kempf@docomolabs-usa.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: November 16, 2001 12:52</FONT>
<BR><FONT SIZE=2>&gt; To: Pat Calhoun</FONT>
<BR><FONT SIZE=2>&gt; Cc: seamoby</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [seamoby] Author List on CT Requirements Doc</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Pat,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; OK, so I still have the question if all of the authors on the</FONT>
<BR><FONT SIZE=2>&gt; current document have contributed text, or have any</FONT>
<BR><FONT SIZE=2>&gt; just contributed to the discussion? I don't believe</FONT>
<BR><FONT SIZE=2>&gt; that any are just on for political reasons.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Those that have contributed to the discussion should</FONT>
<BR><FONT SIZE=2>&gt; go into the acknowledgements section, and those</FONT>
<BR><FONT SIZE=2>&gt; that have contributed text should go on the author</FONT>
<BR><FONT SIZE=2>&gt; list. Right?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; ----- Original Message -----</FONT>
<BR><FONT SIZE=2>&gt; From: &quot;Pat Calhoun&quot; &lt;pcalhoun@diameter.org&gt;</FONT>
<BR><FONT SIZE=2>&gt; To: &quot;James Kempf&quot; &lt;kempf@docomolabs-usa.com&gt;</FONT>
<BR><FONT SIZE=2>&gt; Cc: &lt;seamoby@diameter.org&gt;</FONT>
<BR><FONT SIZE=2>&gt; Sent: Friday, November 16, 2001 10:19 AM</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [seamoby] Author List on CT Requirements Doc</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; yes, I have a comment. The IESG's position is that folks that</FONT>
<BR><FONT SIZE=2>&gt; participate</FONT>
<BR><FONT SIZE=2>&gt; &gt; in providing large sections of text are in fact co-authors. However,</FONT>
<BR><FONT SIZE=2>&gt; people</FONT>
<BR><FONT SIZE=2>&gt; &gt; that just participate in discussions are not. However, what the IESG</FONT>
<BR><FONT SIZE=2>&gt; REALLY</FONT>
<BR><FONT SIZE=2>&gt; &gt; doesn't like is having authors on a document to show that a </FONT>
<BR><FONT SIZE=2>&gt; particular</FONT>
<BR><FONT SIZE=2>&gt; company</FONT>
<BR><FONT SIZE=2>&gt; &gt; is backing a proposal. So adding authors purely for </FONT>
<BR><FONT SIZE=2>&gt; political reasons</FONT>
<BR><FONT SIZE=2>&gt; is a no-no.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; Fortunately, that doesn't apply to any of our documents.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; PatC</FONT>
<BR><FONT SIZE=2>&gt; &gt; On Fri, Nov 16, 2001 at 09:14:56AM -0800, James Kempf wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; The IESG is trying to cut down on long author lists, unless the</FONT>
<BR><FONT SIZE=2>&gt; authors</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; contributed substantial text to the document. In view</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of the fact that Gary has done practically all of the </FONT>
<BR><FONT SIZE=2>&gt; writing on the</FONT>
<BR><FONT SIZE=2>&gt; CT</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Requirements document, I would like to suggest that</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; the author list include his name as editor, and that the </FONT>
<BR><FONT SIZE=2>&gt; rest of the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; contributors be listed in the acknowledgements section.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Note that there is no dishonor in being listed in the</FONT>
<BR><FONT SIZE=2>&gt; acknowledgements</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; section, if it is a vaild reflection of who was primarily</FONT>
<BR><FONT SIZE=2>&gt; responsible</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; for the wordsmithing and work on the body of the document.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Comments?</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C16EF8.F6817AB0--


From owner-seamoby@diameter.org  Fri Nov 16 19:41:23 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00563
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Nov 2001 19:41:23 -0500 (EST)
Received: (qmail 5545 invoked by alias); 17 Nov 2001 01:28:17 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 5539 invoked by uid 200); 17 Nov 2001 01:28:16 -0000
Received: (qmail 5533 invoked from network); 17 Nov 2001 01:28:14 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 17 Nov 2001 01:28:14 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAH0e1521452;
	Fri, 16 Nov 2001 16:40:01 -0800 (PST)
Message-ID: <006e01c16f00$29e9b5f0$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "James Kempf" <kempf@docomolabs-usa.com>, <seamoby@diameter.org>
References: <00a201c16ec2$36b3fa40$0e02320a@T23KEMPF>
Subject: Re: [seamoby] Author List on CT Requirements Doc
Date: Fri, 16 Nov 2001 16:38:23 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

OK, well I must apologize for stirring things up unnecessarily. Perils
of being a new WG chair. :-)

From what I've been able to determine, the usual requirement for
authorship on an RFC is that someone contributed the majority of text to
a draft (say 75%) or their intelletual contribution was 75% but their
writing skills were so deficient that someone else had to write it down.

In this case, I'm told that substantial portions of the requirements
were contributed by the folks on the current author list, so I guess
keeping the author list as it currently stands is probably the fairest
thing to do. Removing the company names, as I think Madjid suggested,
would help to shorten the list. Others should be put into the
acknowledgements section.

There is no guarantee that the document will come back from the IESG
with the author list intact, however.

            jak



From owner-seamoby@diameter.org  Mon Nov 19 09:05:48 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29196
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 09:05:47 -0500 (EST)
Received: (qmail 20704 invoked by alias); 19 Nov 2001 14:52:24 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 20698 invoked by uid 200); 19 Nov 2001 14:52:24 -0000
Received: (qmail 20693 invoked from network); 19 Nov 2001 14:52:22 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 14:52:22 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09532X>; Mon, 19 Nov 2001 09:03:08 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A5@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'gkenward@nortelnetworks.com'" <gkenward@nortelnetworks.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 09:03:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Gary,

	From our discussions last week, I just want to clarify that, that
people had agreed to include two of the requirements that I had suggested,
also, some wording was changed to one of the existing requirements. Can you
please confirm that these are going to be updated?

-Sharif.

"The context transfer solution MUST be scalable".

"The context transfer solution MUST include methods for interworking with
any IETF IP handover solutions".

Also, the wording in section 5.1.2 was changed, I believe.




From owner-seamoby@diameter.org  Mon Nov 19 11:40:50 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08667
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 11:40:49 -0500 (EST)
Received: (qmail 21985 invoked by alias); 19 Nov 2001 17:27:15 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21979 invoked by uid 200); 19 Nov 2001 17:27:15 -0000
Received: (qmail 21974 invoked from network); 19 Nov 2001 17:27:13 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 17:27:13 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJGZ9502961;
	Mon, 19 Nov 2001 08:35:09 -0800 (PST)
Message-ID: <00b701c17117$ed585460$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9A5@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 08:33:32 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

My tracking of the list converstion was that there is  agreement on
adding *one* requirement, 5.6.1 for the CT protocol to support handover,
and modifying the wording on another, 5.1.2, to clarify what is meant by
supporting a standardized representation format.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 6:03 AM
Subject: [seamoby] Update to the requirements draft


> Gary,
>
> From our discussions last week, I just want to clarify that, that
> people had agreed to include two of the requirements that I had
suggested,
> also, some wording was changed to one of the existing requirements.
Can you
> please confirm that these are going to be updated?
>
> -Sharif.
>
> "The context transfer solution MUST be scalable".
>
> "The context transfer solution MUST include methods for interworking
with
> any IETF IP handover solutions".
>
> Also, the wording in section 5.1.2 was changed, I believe.
>
>
>



From owner-seamoby@diameter.org  Mon Nov 19 11:59:58 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09647
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 11:59:57 -0500 (EST)
Received: (qmail 22596 invoked by alias); 19 Nov 2001 17:46:22 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 22590 invoked by uid 200); 19 Nov 2001 17:46:21 -0000
Received: (qmail 22585 invoked from network); 19 Nov 2001 17:46:19 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 17:46:19 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095PAF>; Mon, 19 Nov 2001 11:57:06 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9A7@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 11:57:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

James,

	It appears that no one really opposed the requirement that "CT
solution MUST be scalable". It was suggested to shorten  the wording,
without elaborating on it.. I have some extracts of comments.

Unless there is a large disagreement at this time, perhaps it would not hurt
to include it.
I have noted that "scalability" is a major issue that props up, time and
again, in protocols in the IETF.

-Sharif.

============================================================================
=====================
> 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> scalable to millions of hosts".

This is 'motherhood & apple pie' text (i.e. - noone would really
disagree). I don't know how this adds anything to the text.  
Additionally, I would suggest SHOULD rather than MUST is
what you mean.



Finally, scaleability is desireable, as long as the requirement is for
scaleability 
at an acceptable cost. 
 Other then this, I do not know how one would word a requirement around
scaleability 
other then the motherhood of "ct must be scaleable at an acceptable cost". 

Gary, Sharif, John, 
if the requirement is a given, then let's not argue about/against it. It
cannot 
hurt to include it, and _technically_ there is consensus for it. 
As far as how to phrase it, usually scalability is described as the marginal
increase 
in complexity induced by adding users. So something along the lines: 
the processing complexity at each AR (and the burden on the wired network) 
SHOULD increase linearly with the number of MNs or the number of CT
requests. 
Also, you can check conformance there. 


 -----Original Message-----
From: 	James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent:	Monday, November 19, 2001 11:34 AM
To:	Shahrier, Sharif M.; gkenward@nortelnetworks.com
Cc:	seamoby@cdma-2000.org
Subject:	Re: [seamoby] Update to the requirements draft

Sharif,

My tracking of the list converstion was that there is  agreement on
adding *one* requirement, 5.6.1 for the CT protocol to support handover,
and modifying the wording on another, 5.1.2, to clarify what is meant by
supporting a standardized representation format.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 6:03 AM
Subject: [seamoby] Update to the requirements draft


> Gary,
>
> From our discussions last week, I just want to clarify that, that
> people had agreed to include two of the requirements that I had
suggested,
> also, some wording was changed to one of the existing requirements.
Can you
> please confirm that these are going to be updated?
>
> -Sharif.
>
> "The context transfer solution MUST be scalable".
>
> "The context transfer solution MUST include methods for interworking
with
> any IETF IP handover solutions".
>
> Also, the wording in section 5.1.2 was changed, I believe.
>
>
>


From owner-seamoby@diameter.org  Mon Nov 19 12:20:00 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10665
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 12:19:58 -0500 (EST)
Received: (qmail 23241 invoked by alias); 19 Nov 2001 18:06:19 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 23235 invoked by uid 200); 19 Nov 2001 18:06:18 -0000
Received: (qmail 23230 invoked from network); 19 Nov 2001 18:06:16 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 18:06:16 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJHGJ504433;
	Mon, 19 Nov 2001 09:16:19 -0800 (PST)
Message-ID: <00ff01c1711d$ad9ad400$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9A7@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 09:14:42 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

OK. I had just recalled the "motherhood and apple pie" comment. The
requirement does seem obvious to me. One
could as easily say "The CT solution must be deployable".

But if the WG agrees, then I'd suggest that we add it, with the proviso
that it be a SHOULD, as the comments
below indicate.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 8:57 AM
Subject: RE: [seamoby] Update to the requirements draft


> James,
>
> It appears that no one really opposed the requirement that "CT
> solution MUST be scalable". It was suggested to shorten  the wording,
> without elaborating on it.. I have some extracts of comments.
>
> Unless there is a large disagreement at this time, perhaps it would
not hurt
> to include it.
> I have noted that "scalability" is a major issue that props up, time
and
> again, in protocols in the IETF.
>
> -Sharif.
>
>
========================================================================
====
> =====================
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be
> > scalable to millions of hosts".
>
> This is 'motherhood & apple pie' text (i.e. - noone would really
> disagree). I don't know how this adds anything to the text.
> Additionally, I would suggest SHOULD rather than MUST is
> what you mean.
>
>
>
> Finally, scaleability is desireable, as long as the requirement is for
> scaleability
> at an acceptable cost.
>  Other then this, I do not know how one would word a requirement
around
> scaleability
> other then the motherhood of "ct must be scaleable at an acceptable
cost".
>
> Gary, Sharif, John,
> if the requirement is a given, then let's not argue about/against it.
It
> cannot
> hurt to include it, and _technically_ there is consensus for it.
> As far as how to phrase it, usually scalability is described as the
marginal
> increase
> in complexity induced by adding users. So something along the lines:
> the processing complexity at each AR (and the burden on the wired
network)
> SHOULD increase linearly with the number of MNs or the number of CT
> requests.
> Also, you can check conformance there.
>
>
>  -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Monday, November 19, 2001 11:34 AM
> To: Shahrier, Sharif M.; gkenward@nortelnetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: Re: [seamoby] Update to the requirements draft
>
> Sharif,
>
> My tracking of the list converstion was that there is  agreement on
> adding *one* requirement, 5.6.1 for the CT protocol to support
handover,
> and modifying the wording on another, 5.1.2, to clarify what is meant
by
> supporting a standardized representation format.
>
>             jak
>
> ----- Original Message -----
> From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> To: <gkenward@nortelnetworks.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Monday, November 19, 2001 6:03 AM
> Subject: [seamoby] Update to the requirements draft
>
>
> > Gary,
> >
> > From our discussions last week, I just want to clarify that, that
> > people had agreed to include two of the requirements that I had
> suggested,
> > also, some wording was changed to one of the existing requirements.
> Can you
> > please confirm that these are going to be updated?
> >
> > -Sharif.
> >
> > "The context transfer solution MUST be scalable".
> >
> > "The context transfer solution MUST include methods for interworking
> with
> > any IETF IP handover solutions".
> >
> > Also, the wording in section 5.1.2 was changed, I believe.
> >
> >
> >
>



From owner-seamoby@diameter.org  Mon Nov 19 15:06:01 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21590
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 15:06:00 -0500 (EST)
Received: (qmail 24638 invoked by alias); 19 Nov 2001 20:51:43 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 24632 invoked by uid 200); 19 Nov 2001 20:51:43 -0000
Received: (qmail 24627 invoked from network); 19 Nov 2001 20:51:41 -0000
Received: from motgate4.mot.com (144.189.100.102)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 20:51:41 -0000
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate4.mot.com (motgate4 2.1) with ESMTP id NAA15562 for <seamoby@cdma-2000.org>; Mon, 19 Nov 2001 13:04:06 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id NAA22655 for <seamoby@cdma-2000.org>; Mon, 19 Nov 2001 13:04:06 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <4K0CC5Z0>; Mon, 19 Nov 2001 14:04:05 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB74@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 14:04:05 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I don't like the scalability requirement either.
It is obvious.

Madjid

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, November 19, 2001 10:57 AM
To: 'James Kempf'; Shahrier, Sharif M.; gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft


James,

	It appears that no one really opposed the requirement that "CT
solution MUST be scalable". It was suggested to shorten  the wording,
without elaborating on it.. I have some extracts of comments.

Unless there is a large disagreement at this time, perhaps it would not hurt
to include it.
I have noted that "scalability" is a major issue that props up, time and
again, in protocols in the IETF.

-Sharif.

============================================================================
=====================
> 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> scalable to millions of hosts".

This is 'motherhood & apple pie' text (i.e. - noone would really
disagree). I don't know how this adds anything to the text.  
Additionally, I would suggest SHOULD rather than MUST is
what you mean.



Finally, scaleability is desireable, as long as the requirement is for
scaleability 
at an acceptable cost. 
 Other then this, I do not know how one would word a requirement around
scaleability 
other then the motherhood of "ct must be scaleable at an acceptable cost". 

Gary, Sharif, John, 
if the requirement is a given, then let's not argue about/against it. It
cannot 
hurt to include it, and _technically_ there is consensus for it. 
As far as how to phrase it, usually scalability is described as the marginal
increase 
in complexity induced by adding users. So something along the lines: 
the processing complexity at each AR (and the burden on the wired network) 
SHOULD increase linearly with the number of MNs or the number of CT
requests. 
Also, you can check conformance there. 


 -----Original Message-----
From: 	James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent:	Monday, November 19, 2001 11:34 AM
To:	Shahrier, Sharif M.; gkenward@nortelnetworks.com
Cc:	seamoby@cdma-2000.org
Subject:	Re: [seamoby] Update to the requirements draft

Sharif,

My tracking of the list converstion was that there is  agreement on
adding *one* requirement, 5.6.1 for the CT protocol to support handover,
and modifying the wording on another, 5.1.2, to clarify what is meant by
supporting a standardized representation format.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 6:03 AM
Subject: [seamoby] Update to the requirements draft


> Gary,
>
> From our discussions last week, I just want to clarify that, that
> people had agreed to include two of the requirements that I had
suggested,
> also, some wording was changed to one of the existing requirements.
Can you
> please confirm that these are going to be updated?
>
> -Sharif.
>
> "The context transfer solution MUST be scalable".
>
> "The context transfer solution MUST include methods for interworking
with
> any IETF IP handover solutions".
>
> Also, the wording in section 5.1.2 was changed, I believe.
>
>
>


From owner-seamoby@diameter.org  Mon Nov 19 15:20:38 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22556
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 15:20:37 -0500 (EST)
Received: (qmail 25232 invoked by alias); 19 Nov 2001 21:06:48 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 25226 invoked by uid 200); 19 Nov 2001 21:06:48 -0000
Received: (qmail 25221 invoked from network); 19 Nov 2001 21:06:45 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 21:06:45 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095PY1>; Mon, 19 Nov 2001 15:17:34 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9AB@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 15:17:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

The IESG had turned down the MIPv6 draft due scalability issues - they
obviously consider the issue to be very important.
It is obviously important to CT too, as one increases the number of context
features to be transferred (perhaps to thousands), the CT protocol that
SEAMOBY adopts has to be scalable too.

I think this is a very important requirement, and needs to be spelt out in
the requirements draft - otherwise it would be too easy for people to
overlook it.

-Sharif.


 -----Original Message-----
From: 	Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com] 
Sent:	Monday, November 19, 2001 3:04 PM
To:	'Shahrier, Sharif M.'; 'James Kempf'; gkenward@nortelnetworks.com
Cc:	seamoby@cdma-2000.org
Subject:	RE: [seamoby] Update to the requirements draft

I don't like the scalability requirement either.
It is obvious.

Madjid

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, November 19, 2001 10:57 AM
To: 'James Kempf'; Shahrier, Sharif M.; gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft


James,

	It appears that no one really opposed the requirement that "CT
solution MUST be scalable". It was suggested to shorten  the wording,
without elaborating on it.. I have some extracts of comments.

Unless there is a large disagreement at this time, perhaps it would not hurt
to include it.
I have noted that "scalability" is a major issue that props up, time and
again, in protocols in the IETF.

-Sharif.

============================================================================
=====================
> 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> scalable to millions of hosts".

This is 'motherhood & apple pie' text (i.e. - noone would really
disagree). I don't know how this adds anything to the text.  
Additionally, I would suggest SHOULD rather than MUST is
what you mean.



Finally, scaleability is desireable, as long as the requirement is for
scaleability 
at an acceptable cost. 
 Other then this, I do not know how one would word a requirement around
scaleability 
other then the motherhood of "ct must be scaleable at an acceptable cost". 

Gary, Sharif, John, 
if the requirement is a given, then let's not argue about/against it. It
cannot 
hurt to include it, and _technically_ there is consensus for it. 
As far as how to phrase it, usually scalability is described as the marginal
increase 
in complexity induced by adding users. So something along the lines: 
the processing complexity at each AR (and the burden on the wired network) 
SHOULD increase linearly with the number of MNs or the number of CT
requests. 
Also, you can check conformance there. 


 -----Original Message-----
From: 	James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent:	Monday, November 19, 2001 11:34 AM
To:	Shahrier, Sharif M.; gkenward@nortelnetworks.com
Cc:	seamoby@cdma-2000.org
Subject:	Re: [seamoby] Update to the requirements draft

Sharif,

My tracking of the list converstion was that there is  agreement on
adding *one* requirement, 5.6.1 for the CT protocol to support handover,
and modifying the wording on another, 5.1.2, to clarify what is meant by
supporting a standardized representation format.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 6:03 AM
Subject: [seamoby] Update to the requirements draft


> Gary,
>
> From our discussions last week, I just want to clarify that, that
> people had agreed to include two of the requirements that I had
suggested,
> also, some wording was changed to one of the existing requirements.
Can you
> please confirm that these are going to be updated?
>
> -Sharif.
>
> "The context transfer solution MUST be scalable".
>
> "The context transfer solution MUST include methods for interworking
with
> any IETF IP handover solutions".
>
> Also, the wording in section 5.1.2 was changed, I believe.
>
>
>


From owner-seamoby@diameter.org  Mon Nov 19 16:27:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26317
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 16:27:07 -0500 (EST)
Received: (qmail 25984 invoked by alias); 19 Nov 2001 22:12:55 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 25978 invoked by uid 200); 19 Nov 2001 22:12:55 -0000
Received: (qmail 25973 invoked from network); 19 Nov 2001 22:12:53 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 22:12:53 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJLMC514278;
	Mon, 19 Nov 2001 13:22:12 -0800 (PST)
Message-ID: <002901c17140$06ddf660$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9AB@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 13:20:34 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think we should put it in subject to the comments. I don't think it
should say anything about numbers.
How about:

        The CT protocol SHOULD be scalable at an acceptable cost. The CT
protocol SHOULD scale at most linearly
        with the number of participating network nodes.

That was suggested by one of the commentors.

            jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>;
"Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>; "'James
Kempf'" <kempf@docomolabs-usa.com>; <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 12:17 PM
Subject: RE: [seamoby] Update to the requirements draft


> The IESG had turned down the MIPv6 draft due scalability issues - they
> obviously consider the issue to be very important.
> It is obviously important to CT too, as one increases the number of
context
> features to be transferred (perhaps to thousands), the CT protocol
that
> SEAMOBY adopts has to be scalable too.
>
> I think this is a very important requirement, and needs to be spelt
out in
> the requirements draft - otherwise it would be too easy for people to
> overlook it.
>
> -Sharif.
>
>
>  -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Monday, November 19, 2001 3:04 PM
> To: 'Shahrier, Sharif M.'; 'James Kempf'; gkenward@nortelnetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Update to the requirements draft
>
> I don't like the scalability requirement either.
> It is obvious.
>
> Madjid
>
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Monday, November 19, 2001 10:57 AM
> To: 'James Kempf'; Shahrier, Sharif M.; gkenward@nortelnetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Update to the requirements draft
>
>
> James,
>
> It appears that no one really opposed the requirement that "CT
> solution MUST be scalable". It was suggested to shorten  the wording,
> without elaborating on it.. I have some extracts of comments.
>
> Unless there is a large disagreement at this time, perhaps it would
not hurt
> to include it.
> I have noted that "scalability" is a major issue that props up, time
and
> again, in protocols in the IETF.
>
> -Sharif.
>
>
========================================================================
====
> =====================
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be
> > scalable to millions of hosts".
>
> This is 'motherhood & apple pie' text (i.e. - noone would really
> disagree). I don't know how this adds anything to the text.
> Additionally, I would suggest SHOULD rather than MUST is
> what you mean.
>
>
>
> Finally, scaleability is desireable, as long as the requirement is for
> scaleability
> at an acceptable cost.
>  Other then this, I do not know how one would word a requirement
around
> scaleability
> other then the motherhood of "ct must be scaleable at an acceptable
cost".
>
> Gary, Sharif, John,
> if the requirement is a given, then let's not argue about/against it.
It
> cannot
> hurt to include it, and _technically_ there is consensus for it.
> As far as how to phrase it, usually scalability is described as the
marginal
> increase
> in complexity induced by adding users. So something along the lines:
> the processing complexity at each AR (and the burden on the wired
network)
> SHOULD increase linearly with the number of MNs or the number of CT
> requests.
> Also, you can check conformance there.
>
>
>  -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Monday, November 19, 2001 11:34 AM
> To: Shahrier, Sharif M.; gkenward@nortelnetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: Re: [seamoby] Update to the requirements draft
>
> Sharif,
>
> My tracking of the list converstion was that there is  agreement on
> adding *one* requirement, 5.6.1 for the CT protocol to support
handover,
> and modifying the wording on another, 5.1.2, to clarify what is meant
by
> supporting a standardized representation format.
>
>             jak
>
> ----- Original Message -----
> From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> To: <gkenward@nortelnetworks.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Monday, November 19, 2001 6:03 AM
> Subject: [seamoby] Update to the requirements draft
>
>
> > Gary,
> >
> > From our discussions last week, I just want to clarify that, that
> > people had agreed to include two of the requirements that I had
> suggested,
> > also, some wording was changed to one of the existing requirements.
> Can you
> > please confirm that these are going to be updated?
> >
> > -Sharif.
> >
> > "The context transfer solution MUST be scalable".
> >
> > "The context transfer solution MUST include methods for interworking
> with
> > any IETF IP handover solutions".
> >
> > Also, the wording in section 5.1.2 was changed, I believe.
> >
> >
> >
>



From owner-seamoby@diameter.org  Mon Nov 19 16:30:54 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26685
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 16:30:53 -0500 (EST)
Received: (qmail 26385 invoked by alias); 19 Nov 2001 22:16:31 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 26379 invoked by uid 200); 19 Nov 2001 22:16:31 -0000
Received: (qmail 26371 invoked from network); 19 Nov 2001 22:16:29 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 22:16:29 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095QB1>; Mon, 19 Nov 2001 16:27:16 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9AF@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        gkenward@nortelnetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 16:27:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


I would support this. In addition, I would like to add:

I think we should put it in subject to the comments. I don't think it
should say anything about numbers.
How about:

        The CT protocol SHOULD be scalable at an acceptable cost. The CT
protocol SHOULD scale at most linearly
        with the number of participating network nodes.
The CT protocol SHOULD scale at most linearly with the number of contexts
and context features being transferred.

-Sharif.




From owner-seamoby@diameter.org  Mon Nov 19 16:47:47 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA27760
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 16:47:46 -0500 (EST)
Received: (qmail 27072 invoked by alias); 19 Nov 2001 22:34:30 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27066 invoked by uid 200); 19 Nov 2001 22:34:30 -0000
Received: (qmail 27061 invoked from network); 19 Nov 2001 22:34:28 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 22:34:28 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJLhP515221;
	Mon, 19 Nov 2001 13:43:25 -0800 (PST)
Message-ID: <004901c17142$fdbdf730$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9AF@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 13:41:47 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fine with me.

Any other objections? If not, can we call it done and have Gary update
for submission before Wed.?

        jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Shahrier, Sharif M."
<Sharif.Shahrier@InterDigital.com>; "'Nakhjiri Madjid-MNAKHJI1'"
<Madjid.Nakhjiri@motorola.com>; <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 1:27 PM
Subject: RE: [seamoby] Update to the requirements draft


>
> I would support this. In addition, I would like to add:
>
> I think we should put it in subject to the comments. I don't think it
> should say anything about numbers.
> How about:
>
>         The CT protocol SHOULD be scalable at an acceptable cost. The
CT
> protocol SHOULD scale at most linearly
>         with the number of participating network nodes.
> The CT protocol SHOULD scale at most linearly with the number of
contexts
> and context features being transferred.
>
> -Sharif.
>
>
>



From owner-seamoby@diameter.org  Mon Nov 19 16:51:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA28076
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 16:51:25 -0500 (EST)
Received: (qmail 27431 invoked by alias); 19 Nov 2001 22:36:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27424 invoked by uid 200); 19 Nov 2001 22:36:10 -0000
Received: (qmail 27412 invoked from network); 19 Nov 2001 22:36:08 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 22:36:08 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAJLlIS11785
	for <seamoby@cdma-2000.org>; Mon, 19 Nov 2001 16:47:18 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Mon, 19 Nov 2001 16:47:48 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <W9X3C1W2>; Mon, 19 Nov 2001 16:46:51 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4682@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 16:46:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C17143.AFE45990"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17143.AFE45990
Content-Type: text/plain;
	charset="iso-8859-1"

So how do we determine what an acceptable cost is?
Why is linear scaling the objective? Many systems scale
on the order of N^2, and yet are still acceptable in limited 
scenarios they are used. In many cases, the scope of the solution
is limited in order to ensure that the polynomial growth remains
manageable. Route discovery/propagation is a good example.

You provide the example of MIPv6: well, MIP was never designed to
be non-scaleable, just the opposite. There were many ideas that
were tossed because they were not considered scalable. The issue
with MIP scaleability is really a more general issue that has to
do with maintaining SA's over a large mobile population, which,
as the MIP wg discussion should examplify, is a tough problem to
solve. Which just shows that scaleability is a principle, that
has to be evaluated with every new embelishement to the solution,
and there are no fixed criteria.

As I said before, if there's an agreement to require that CT be 
scaleable, fine, then let's add the requirement that "CT MUST be
scaleable" and leave it at that. We could spend a long time trying 
to find a suitable definition of scaleability, and I personally
don't think it will stand the test of time. Mostly because we have
no idea what suitable means. 

Gary

> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: November 19, 2001 16:27
> To: 'James Kempf'; Shahrier, Sharif M.; 'Nakhjiri Madjid-MNAKHJI1';
> Kenward, Gary [WDLN2:AN10:EXCH]
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Update to the requirements draft
> 
> 
> 
> I would support this. In addition, I would like to add:
> 
> I think we should put it in subject to the comments. I don't think it
> should say anything about numbers.
> How about:
> 
>         The CT protocol SHOULD be scalable at an acceptable 
> cost. The CT
> protocol SHOULD scale at most linearly
>         with the number of participating network nodes.
> The CT protocol SHOULD scale at most linearly with the number 
> of contexts
> and context features being transferred.
> 
> -Sharif.
> 
> 
> 

------_=_NextPart_001_01C17143.AFE45990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [seamoby] Update to the requirements draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>So how do we determine what an acceptable cost =
is?</FONT>
<BR><FONT SIZE=3D2>Why is linear scaling the objective? Many systems =
scale</FONT>
<BR><FONT SIZE=3D2>on the order of N^2, and yet are still acceptable in =
limited </FONT>
<BR><FONT SIZE=3D2>scenarios they are used. In many cases, the scope of =
the solution</FONT>
<BR><FONT SIZE=3D2>is limited in order to ensure that the polynomial =
growth remains</FONT>
<BR><FONT SIZE=3D2>manageable. Route discovery/propagation is a good =
example.</FONT>
</P>

<P><FONT SIZE=3D2>You provide the example of MIPv6: well, MIP was never =
designed to</FONT>
<BR><FONT SIZE=3D2>be non-scaleable, just the opposite. There were many =
ideas that</FONT>
<BR><FONT SIZE=3D2>were tossed because they were not considered =
scalable. The issue</FONT>
<BR><FONT SIZE=3D2>with MIP scaleability is really a more general issue =
that has to</FONT>
<BR><FONT SIZE=3D2>do with maintaining SA's over a large mobile =
population, which,</FONT>
<BR><FONT SIZE=3D2>as the MIP wg discussion should examplify, is a =
tough problem to</FONT>
<BR><FONT SIZE=3D2>solve. Which just shows that scaleability is a =
principle, that</FONT>
<BR><FONT SIZE=3D2>has to be evaluated with every new embelishement to =
the solution,</FONT>
<BR><FONT SIZE=3D2>and there are no fixed criteria.</FONT>
</P>

<P><FONT SIZE=3D2>As I said before, if there's an agreement to require =
that CT be </FONT>
<BR><FONT SIZE=3D2>scaleable, fine, then let's add the requirement that =
&quot;CT MUST be</FONT>
<BR><FONT SIZE=3D2>scaleable&quot; and leave it at that. We could spend =
a long time trying </FONT>
<BR><FONT SIZE=3D2>to find a suitable definition of scaleability, and I =
personally</FONT>
<BR><FONT SIZE=3D2>don't think it will stand the test of time. Mostly =
because we have</FONT>
<BR><FONT SIZE=3D2>no idea what suitable means. </FONT>
</P>

<P><FONT SIZE=3D2>Gary</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Shahrier, Sharif M. [<A =
HREF=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: November 19, 2001 16:27</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'James Kempf'; Shahrier, Sharif M.; =
'Nakhjiri Madjid-MNAKHJI1';</FONT>
<BR><FONT SIZE=3D2>&gt; Kenward, Gary [WDLN2:AN10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: seamoby@cdma-2000.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [seamoby] Update to the =
requirements draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I would support this. In addition, I would like =
to add:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think we should put it in subject to the =
comments. I don't think it</FONT>
<BR><FONT SIZE=3D2>&gt; should say anything about numbers.</FONT>
<BR><FONT SIZE=3D2>&gt; How about:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The CT protocol SHOULD be scalable at an acceptable </FONT>
<BR><FONT SIZE=3D2>&gt; cost. The CT</FONT>
<BR><FONT SIZE=3D2>&gt; protocol SHOULD scale at most linearly</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
with the number of participating network nodes.</FONT>
<BR><FONT SIZE=3D2>&gt; The CT protocol SHOULD scale at most linearly =
with the number </FONT>
<BR><FONT SIZE=3D2>&gt; of contexts</FONT>
<BR><FONT SIZE=3D2>&gt; and context features being transferred.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -Sharif.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17143.AFE45990--


From owner-seamoby@diameter.org  Mon Nov 19 16:58:03 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA28426
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 16:57:54 -0500 (EST)
Received: (qmail 27879 invoked by alias); 19 Nov 2001 22:39:42 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 27873 invoked by uid 200); 19 Nov 2001 22:39:42 -0000
Received: (qmail 27860 invoked from network); 19 Nov 2001 22:39:37 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 22:39:37 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095QDV>; Mon, 19 Nov 2001 16:50:19 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9B1@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 16:50:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17144.2DA0C3F0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17144.2DA0C3F0
Content-Type: text/plain;
	charset="iso-8859-1"

I would actually prefer "MUST" as opposed to "SHOULD" wrt scalability.
-Sharif.
 
As I said before, if there's an agreement to require that CT be 
scaleable, fine, then let's add the requirement that "CT MUST be 
scaleable" and leave it at that. We could spend a long time trying 
to find a suitable definition of scaleability, and I personally 
don't think it will stand the test of time. Mostly because we have 
no idea what suitable means. 
Gary 
> -----Original Message----- 
> From: Shahrier, Sharif M. [ mailto:Sharif.Shahrier@InterDigital.com
<mailto:Sharif.Shahrier@InterDigital.com> ] 
> Sent: November 19, 2001 16:27 
> To: 'James Kempf'; Shahrier, Sharif M.; 'Nakhjiri Madjid-MNAKHJI1'; 
> Kenward, Gary [WDLN2:AN10:EXCH] 
> Cc: seamoby@cdma-2000.org 
> Subject: RE: [seamoby] Update to the requirements draft 
> 
> 
> 
> I would support this. In addition, I would like to add: 
> 
> I think we should put it in subject to the comments. I don't think it 
> should say anything about numbers. 
> How about: 
> 
>         The CT protocol SHOULD be scalable at an acceptable 
> cost. The CT 
> protocol SHOULD scale at most linearly 
>         with the number of participating network nodes. 
> The CT protocol SHOULD scale at most linearly with the number 
> of contexts 
> and context features being transferred. 
> 
> -Sharif. 
> 
> 
> 

------_=_NextPart_001_01C17144.2DA0C3F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C1711B.0C019310">
<title>RE: [seamoby] Update to the requirements draft</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p><font size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:navy'>I would actually prefer &#8220;MUST&#8221; as opposed to =
&#8220;SHOULD&#8221; wrt
scalability.</span></font><font size=3D2 color=3Dnavy><span =
style=3D'font-size:10.0pt;
color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:navy'>-Sharif.</span></font><font size=3D2 color=3Dnavy><span
style=3D'font-size:10.0pt;color:navy;mso-color-alt:windowtext'><o:p></o:=
p></span></font></p>

<p><font size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:navy'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
size=3D2 color=3Dnavy><span =
style=3D'font-size:10.0pt;color:navy;mso-color-alt:windowtext'><o:p></o:=
p></span></font></p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>As I said before, if there's an agreement to require that =
CT be </span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>scaleable, fine, then let's add the requirement that =
&quot;CT MUST
be</span></font><font color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>scaleable&quot; and leave it at that. We could spend a =
long time
trying </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>to find a suitable definition of scaleability, and I =
personally</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>don't think it will stand the test of time. Mostly because =
we have</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>no idea what suitable means. </span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>Gary</span></font><font color=3Dblack><span =
style=3D'color:black'> </span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&gt; -----Original Message-----</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; From: Shahrier, Sharif M. [<a
href=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</a>]</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Sent: November 19, 2001 16:27</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; To: 'James Kempf'; Shahrier, Sharif M.; 'Nakhjiri
Madjid-MNAKHJI1';</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Kenward, Gary [WDLN2:AN10:EXCH]</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Cc: seamoby@cdma-2000.org</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; Subject: RE: [seamoby] Update to the requirements =
draft</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; I would support this. In addition, I would like to =
add:</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; I think we should put it in subject to the comments. =
I don't
think it</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; should say anything about numbers.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; How about:</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
CT
protocol SHOULD be scalable at an acceptable </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; cost. The CT</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; protocol SHOULD scale at most =
linearly</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
the
number of participating network nodes.</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; The CT protocol SHOULD scale at most linearly with =
the number
</span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; of contexts</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; and context features being =
transferred.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; -Sharif.</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&gt; </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C17144.2DA0C3F0--


From owner-seamoby@diameter.org  Mon Nov 19 17:18:34 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA29699
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 17:18:33 -0500 (EST)
Received: (qmail 28744 invoked by alias); 19 Nov 2001 23:05:02 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28738 invoked by uid 200); 19 Nov 2001 23:05:02 -0000
Received: (qmail 28733 invoked from network); 19 Nov 2001 23:05:00 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 23:05:00 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJMFT516664;
	Mon, 19 Nov 2001 14:15:30 -0800 (PST)
Message-ID: <006601c17147$78d1da00$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>,
        "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
References: <9FBD322B7824D511B36900508BF93C9C01AA4682@zcard031.ca.nortel.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 14:13:52 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary,

Alright, how about:

    The CT solution MUST be scalable.

            jak

----- Original Message -----
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>; "'James
Kempf'" <kempf@docomolabs-usa.com>; "'Nakhjiri Madjid-MNAKHJI1'"
<Madjid.Nakhjiri@motorola.com>
Cc: <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 1:46 PM
Subject: RE: [seamoby] Update to the requirements draft


> So how do we determine what an acceptable cost is?
> Why is linear scaling the objective? Many systems scale
> on the order of N^2, and yet are still acceptable in limited
> scenarios they are used. In many cases, the scope of the solution
> is limited in order to ensure that the polynomial growth remains
> manageable. Route discovery/propagation is a good example.
>
> You provide the example of MIPv6: well, MIP was never designed to
> be non-scaleable, just the opposite. There were many ideas that
> were tossed because they were not considered scalable. The issue
> with MIP scaleability is really a more general issue that has to
> do with maintaining SA's over a large mobile population, which,
> as the MIP wg discussion should examplify, is a tough problem to
> solve. Which just shows that scaleability is a principle, that
> has to be evaluated with every new embelishement to the solution,
> and there are no fixed criteria.
>
> As I said before, if there's an agreement to require that CT be
> scaleable, fine, then let's add the requirement that "CT MUST be
> scaleable" and leave it at that. We could spend a long time trying
> to find a suitable definition of scaleability, and I personally
> don't think it will stand the test of time. Mostly because we have
> no idea what suitable means.
>
> Gary
>
> > -----Original Message-----
> > From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> > Sent: November 19, 2001 16:27
> > To: 'James Kempf'; Shahrier, Sharif M.; 'Nakhjiri Madjid-MNAKHJI1';
> > Kenward, Gary [WDLN2:AN10:EXCH]
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] Update to the requirements draft
> >
> >
> >
> > I would support this. In addition, I would like to add:
> >
> > I think we should put it in subject to the comments. I don't think
it
> > should say anything about numbers.
> > How about:
> >
> >         The CT protocol SHOULD be scalable at an acceptable
> > cost. The CT
> > protocol SHOULD scale at most linearly
> >         with the number of participating network nodes.
> > The CT protocol SHOULD scale at most linearly with the number
> > of contexts
> > and context features being transferred.
> >
> > -Sharif.
> >
> >
> >
>



From owner-seamoby@diameter.org  Mon Nov 19 17:31:05 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA00338
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 17:31:03 -0500 (EST)
Received: (qmail 29323 invoked by alias); 19 Nov 2001 23:17:38 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29317 invoked by uid 200); 19 Nov 2001 23:17:37 -0000
Received: (qmail 29311 invoked from network); 19 Nov 2001 23:17:34 -0000
Received: from mailhost.iprg.nokia.com (205.226.5.12)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 23:17:34 -0000
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 OAA22687;
	Mon, 19 Nov 2001 14:29:23 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fAJMTMl12273;
	Mon, 19 Nov 2001 14:29:22 -0800
X-mProtect:  Mon, 19 Nov 2001 14:29:22 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdn7BpCR; Mon, 19 Nov 2001 14:29:21 PST
Message-ID: <3BF987C1.19F87D3A@iprg.nokia.com>
Date: Mon, 19 Nov 2001 14:29:21 -0800
From: Rajeev Koodli <rajeev@IPRG.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        gkenward@nortelnetworks.com, seamoby@cdma-2000.org
Subject: Re: [seamoby] Update to the requirements draft
References: <A1170612471BD21185B90008C7FA0A0D0327F9AF@idcpa4.pa.interdigital.com> <004901c17142$fdbdf730$0e02320a@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


James,

while I strongly support the desire to move ahead, it is not a good idea
to incorporate a requirement without a clear sense of what it means.. As
Gary pointed out, having a criterion to evaluate scalability is tricky.
I can resonably understand what is "acceptable cost"; however, it is not
something we can use to evaluate alternatives.

Regards,

-Rajeev


James Kempf wrote:

> Fine with me.
>
> Any other objections? If not, can we call it done and have Gary update
> for submission before Wed.?
>
>         jak
>
> ----- Original Message -----
> From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Shahrier, Sharif M."
> <Sharif.Shahrier@InterDigital.com>; "'Nakhjiri Madjid-MNAKHJI1'"
> <Madjid.Nakhjiri@motorola.com>; <gkenward@nortelnetworks.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Monday, November 19, 2001 1:27 PM
> Subject: RE: [seamoby] Update to the requirements draft
>
> >
> > I would support this. In addition, I would like to add:
> >
> > I think we should put it in subject to the comments. I don't think it
> > should say anything about numbers.
> > How about:
> >
> >         The CT protocol SHOULD be scalable at an acceptable cost. The
> CT
> > protocol SHOULD scale at most linearly
> >         with the number of participating network nodes.
> > The CT protocol SHOULD scale at most linearly with the number of
> contexts
> > and context features being transferred.
> >
> > -Sharif.
> >
> >
> >



From owner-seamoby@diameter.org  Mon Nov 19 17:36:09 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA00771
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 17:36:08 -0500 (EST)
Received: (qmail 29865 invoked by alias); 19 Nov 2001 23:22:38 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29859 invoked by uid 200); 19 Nov 2001 23:22:38 -0000
Received: (qmail 29854 invoked from network); 19 Nov 2001 23:22:36 -0000
Received: from motgate.mot.com (129.188.136.100)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 23:22:36 -0000
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (motgate 2.1) with ESMTP id PAA15411 for <seamoby@cdma-2000.org>; Mon, 19 Nov 2001 15:35:02 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id PAA14504 for <seamoby@cdma-2000.org>; Mon, 19 Nov 2001 15:35:02 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <VRW8QCSV>; Mon, 19 Nov 2001 16:35:02 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FB79@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Rajeev Koodli'" <rajeev@IPRG.nokia.com>,
        James Kempf <kempf@docomolabs-usa.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        gkenward@nortelnetworks.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 16:35:01 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

I agree with Rajeev. I still don't see a reason for a requirement
for which no compliance test exist, we have been through this extensively
long time ago and agreed it was not necessary.
If I write a proposal for CT, how can I prove it is scalable. It is like
asking a car company to make "nice" cars...

-----Original Message-----
From: Rajeev Koodli [mailto:rajeev@IPRG.nokia.com]
Sent: Monday, November 19, 2001 4:29 PM
To: James Kempf
Cc: Shahrier, Sharif M.; 'Nakhjiri Madjid-MNAKHJI1';
gkenward@nortelnetworks.com; seamoby@cdma-2000.org
Subject: Re: [seamoby] Update to the requirements draft



James,

while I strongly support the desire to move ahead, it is not a good idea
to incorporate a requirement without a clear sense of what it means.. As
Gary pointed out, having a criterion to evaluate scalability is tricky.
I can resonably understand what is "acceptable cost"; however, it is not
something we can use to evaluate alternatives.

Regards,

-Rajeev


James Kempf wrote:

> Fine with me.
>
> Any other objections? If not, can we call it done and have Gary update
> for submission before Wed.?
>
>         jak
>
> ----- Original Message -----
> From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Shahrier, Sharif M."
> <Sharif.Shahrier@InterDigital.com>; "'Nakhjiri Madjid-MNAKHJI1'"
> <Madjid.Nakhjiri@motorola.com>; <gkenward@nortelnetworks.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Monday, November 19, 2001 1:27 PM
> Subject: RE: [seamoby] Update to the requirements draft
>
> >
> > I would support this. In addition, I would like to add:
> >
> > I think we should put it in subject to the comments. I don't think it
> > should say anything about numbers.
> > How about:
> >
> >         The CT protocol SHOULD be scalable at an acceptable cost. The
> CT
> > protocol SHOULD scale at most linearly
> >         with the number of participating network nodes.
> > The CT protocol SHOULD scale at most linearly with the number of
> contexts
> > and context features being transferred.
> >
> > -Sharif.
> >
> >
> >


From owner-seamoby@diameter.org  Mon Nov 19 17:47:03 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01498
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Nov 2001 17:47:03 -0500 (EST)
Received: (qmail 30432 invoked by alias); 19 Nov 2001 23:33:22 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 30426 invoked by uid 200); 19 Nov 2001 23:33:21 -0000
Received: (qmail 30421 invoked from network); 19 Nov 2001 23:33:20 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 19 Nov 2001 23:33:20 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAJMch517825;
	Mon, 19 Nov 2001 14:38:43 -0800 (PST)
Message-ID: <00a001c1714a$b7a9ed50$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@IPRG.nokia.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        <gkenward@nortelnetworks.com>, <seamoby@cdma-2000.org>
References: <A1170612471BD21185B90008C7FA0A0D0327F9AF@idcpa4.pa.interdigital.com> <004901c17142$fdbdf730$0e02320a@T23KEMPF> <3BF987C1.19F87D3A@iprg.nokia.com>
Subject: Re: [seamoby] Update to the requirements draft
Date: Mon, 19 Nov 2001 14:37:06 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sharif,

We cannot get concensus on this requirement.

I would suggest we drop it and move ahead with the draft given two
additions, namely 5.6.1 and modified wording for 5.1.2.
Sorry.

Gary, Rajeev, Sharif,

If the IESG decides they want a scability requirement, you can be
assured we will get a comment back and we will need to put one in. But
we can try it and see.

Gary,

Can you please write up the draft with these modifications and submit
it? We really *do* need to get moving on this.

            jak

----- Original Message -----
From: "Rajeev Koodli" <rajeev@IPRG.nokia.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>; "'Nakhjiri
Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>;
<gkenward@nortelnetworks.com>; <seamoby@cdma-2000.org>
Sent: Monday, November 19, 2001 2:29 PM
Subject: Re: [seamoby] Update to the requirements draft


>
> James,
>
> while I strongly support the desire to move ahead, it is not a good
idea
> to incorporate a requirement without a clear sense of what it means..
As
> Gary pointed out, having a criterion to evaluate scalability is
tricky.
> I can resonably understand what is "acceptable cost"; however, it is
not
> something we can use to evaluate alternatives.
>
> Regards,
>
> -Rajeev
>
>
> James Kempf wrote:
>
> > Fine with me.
> >
> > Any other objections? If not, can we call it done and have Gary
update
> > for submission before Wed.?
> >
> >         jak
> >
> > ----- Original Message -----
> > From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> > To: "'James Kempf'" <kempf@docomolabs-usa.com>; "Shahrier, Sharif
M."
> > <Sharif.Shahrier@InterDigital.com>; "'Nakhjiri Madjid-MNAKHJI1'"
> > <Madjid.Nakhjiri@motorola.com>; <gkenward@nortelnetworks.com>
> > Cc: <seamoby@cdma-2000.org>
> > Sent: Monday, November 19, 2001 1:27 PM
> > Subject: RE: [seamoby] Update to the requirements draft
> >
> > >
> > > I would support this. In addition, I would like to add:
> > >
> > > I think we should put it in subject to the comments. I don't think
it
> > > should say anything about numbers.
> > > How about:
> > >
> > >         The CT protocol SHOULD be scalable at an acceptable cost.
The
> > CT
> > > protocol SHOULD scale at most linearly
> > >         with the number of participating network nodes.
> > > The CT protocol SHOULD scale at most linearly with the number of
> > contexts
> > > and context features being transferred.
> > >
> > > -Sharif.
> > >
> > >
> > >
>
>



From owner-seamoby@diameter.org  Tue Nov 20 04:25:42 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA02535
	for <seamoby-archive@lists.ietf.org>; Tue, 20 Nov 2001 04:25:42 -0500 (EST)
Received: (qmail 864 invoked by alias); 20 Nov 2001 10:12:21 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 858 invoked by uid 200); 20 Nov 2001 10:12:21 -0000
Received: (qmail 853 invoked from network); 20 Nov 2001 10:12:19 -0000
Received: from mgw-dax1.ext.nokia.com (63.78.179.216)
  by c900656-a.plstn1.sfba.home.com with SMTP; 20 Nov 2001 10:12:19 -0000
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAK9OnQ07497
	for <seamoby@diameter.org>; Tue, 20 Nov 2001 03:24:50 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5754317decac12f256126@davir03nok.americas.nokia.com> for <seamoby@diameter.org>;
 Tue, 20 Nov 2001 03:24:44 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 20 Nov 2001 03:24:27 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
Subject: [seamoby] New draft - IPSec Context Transfer
Date: Tue, 20 Nov 2001 04:24:43 -0500
MIME-Version: 1.0
Message-ID: <DC504E9C3384054C8506D3E6BB01246006E09A@bsebe001.NOE.Nokia.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: New draft - IPSec Context Transfer
Thread-Index: AcFxpetrhTjZ7V0ETXqk38mvRnIycg==
From: "Gopal Ram \(NRC/Boston\)" <ram.gopal@nokia.com>
To: <seamoby@diameter.org>
Cc: "Sengodan Senthil \(NRC/Boston\)" <senthil.sengodan@nokia.com>,
        "Krishnamurthi Govind \(NRC/Boston\)" <Govind.Krishnamurthi@nokia.com>,
        "Devarapalli Vijay \(NRC/MtView\)" <Vijay.Devarapalli@nokia.com>,
        "Koodli Rajeev \(NRC/MtView\)" <rajeev.koodli@nokia.com>,
        "Perkins Charles \(IPRG/MtView\)" <Charles.Perkins@nokia.com>
X-OriginalArrivalTime: 20 Nov 2001 09:24:28.0062 (UTC) FILETIME=[26FB23E0:01C171A5]
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA02535

Hello All,

We would like to announce the availability of a new Internet 
Draft - "IPSec Context Transfer"

http://www.ietf.org/internet-drafts/draft-gopal-seamoby-ipsec-relocate-0
0.txt


Thanks and Regards
Ramg


P.S: We also posted "Issues in IPSec Context Transfer"  but has not
shown up in IETF  website.



From owner-seamoby@diameter.org  Tue Nov 20 07:20:32 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA05237
	for <seamoby-archive@lists.ietf.org>; Tue, 20 Nov 2001 07:20:32 -0500 (EST)
Received: (qmail 2236 invoked by alias); 20 Nov 2001 13:01:40 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2228 invoked by uid 200); 20 Nov 2001 13:01:39 -0000
Received: (qmail 2217 invoked from network); 20 Nov 2001 13:01:36 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 20 Nov 2001 13:01:36 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04716;
	Tue, 20 Nov 2001 07:14:00 -0500 (EST)
Message-Id: <200111201214.HAA04716@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-trossen-seamoby-cardiscovery-00.txt
Date: Tue, 20 Nov 2001 07:13:59 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Protocol for Candidate Access Router Discovery for 
                          Seamless IP-level Handovers
	Author(s)	: D. Trossen et al.
	Filename	: draft-trossen-seamoby-cardiscovery-00.txt
	Pages		: 15
	Date		: 19-Nov-01
	
A critical requirement in the protocols being designed for seamless 
IP-level handovers, such as fast handover and context transfer, is 
that the target access router (TAR) for the mobile node's (MN) 
handover is known to the current access router (AR). The TAR needs to 
have the capability set necessary to meet the MN's requirements, and 
meet any local policy requirements. While the TAR selection process 
happens at the time of handover, the ARs which have the capabilities 
to meet the MN's requirements can be identified in advance. These 
ARs are called candidate access routers (CARs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-trossen-seamoby-cardiscovery-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-trossen-seamoby-cardiscovery-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-trossen-seamoby-cardiscovery-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011119140830.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-trossen-seamoby-cardiscovery-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-trossen-seamoby-cardiscovery-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011119140830.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Tue Nov 20 13:16:55 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA25592
	for <seamoby-archive@odin.ietf.org>; Tue, 20 Nov 2001 13:16:55 -0500 (EST)
Received: (qmail 4239 invoked by alias); 20 Nov 2001 19:02:40 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4233 invoked by uid 200); 20 Nov 2001 19:02:39 -0000
Received: (qmail 4228 invoked from network); 20 Nov 2001 19:02:38 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 20 Nov 2001 19:02:38 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAKIEa525963
	for <seamoby@diameter.org>; Tue, 20 Nov 2001 10:14:36 -0800 (PST)
Message-ID: <011e01c171ee$fc3ac670$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@diameter.org>
Subject: [seamoby] Paging Protocol Assessment and CT Problem Statement
Date: Tue, 20 Nov 2001 10:12:58 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I submitted the paging protocol assessment draft last week on Tues. but
got email from odin.isi.edu on Wed. that the mail had been delayed, so I
am not sure whether it got in on time. The actual email from the
Internet Drafts saying it was received arrived on Thurs.

I submitted 04 draft of the CT problem statement today, so, provided
odin doesn't get full again, it should be there before the deadline.

In any event, I've put the paging protocol assessment and the 04 draft
of the CT problem statement on my Geocities web site.
They are available through the following links:


http://www.geocities.com/kempf42/draft-ietf-seamoby-context-transfer-pro
blem-stat-04.txt

http://www.geocities.com/kempf42/draft-ietf-seamoby-paging-protocol-asse
ssment-00.txt

                jak



From owner-seamoby@diameter.org  Wed Nov 21 13:11:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28068
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Nov 2001 13:11:27 -0500 (EST)
Received: (qmail 13220 invoked by alias); 21 Nov 2001 18:57:54 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13214 invoked by uid 200); 21 Nov 2001 18:57:54 -0000
Received: (qmail 13209 invoked from network); 21 Nov 2001 18:57:52 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 21 Nov 2001 18:57:52 -0000
Received: from VAIOHE (dhcp5.docomo-usa.com [172.21.96.5])
	by docomolabs-usa.com (8.11.3/8.11.3) with ESMTP id fALI9r510499;
	Wed, 21 Nov 2001 10:09:53 -0800 (PST)
Reply-To: <xiaoning@docomolabs-usa.com>
From: "Xiaoning He" <xiaoning@docomolabs-usa.com>
To: "IETF-Seamoby Working Group" <seamoby@diameter.org>
Cc: "Atsushi Takeshita" <takeshita@docomolabs-usa.com>,
        "Carl Williams" <carlw@docomolabs-usa.com>,
        "Daichi Funato" <funato@docomolabs-usa.com>
Subject: [seamoby] GAARD Draft
Date: Wed, 21 Nov 2001 10:09:03 -0800
Organization: NTT-Docomo USA Labs
Message-ID: <000001c172b7$9a139200$056015ac@VAIOHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello all

We have submitted a draft for the SEAMOBY working group. I am not sure
when an announcement will be sent to this alias. You can access the
draft at following address

http://www.inogroup.com/apps/docomo/publications/docs/draft-funato-seamo
by-gaard-00.txt


FYI....

Xiaoning He




From owner-seamoby@diameter.org  Wed Nov 21 17:11:53 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10911
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Nov 2001 17:11:51 -0500 (EST)
Received: (qmail 16062 invoked by alias); 21 Nov 2001 22:56:50 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 16056 invoked by uid 200); 21 Nov 2001 22:56:49 -0000
Received: (qmail 16050 invoked from network); 21 Nov 2001 22:56:47 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 21 Nov 2001 22:56:47 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fALM84S16222
	for <seamoby@diameter.org>; Wed, 21 Nov 2001 17:08:04 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 21 Nov 2001 17:08:33 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <XJ9SAKX3>; Wed, 21 Nov 2001 17:07:34 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA4696@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "Seamoby \(E-mail\)" <seamoby@diameter.org>
Subject: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Wed, 21 Nov 2001 17:07:33 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C172D8.EB8CF330"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C172D8.EB8CF330
Content-Type: text/plain;
	charset="ISO-8859-1"

To help everyone with the newest release, below is a list
of *all* the changes that I have made. I made these changes
based upon the decisions of the working group chairs. I believe
I captured all the accepted changes. In some cases, I had to word 
smith, but I tried to keep the changes to a minimum.

Hope you like it.

Gary


1. Company names removed from author's list

2. 4.9 changed from:

  4.9 The entities transferring context MUST have completed a mutual
      authentication process prior to initiating the transfer. 

to:

  4.9 The entities transferring context MUST support a process for mutual
      authentication prior to initiating the transfer. 

3. 4.13 changed from:

  4.13 The context information provided for transfer MUST be reliable.

to:

  4.13 The context transfer solution WILL NOT verify the context information
       prior to transfer.
  
     The context transfer solution may provide mechanisms to support the 
     reliable transfer of context, however, it is not the purpose of the
context
     transfer solution to verify the context at the source prior to
transfer. 

     The effectiveness of context transfer in enhancing handover between ARs

     would very likely be compromised if the context at the source is
malformed.
     Nonetheless, ensuring the integrity of the context at the source
requires
     specific knowledge of the syntax and semantics of the context
representation
     for each feature and this is outside the scope of the context transfer
solution.

4. New (note: this requirements was suggested for section 5 - 5.6.1, however
it
   seems to fit better in second 4, right after the mobility requirements):

  4.16 The context transfer solution MUST include methods for interworking
       with any IETF IP handover solutions.

5. New:

  4.17 The context transfer solution MUST be scalable.

6. 5.1.2 changed from:

  5.1.2 The context transfer protocol design MUST define a standard 
        representation for conveying context information that will be 
        interpreted uniformly and perspicuously by different 
        implementations.

to
 
  5.1.2 The context transfer protocol design MUST define a standard 
        representation for encapsulating context information in the IP
packet
        payload that will be interpreted uniformly and perspicuously by 
        different implementations.
 
  Note: I couldn't come up with a better term then "encapsulate".
Denotatively,
  it is an accurate description of what should happen. I'm not sure what
connotative
  baggage the term carries.

Gary

------_=_NextPart_001_01C172D8.EB8CF330
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>draft-ietf-seamoby-ct-reqs-02.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>To help everyone with the newest release, below is a list</FONT>
<BR><FONT SIZE=2>of *all* the changes that I have made. I made these changes</FONT>
<BR><FONT SIZE=2>based upon the decisions of the working group chairs. I believe</FONT>
<BR><FONT SIZE=2>I captured all the accepted changes. In some cases, I had to word </FONT>
<BR><FONT SIZE=2>smith, but I tried to keep the changes to a minimum.</FONT>
</P>

<P><FONT SIZE=2>Hope you like it.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>
<BR>

<P><FONT SIZE=2>1. Company names removed from author's list</FONT>
</P>

<P><FONT SIZE=2>2. 4.9 changed from:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.9 The entities transferring context MUST have completed a mutual</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authentication process prior to initiating the transfer. </FONT>
</P>

<P><FONT SIZE=2>to:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.9 The entities transferring context MUST support a process for mutual</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authentication prior to initiating the transfer. </FONT>
</P>

<P><FONT SIZE=2>3. 4.13 changed from:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.13 The context information provided for transfer MUST be reliable.</FONT>
</P>

<P><FONT SIZE=2>to:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.13 The context transfer solution WILL NOT verify the context information</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; prior to transfer.</FONT>
<BR><FONT SIZE=2>&nbsp; </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; The context transfer solution may provide mechanisms to support the </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; reliable transfer of context, however, it is not the purpose of the context</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; transfer solution to verify the context at the source prior to transfer. </FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; The effectiveness of context transfer in enhancing handover between ARs </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; would very likely be compromised if the context at the source is malformed.</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Nonetheless, ensuring the integrity of the context at the source requires</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; specific knowledge of the syntax and semantics of the context representation</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; for each feature and this is outside the scope of the context transfer solution.</FONT>
</P>

<P><FONT SIZE=2>4. New (note: this requirements was suggested for section 5 - 5.6.1, however it</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; seems to fit better in second 4, right after the mobility requirements):</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.16 The context transfer solution MUST include methods for interworking</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with any IETF IP handover solutions.</FONT>
</P>

<P><FONT SIZE=2>5. New:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 4.17 The context transfer solution MUST be scalable.</FONT>
</P>

<P><FONT SIZE=2>6. 5.1.2 changed from:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; 5.1.2 The context transfer protocol design MUST define a standard </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; representation for conveying context information that will be </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interpreted uniformly and perspicuously by different </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementations.</FONT>
</P>

<P><FONT SIZE=2>to</FONT>
<BR><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>&nbsp; 5.1.2 The context transfer protocol design MUST define a standard </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; representation for encapsulating context information in the IP packet</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; payload that will be interpreted uniformly and perspicuously by </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; different implementations.</FONT>
<BR><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>&nbsp; Note: I couldn't come up with a better term then &quot;encapsulate&quot;. Denotatively,</FONT>
<BR><FONT SIZE=2>&nbsp; it is an accurate description of what should happen. I'm not sure what connotative</FONT>
<BR><FONT SIZE=2>&nbsp; baggage the term carries.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C172D8.EB8CF330--


From owner-seamoby@diameter.org  Wed Nov 21 19:08:24 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA14061
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Nov 2001 19:08:23 -0500 (EST)
Received: (qmail 17427 invoked by alias); 22 Nov 2001 00:54:55 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 17421 invoked by uid 200); 22 Nov 2001 00:54:55 -0000
Received: (qmail 17416 invoked from network); 22 Nov 2001 00:54:52 -0000
Received: from bells.cs.ucl.ac.uk (128.16.5.31)
  by c900656-a.plstn1.sfba.home.com with SMTP; 22 Nov 2001 00:54:52 -0000
Received: from bohemian.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.13856-0@bells.cs.ucl.ac.uk>; Thu, 22 Nov 2001 00:02:29 +0000
Message-ID: <3BFC4094.1DB0830F@cs.ucl.ac.uk>
Date: Thu, 22 Nov 2001 00:02:28 +0000
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: t.pagtzis@cs.ucl.ac.uk
Organization: UCL/Mobile Systems Group
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: xiaoning <xiaoning@docomolabs-usa.com>
CC: IETF-Seamoby Working Group <seamoby@diameter.org>,
        Atsushi Takeshita <takeshita@docomolabs-usa.com>,
        Carl Williams <carlw@docomolabs-usa.com>,
        Daichi Funato <funato@docomolabs-usa.com>
Subject: Re: [seamoby] GAARD Draft
References: <000001c172b7$9a139200$056015ac@VAIOHE>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Xiaoning,

  While I appreciate your work, I am surpized not to see my work
referred anywhere in your proposal (like others), since I have already
proposed something like that back in July where the core element
revolves about the distinction between the mobility and routing
neighbourhood.

Please see

http://search.ietf.org/internet-drafts/draft-pagtzis-seamoby-proactivev6-00.txt

Regards

Theo
UCL/Mobile Systems Group


Xiaoning He wrote:
> 
> Hello all
> 
> We have submitted a draft for the SEAMOBY working group. I am not sure
> when an announcement will be sent to this alias. You can access the
> draft at following address
> 
> http://www.inogroup.com/apps/docomo/publications/docs/draft-funato-seamo
> by-gaard-00.txt
> 
> FYI....
> 
> Xiaoning He


From owner-seamoby@diameter.org  Sat Nov 24 21:24:51 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA27191
	for <seamoby-archive@odin.ietf.org>; Sat, 24 Nov 2001 21:24:50 -0500 (EST)
Received: (qmail 29457 invoked by alias); 25 Nov 2001 03:11:14 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29451 invoked by uid 200); 25 Nov 2001 03:11:13 -0000
Received: (qmail 29446 invoked from network); 25 Nov 2001 03:11:11 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 25 Nov 2001 03:11:11 -0000
Received: from VAIOHE (dhcp53.docomo-usa.com [172.21.96.53])
	by docomolabs-usa.com (8.11.3/8.11.3) with ESMTP id fAP2NH514377;
	Sat, 24 Nov 2001 18:23:17 -0800 (PST)
Reply-To: <xiaoning@docomolabs-usa.com>
From: "Xiaoning He" <xiaoning@docomolabs-usa.com>
To: <t.pagtzis@cs.ucl.ac.uk>
Cc: "'IETF-Seamoby Working Group'" <seamoby@diameter.org>,
        "'Atsushi Takeshita'" <takeshita@docomolabs-usa.com>,
        "'Carl Williams'" <carlw@docomolabs-usa.com>,
        "'Daichi Funato'" <funato@docomolabs-usa.com>
Subject: RE: [seamoby] GAARD Draft
Date: Sat, 24 Nov 2001 18:22:25 -0800
Organization: NTT-Docomo USA Labs
Message-ID: <000001c17558$065a2f30$356015ac@VAIOHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <3BFC4094.1DB0830F@cs.ucl.ac.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Theo

We really appreciate your comments on our draft. Since the draft is
still at its .00 statuses, we didn't intent to neglect your work.
Probably we just missed it.

My initial impression with your draft is that your draft is a
comprehensive framework which proposed a new scheme for mobility. So, it
will be very helpful if you can further let us know which part of your
draft contains the similar contents as ours. 

Thank you

Xiaoning He 

-----Original Message-----
From: owner-seamoby@diameter.org [mailto:owner-seamoby@diameter.org] On
Behalf Of Theo Pagtzis
Sent: Wednesday, November 21, 2001 4:02 PM
To: xiaoning
Cc: IETF-Seamoby Working Group; Atsushi Takeshita; Carl Williams; Daichi
Funato
Subject: Re: [seamoby] GAARD Draft

Hello Xiaoning,

  While I appreciate your work, I am surpized not to see my work
referred anywhere in your proposal (like others), since I have already
proposed something like that back in July where the core element
revolves about the distinction between the mobility and routing
neighbourhood.

Please see

http://search.ietf.org/internet-drafts/draft-pagtzis-seamoby-proactivev6
-00.txt

Regards

Theo
UCL/Mobile Systems Group


Xiaoning He wrote:
> 
> Hello all
> 
> We have submitted a draft for the SEAMOBY working group. I am not sure
> when an announcement will be sent to this alias. You can access the
> draft at following address
> 
>
http://www.inogroup.com/apps/docomo/publications/docs/draft-funato-seamo
> by-gaard-00.txt
> 
> FYI....
> 
> Xiaoning He




From owner-seamoby@diameter.org  Sun Nov 25 10:21:17 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA20936
	for <seamoby-archive@lists.ietf.org>; Sun, 25 Nov 2001 10:21:15 -0500 (EST)
Received: (qmail 4388 invoked by alias); 25 Nov 2001 16:07:11 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4382 invoked by uid 200); 25 Nov 2001 16:07:11 -0000
Received: (qmail 4373 invoked by uid 500); 25 Nov 2001 16:07:10 -0000
Date: Sun, 25 Nov 2001 08:07:10 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: "'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
        "'James Kempf'" <kempf@docomolabs-usa.com>,
        gkenward@nortelnetworks.com, seamoby@cdma-2000.org
Subject: Re: [seamoby] Update to the requirements draft
Message-ID: <20011125080710.F3988@charizard.diameter.org>
Mail-Followup-To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
	"'Shahrier, Sharif M.'" <Sharif.Shahrier@InterDigital.com>,
	'James Kempf' <kempf@docomolabs-usa.com>,
	gkenward@nortelnetworks.com, seamoby@cdma-2000.org
References: <35DBB8B7AC89D4118E98009027B1009B0464FB74@IL27EXM10.cig.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B0464FB74@IL27EXM10.cig.mot.com>; from Madjid.Nakhjiri@motorola.com on Mon, Nov 19, 2001 at 02:04:05PM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

...and requirements that cannot be quantified are of dubious value.
When, and if, we have to evaluate protocols against requirements, how do
we determine whether a protocol scales (as per this requirement)?

I'm really not sure it's needed, unless it is more specific, and I believe
that the IETF mandates protocols that scales to the millions of hosts
anyways.

PatC
On Mon, Nov 19, 2001 at 02:04:05PM -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> I don't like the scalability requirement either.
> It is obvious.
> 
> Madjid
> 
> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Monday, November 19, 2001 10:57 AM
> To: 'James Kempf'; Shahrier, Sharif M.; gkenward@nortelnetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] Update to the requirements draft
> 
> 
> James,
> 
> 	It appears that no one really opposed the requirement that "CT
> solution MUST be scalable". It was suggested to shorten  the wording,
> without elaborating on it.. I have some extracts of comments.
> 
> Unless there is a large disagreement at this time, perhaps it would not hurt
> to include it.
> I have noted that "scalability" is a major issue that props up, time and
> again, in protocols in the IETF.
> 
> -Sharif.
> 
> ============================================================================
> =====================
> > 4.16 "The context transfer protocol MUST be scalable. It MUST be 
> > scalable to millions of hosts".
> 
> This is 'motherhood & apple pie' text (i.e. - noone would really
> disagree). I don't know how this adds anything to the text.  
> Additionally, I would suggest SHOULD rather than MUST is
> what you mean.
> 
> 
> 
> Finally, scaleability is desireable, as long as the requirement is for
> scaleability 
> at an acceptable cost. 
>  Other then this, I do not know how one would word a requirement around
> scaleability 
> other then the motherhood of "ct must be scaleable at an acceptable cost". 
> 
> Gary, Sharif, John, 
> if the requirement is a given, then let's not argue about/against it. It
> cannot 
> hurt to include it, and _technically_ there is consensus for it. 
> As far as how to phrase it, usually scalability is described as the marginal
> increase 
> in complexity induced by adding users. So something along the lines: 
> the processing complexity at each AR (and the burden on the wired network) 
> SHOULD increase linearly with the number of MNs or the number of CT
> requests. 
> Also, you can check conformance there. 
> 
> 
>  -----Original Message-----
> From: 	James Kempf [mailto:kempf@docomolabs-usa.com] 
> Sent:	Monday, November 19, 2001 11:34 AM
> To:	Shahrier, Sharif M.; gkenward@nortelnetworks.com
> Cc:	seamoby@cdma-2000.org
> Subject:	Re: [seamoby] Update to the requirements draft
> 
> Sharif,
> 
> My tracking of the list converstion was that there is  agreement on
> adding *one* requirement, 5.6.1 for the CT protocol to support handover,
> and modifying the wording on another, 5.1.2, to clarify what is meant by
> supporting a standardized representation format.
> 
>             jak
> 
> ----- Original Message -----
> From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
> To: <gkenward@nortelnetworks.com>
> Cc: <seamoby@cdma-2000.org>
> Sent: Monday, November 19, 2001 6:03 AM
> Subject: [seamoby] Update to the requirements draft
> 
> 
> > Gary,
> >
> > From our discussions last week, I just want to clarify that, that
> > people had agreed to include two of the requirements that I had
> suggested,
> > also, some wording was changed to one of the existing requirements.
> Can you
> > please confirm that these are going to be updated?
> >
> > -Sharif.
> >
> > "The context transfer solution MUST be scalable".
> >
> > "The context transfer solution MUST include methods for interworking
> with
> > any IETF IP handover solutions".
> >
> > Also, the wording in section 5.1.2 was changed, I believe.
> >
> >
> >


From owner-seamoby@diameter.org  Mon Nov 26 06:14:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA18983
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 06:14:17 -0500 (EST)
Received: (qmail 9135 invoked by alias); 26 Nov 2001 12:00:27 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9129 invoked by uid 200); 26 Nov 2001 12:00:26 -0000
Received: (qmail 9124 invoked from network); 26 Nov 2001 12:00:24 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 26 Nov 2001 12:00:24 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18840;
	Mon, 26 Nov 2001 06:13:00 -0500 (EST)
Message-Id: <200111261113.GAA18840@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-ietf-seamoby-paging-protocol-assessment-00.txt
Date: Mon, 26 Nov 2001 06:13:00 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting Working Group of the IETF.

	Title		: Dormant Mode Host Alerting (DMHA) Protocol Assessment
	Author(s)	: J. Kempf et al.
	Filename	: draft-ietf-seamoby-paging-protocol-assessment-00.txt
	Pages		: 16
	Date		: 21-Nov-01
	
The Seamoby Working Group has been working toward specification of 
an IP-level protocol for Dormant Mode Host Alerting (DMHA), 
sometimes known as IP-paging or simply paging (the terms IP-DMHA, 
DMHA, IP Paging, and Paging will be used interchangeably in this 
document). A problem statement and requirements have been developed, 
and in response to a request for protocol submissions, five 
protocols were submitted.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-seamoby-paging-protocol-assessment-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-seamoby-paging-protocol-assessment-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-seamoby-paging-protocol-assessment-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011121140752.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-seamoby-paging-protocol-assessment-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-seamoby-paging-protocol-assessment-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011121140752.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Mon Nov 26 12:23:10 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14114
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 12:22:35 -0500 (EST)
Received: (qmail 11482 invoked by alias); 26 Nov 2001 17:58:23 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 11476 invoked by uid 200); 26 Nov 2001 17:58:23 -0000
Received: (qmail 11465 invoked from network); 26 Nov 2001 17:58:20 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 26 Nov 2001 17:58:20 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0955VB>; Mon, 26 Nov 2001 12:09:21 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9B9@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Pat R. Calhoun'" <pcalhoun@bstormnetworks.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: "'kempf@docomolabs-usa.com'" <kempf@docomolabs-usa.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>,
        "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Mon, 26 Nov 2001 12:09:17 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1769D.14D4FBD0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1769D.14D4FBD0
Content-Type: text/plain;
	charset="iso-8859-1"

No, MIP is not sufficient, in my oppinion. There are many other issues
involved when the MN changes its AP from one WLAN to another. 
 
-          Fast, seamless handover.
-          Authentication and authorization.
-          Billing (especially if the two WLANs are controlled by different
operators).
-          Context transfer
-          Mobility management.
-          Quality-of-Service.
 
Now, the IETF has different protocol for these, but how they fit together
into the interworking problem should be looked at.
 
Also important, is to understand how the L2 functions in the WLANs
interoperate with the functions in the IP layer. Perhaps, some functions are
better done in L2, while others in the IP layer .....
 
WLANs are going to be deployed more and more now, in campuses, enterprise
networks, and also in home networking. And how to interconnect them is of
great importance.
 
Thus, I believe, if there were sufficient interest from people, IETF should
consider taking an active role in attempting to understand ALL the issues
and decide what (if anything) to do.
 
Thus, a BOF session on "Interconnecting 802.11 in IP Layer"  is a small
step.
 
I am hoping to get a general feedback. Thanks.
 
 
-Sharif.
 
-----Original Message-----
From: Pat R. Calhoun [mailto:pcalhoun@bstormnetworks.com]
Sent: Monday, November 26, 2001 11:46 AM
To: 'Shahrier, Sharif M.'; 'Gary Kenward'
Cc: 'kempf@docomolabs-usa.com'
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Sensitivity: Confidential
 
  
-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 
Right so if MIP is sufficient, no BOF is required. 
  
PatC 
- -----Original Message----- 
From: Shahrier, Sharif M. [ mailto:Sharif.Shahrier@InterDigital.com
<mailto:Sharif.Shahrier@InterDigital.com> ] 
Sent: Monday, November 26, 2001 8:38 AM 
To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary Kenward' 
Cc: 'kempf@docomolabs-usa.com' 
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 
Sensitivity: Confidential 
 
Well, an  interworking solution need not necessarily be  a radio 
access network (RAN)  based solution. In fact, I have been 
researching into what companies are doing to interwork different 
types of networks, including 802.11. Most of them seem to be using 
Mobile IP (RFC2002), with some extensions of their own. 
As for IEEE, they just do L1 and L2, and nothing else. 
- -Sharif. 
The IESG would have zero interest on developing an air interface 
specific solution, and IEEE shouldn't get involved in L3 and above. 
  
See the problem :( 
  
PatC 
- - -----Original Message----- 
From: Shahrier, Sharif M. [ mailto:Sharif.Shahrier@InterDigital.com
<mailto:Sharif.Shahrier@InterDigital.com> ] 
Sent: Monday, November 26, 2001 8:19 AM 
To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary Kenward' 
Cc: 'kempf@docomolabs-usa.com' 
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 
Sensitivity: Confidential 
  
As far as I know, the MWIF are currently looking into interconnecting 
solutions for WLANs. Also, SA1 in 3GPP have a WI on interconnecting 
UMTS and WLANs, so it may be interconnecting 802.11's are a sub-set 
of that. What are the chances of requesting the IESG about forming an 
ad-hoc at the next IETF meeting, and getting a favorable response 
......? 
  
- - -Sharif. 
  
- - -----Original Message----- 
From: Pat R. Calhoun [ mailto:pcalhoun@bstormnetworks.com
<mailto:pcalhoun@bstormnetworks.com> ] 
Sent: Monday, November 26, 2001 11:07 AM 
To: 'Shahrier, Sharif M.'; 'Gary Kenward' 
Cc: 'kempf@docomolabs-usa.com' 
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 
Sensitivity: Confidential 
  
- - -----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 
yes, I have particular interest in this area, but I am also not sure 
that the standards body is the right place for this work. 
  
PatC 
- - - -----Original Message----- 
 - 

------_=_NextPart_001_01C1769D.14D4FBD0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C17673.F462B230">
<title>RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:293565682;
	mso-list-type:hybrid;
	mso-list-template-ids:1490601352 1445114762 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>N=
o, MIP is
not sufficient, in my oppinion. There are many other issues involved =
when the
MN changes its AP from one WLAN to another. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Fast, seamless =
handover.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Authentication and =
authorization.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Billing (especially if the two WLANs are =
controlled
by different operators).<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Context =
transfer<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Mobility =
management.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list .5in'><![if !supportLists]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:
"Times New Roman";mso-bidi-font-family:"Times New Roman"'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font></span><![endif]><span =
class=3DEmailStyle19><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'>Quality-of-Service.<o:p></o:p></span></font></=
span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>N=
ow, the
IETF has different protocol for these, but how they fit together into =
the
interworking problem should be looked =
at.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>A=
lso
important, is to understand how the L2 functions in the WLANs =
interoperate with
the functions in the IP layer. Perhaps, some functions are better done =
in L2,
while others in the IP layer =
&#8230;..<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>W=
LANs are
going to be deployed more and more now, in campuses, enterprise =
networks, and
also in home networking. And how to interconnect them is of great =
importance.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
hus, I believe,
if there were sufficient interest from people, IETF should consider =
taking an
active role in attempting to understand ALL the issues and decide what =
(if
anything) to do.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>T=
hus, a
BOF session on &#8220;Interconnecting 802.11 in IP Layer&#8221; <span =
style=3D"mso-spacerun:
yes">&nbsp;</span>is a small step.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>I=
 am
hoping to get a general feedback. =
Thanks.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>-=
Sharif.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Pat R. Calhoun
[mailto:pcalhoun@bstormnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, November =
26, 2001
11:46 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Shahrier, Sharif =
M.'; 'Gary
Kenward'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
'kempf@docomolabs-usa.com'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [seamoby]
draft-ietf-seamoby-ct-reqs-02.txt<br>
<b><span style=3D'font-weight:bold'>Sensitivity:</span></b> =
Confidential</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>-----BEGIN PGP SIGNED MESSAGE-----</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Hash: SHA1</span></font><font color=3Dblack><span =
style=3D'color:black'>
</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>Right so if MIP is sufficient, no BOF is =
required.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>PatC</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- -----Original Message-----</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>From: Shahrier, Sharif M. [<a
href=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</a>]
</span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Sent: Monday, November 26, 2001 8:38 AM</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary =
Kenward'</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Cc: 'kempf@docomolabs-usa.com'</span></font><font =
color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Subject: RE: [seamoby] =
draft-ietf-seamoby-ct-reqs-02.txt</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Sensitivity: Confidential</span></font><font =
color=3Dblack><span
style=3D'color:black'> </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>Well, an&nbsp; interworking solution need not necessarily =
be&nbsp;
a radio</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>access network (RAN)&nbsp; based solution. In fact, I have =
been</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>researching into what companies are doing to interwork =
different </span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>types of networks, including 802.11. Most of them seem to =
be using</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Mobile IP (RFC2002), with some extensions of their =
own.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>As for IEEE, they just do L1 and L2, and nothing =
else.</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- -Sharif.</span></font><font color=3Dblack><span =
style=3D'color:black'>
</span></font><font color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p><font size=3D2 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:black'>The IESG would have zero interest on developing an air =
interface </span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>specific solution, and IEEE shouldn't get involved in L3 =
and
above. </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>See the problem :( </span></font><font color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>PatC </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- - -----Original Message----- </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>From: Shahrier, Sharif M. [<a
href=3D"mailto:Sharif.Shahrier@InterDigital.com">mailto:Sharif.Shahrier@=
InterDigital.com</a>]
</span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Sent: Monday, November 26, 2001 8:19 AM =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary Kenward' =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Cc: 'kempf@docomolabs-usa.com' </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Sensitivity: Confidential </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp;</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>As far as I know, the MWIF are currently looking into
interconnecting</span></font><font color=3Dblack><span =
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>solutions for WLANs. Also, SA1 in 3GPP have a WI on
interconnecting </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>UMTS and WLANs, so it may be interconnecting 802.11's are =
a
sub-set </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>of that. What are the chances of requesting the IESG about =
forming
an</span></font><font color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>ad-hoc at the next IETF meeting, and getting a favorable =
response</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>......? </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- - -Sharif. </span></font><font color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- - -----Original Message----- </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>From: Pat R. Calhoun [<a =
href=3D"mailto:pcalhoun@bstormnetworks.com">mailto:pcalhoun@bstormnetwor=
ks.com</a>]
</span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Sent: Monday, November 26, 2001 11:07 AM =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>To: 'Shahrier, Sharif M.'; 'Gary Kenward' =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Cc: 'kempf@docomolabs-usa.com' </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0=
pt;
color:black'>Sensitivity: Confidential </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- - -----BEGIN PGP SIGNED MESSAGE----- </span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>Hash: SHA1 </span></font><font color=3Dblack><span =
style=3D'color:
black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>yes, I have particular interest in this area, but I am =
also not
sure </span></font><font color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>that the standards body is the right place for this work. =
</span></font><font
color=3Dblack><span style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>&nbsp; </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>PatC </span></font><font color=3Dblack><span =
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
color:black'>- - - -----Original Message----- </span></font><font =
color=3Dblack><span
style=3D'color:black'><br>
</span></font><font size=3D2 color=3Dnavy><span =
style=3D'font-size:10.0pt;color:navy'><span
style=3D"mso-spacerun: yes">&nbsp;</span></span></font><font size=3D2 =
color=3Dblack><span
style=3D'font-size:10.0pt;color:black'>-</span></font><font =
color=3Dblack><span
style=3D'color:black'> </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C1769D.14D4FBD0--


From owner-seamoby@diameter.org  Mon Nov 26 13:11:05 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17439
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 13:10:52 -0500 (EST)
Received: (qmail 13130 invoked by alias); 26 Nov 2001 18:56:39 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13124 invoked by uid 200); 26 Nov 2001 18:56:38 -0000
Received: (qmail 13119 invoked from network); 26 Nov 2001 18:56:37 -0000
Received: from fridge.docomo-usa.com (HELO docomolabs-usa.com) (216.98.102.228)
  by c900656-a.plstn1.sfba.home.com with SMTP; 26 Nov 2001 18:56:37 -0000
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fAQHvc527783;
	Mon, 26 Nov 2001 09:57:38 -0800 (PST)
Message-ID: <017501c176a3$9cd24fa0$0e02320a@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
        "'Pat R. Calhoun'" <pcalhoun@bstormnetworks.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>, <mobile-ip@sunroof.eng.sun.com>
References: <A1170612471BD21185B90008C7FA0A0D0327F9B9@idcpa4.pa.interdigital.com>
Subject: Re: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Mon, 26 Nov 2001 09:56:02 -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
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This sounds like architecture to me. IETF typically doesn't do that kind
of thing. I think IEEE should do this.

But you can try a BOF if you want...

        jak

----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Pat R. Calhoun'" <pcalhoun@bstormnetworks.com>; "Shahrier, Sharif
M." <Sharif.Shahrier@InterDigital.com>; "'Gary Kenward'"
<gkenward@nortelnetworks.com>
Cc: <kempf@docomolabs-usa.com>; <seamoby@cdma-2000.org>;
<mobile-ip@sunroof.eng.sun.com>
Sent: Monday, November 26, 2001 9:09 AM
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt


> No, MIP is not sufficient, in my oppinion. There are many other issues
> involved when the MN changes its AP from one WLAN to another.
>
> -          Fast, seamless handover.
> -          Authentication and authorization.
> -          Billing (especially if the two WLANs are controlled by
different
> operators).
> -          Context transfer
> -          Mobility management.
> -          Quality-of-Service.
>
> Now, the IETF has different protocol for these, but how they fit
together
> into the interworking problem should be looked at.
>
> Also important, is to understand how the L2 functions in the WLANs
> interoperate with the functions in the IP layer. Perhaps, some
functions are
> better done in L2, while others in the IP layer .....
>
> WLANs are going to be deployed more and more now, in campuses,
enterprise
> networks, and also in home networking. And how to interconnect them is
of
> great importance.
>
> Thus, I believe, if there were sufficient interest from people, IETF
should
> consider taking an active role in attempting to understand ALL the
issues
> and decide what (if anything) to do.
>
> Thus, a BOF session on "Interconnecting 802.11 in IP Layer"  is a
small
> step.
>
> I am hoping to get a general feedback. Thanks.
>
>
> -Sharif.
>
> -----Original Message-----
> From: Pat R. Calhoun [mailto:pcalhoun@bstormnetworks.com]
> Sent: Monday, November 26, 2001 11:46 AM
> To: 'Shahrier, Sharif M.'; 'Gary Kenward'
> Cc: 'kempf@docomolabs-usa.com'
> Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
> Sensitivity: Confidential
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Right so if MIP is sufficient, no BOF is required.
>
> PatC
> - -----Original Message-----
> From: Shahrier, Sharif M. [ mailto:Sharif.Shahrier@InterDigital.com
> <mailto:Sharif.Shahrier@InterDigital.com> ]
> Sent: Monday, November 26, 2001 8:38 AM
> To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: 'kempf@docomolabs-usa.com'
> Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
> Sensitivity: Confidential
>
> Well, an  interworking solution need not necessarily be  a radio
> access network (RAN)  based solution. In fact, I have been
> researching into what companies are doing to interwork different
> types of networks, including 802.11. Most of them seem to be using
> Mobile IP (RFC2002), with some extensions of their own.
> As for IEEE, they just do L1 and L2, and nothing else.
> - -Sharif.
> The IESG would have zero interest on developing an air interface
> specific solution, and IEEE shouldn't get involved in L3 and above.
>
> See the problem :(
>
> PatC
> - - -----Original Message-----
> From: Shahrier, Sharif M. [ mailto:Sharif.Shahrier@InterDigital.com
> <mailto:Sharif.Shahrier@InterDigital.com> ]
> Sent: Monday, November 26, 2001 8:19 AM
> To: Pat R. Calhoun; Shahrier, Sharif M.; 'Gary Kenward'
> Cc: 'kempf@docomolabs-usa.com'
> Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
> Sensitivity: Confidential
>
> As far as I know, the MWIF are currently looking into interconnecting
> solutions for WLANs. Also, SA1 in 3GPP have a WI on interconnecting
> UMTS and WLANs, so it may be interconnecting 802.11's are a sub-set
> of that. What are the chances of requesting the IESG about forming an
> ad-hoc at the next IETF meeting, and getting a favorable response
> ......?
>
> - - -Sharif.
>
> - - -----Original Message-----
> From: Pat R. Calhoun [ mailto:pcalhoun@bstormnetworks.com
> <mailto:pcalhoun@bstormnetworks.com> ]
> Sent: Monday, November 26, 2001 11:07 AM
> To: 'Shahrier, Sharif M.'; 'Gary Kenward'
> Cc: 'kempf@docomolabs-usa.com'
> Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
> Sensitivity: Confidential
>
> - - -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> yes, I have particular interest in this area, but I am also not sure
> that the standards body is the right place for this work.
>
> PatC
> - - - -----Original Message-----
>  -
>



From owner-seamoby@diameter.org  Mon Nov 26 13:46:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19997
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 13:46:06 -0500 (EST)
Received: (qmail 13794 invoked by alias); 26 Nov 2001 19:31:55 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13788 invoked by uid 200); 26 Nov 2001 19:31:55 -0000
Received: (qmail 13783 invoked from network); 26 Nov 2001 19:31:53 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 26 Nov 2001 19:31:53 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN095596>; Mon, 26 Nov 2001 13:43:03 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9BB@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] ICMP
Date: Mon, 26 Nov 2001 13:42:53 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C176AA.2830F6E0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C176AA.2830F6E0
Content-Type: text/plain;
	charset="iso-8859-1"

 Who is authorized to issue new values for TYPE and CODE in an ICMP message,
is it IANA?
Thanks.
 
-Sharif.

------_=_NextPart_001_01C176AA.2830F6E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C17681.07D84FC0">
<title>RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:293565682;
	mso-list-type:hybrid;
	mso-list-template-ids:1490601352 1445114762 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'><span style=3D"mso-spacerun:
yes">&nbsp;</span></span></font><font color=3D"#993366"><span =
style=3D'color:#993366'>Who
is authorized to issue new values for TYPE and CODE in an ICMP message, =
is it
IANA?</span></font></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Thanks.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle21><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C176AA.2830F6E0--


From owner-seamoby@diameter.org  Mon Nov 26 14:54:35 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA25215
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 14:54:34 -0500 (EST)
Received: (qmail 15237 invoked by alias); 26 Nov 2001 20:41:15 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 15231 invoked by uid 200); 26 Nov 2001 20:41:14 -0000
Received: (qmail 15226 invoked by uid 500); 26 Nov 2001 20:41:13 -0000
Date: Mon, 26 Nov 2001 12:41:13 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: seamoby@cdma-2000.org
Subject: [seamoby] Proposed Seamoby Agenda
Message-ID: <20011126124113.E15160@charizard.diameter.org>
Mail-Followup-To: seamoby@cdma-2000.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

Below is the proposed Seamoby Agenda. Both Jim and I are looking for feedback.

Thanks,

PatC
----

1.  Charter/Milestone Review (Chairs) - 10 mins
2.  Paging Assessment Update (Kempf) - 35 mins
3.  Paging Protocol Next Steps (Chairs) - 10 mins
4.  Context Transfer Problem Statement Update (Kempf) - 5 mins 
5.  Context Transfer Requirements Update (Kenward) - 30 mins 
6.  Context Transfer Next Steps (Chairs) - 10 mins 
7.  Candidate Access Router Discovery Problem Statement Update (Govind) - 15 mins
8.  Candidate Access Router Discovery Next Steps (Chairs) - 10 mins 
9.  Summary (Chairs) - 10 mins 
10. Adjourn



From owner-seamoby@diameter.org  Mon Nov 26 17:57:30 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA09326
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:57:30 -0500 (EST)
Received: (qmail 18366 invoked by alias); 26 Nov 2001 23:41:09 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 18360 invoked by uid 200); 26 Nov 2001 23:41:09 -0000
Received: (qmail 18355 invoked from network); 26 Nov 2001 23:41:08 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 26 Nov 2001 23:41:08 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0956XF>; Mon, 26 Nov 2001 17:52:18 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9BE@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Mon, 26 Nov 2001 17:52:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Could anyone please advise me where I can get the document that lists all
the standardized (so far) values for TYPE and CODE in the ICMP message?

-Sharif.


From owner-seamoby@diameter.org  Mon Nov 26 20:01:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17211
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Nov 2001 20:01:26 -0500 (EST)
Received: (qmail 21394 invoked by alias); 27 Nov 2001 01:47:34 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 21388 invoked by uid 200); 27 Nov 2001 01:47:34 -0000
Received: (qmail 21383 invoked from network); 27 Nov 2001 01:47:32 -0000
Received: from minotaur.nge.isi.edu (65.114.169.202)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 01:47:32 -0000
Received: from minotaur (mankin@localhost)
	by minotaur.nge.isi.edu (8.11.6/8.11.6) with ESMTP id fAR10GT12045;
	Mon, 26 Nov 2001 20:00:18 -0500
Message-Id: <200111270100.fAR10GT12045@minotaur.nge.isi.edu>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
cc: seamoby@cdma-2000.org
Reply-To: mankin@isi.edu
Subject: Re: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 
In-reply-to: Your message of Mon, 26 Nov 2001 17:52:07 -0500.
             <A1170612471BD21185B90008C7FA0A0D0327F9BE@idcpa4.pa.interdigital.com> 
Mime-Version: 1.0 (generated by tm-edit 1.7)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 26 Nov 2001 20:00:16 -0500
From: Allison Mankin <mankin@isi.edu>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> Could anyone please advise me where I can get the document that lists all 
> the standardized (so far) values for TYPE and CODE in the ICMP message? 

The definitive list is the IANA registry:
 
   http://www.iana.org/assignments/icmp-parameters

See also RFC 2780 (BCP 37) about how new ones get approved.



From owner-seamoby@diameter.org  Tue Nov 27 01:40:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02636
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 01:40:07 -0500 (EST)
Received: (qmail 24773 invoked by alias); 27 Nov 2001 07:26:07 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 24767 invoked by uid 200); 27 Nov 2001 07:26:07 -0000
Received: (qmail 24762 invoked from network); 27 Nov 2001 07:26:05 -0000
Received: from mail11.speakeasy.net (216.254.0.211)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 07:26:05 -0000
Received: (qmail 29106 invoked from network); 27 Nov 2001 06:39:19 -0000
Received: from unknown (HELO dsl092-015-190.sfo1.dsl.speakeasy.net) ([66.92.15.190]) (envelope-sender <jonwood@speakeasy.net>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <seamoby@cdma-2000.org>; 27 Nov 2001 06:39:19 -0000
Date: Mon, 26 Nov 2001 22:38:52 -0800
Subject: [seamoby] Re: I-D ACTION:draft-funato-seamoby-gaard-00.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v475)
From: Jonathan Wood <jonwood@speakeasy.net>
To: seamoby@cdma-2000.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <200111270544.VAA17692@heliopolis.eng.sun.com>
Message-Id: <6C581E8A-E301-11D5-8E8C-0003930D291E@speakeasy.net>
X-Mailer: Apple Mail (2.475)
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


As mentioned in the draft, the use of SLP is similar to its use
in IEEE IAPP. However, the two standards have different service
types (and may end up with different service definitions when
GAARD's service template is written). IAPP has
service:dot11-iapp, while GAARD has service:gaard.

Since the two services are so similar, you might want to=12sync up
the two proposals and create a common service definition.
If you find that a single type can't cover the peculiarities of
differnet links and their capabilities, you could create a common
abstract type (with just one attribute, the L2 identifier), and
then create concrete types for each different link, as needed. See
rfc2609 (Service Templates and Service: Schemes) for more
information on how to do this.

Jonathan


> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>
>
> 	Title		: Geographically Adjacent Access Router Discovery
>                           Protocol
> 	Author(s)	: D. Funato et al.
> 	Filename	: draft-funato-seamoby-gaard-00.txt
> 	Pages		: 20
> 	Date		: 21-Nov-01
> 	
> This document describes a scheme (GAARD) that discovers geographically
> adjacent access routers (GAARs). This is accomplished through a
> distributed process whereby all mobile hosts associated with the
> current access router identify geographically adjacent access routers
> by their corresponding Link-Layer beacons sent by geographically
> adjacent access points.
>



From owner-seamoby@diameter.org  Tue Nov 27 02:23:21 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15039
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 02:23:20 -0500 (EST)
Received: (qmail 25352 invoked by alias); 27 Nov 2001 08:09:53 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 25346 invoked by uid 200); 27 Nov 2001 08:09:53 -0000
Received: (qmail 25338 invoked from network); 27 Nov 2001 08:09:46 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 08:09:46 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAR7NGA21051
	for <seamoby@cdma-2000.org>; Tue, 27 Nov 2001 09:23:16 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T577984f774ac158f2313c@esvir03nok.nokia.com>;
 Tue, 27 Nov 2001 09:21:51 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <XP21Y6X2>; Tue, 27 Nov 2001 09:21:52 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D91A3@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: Sharif.Shahrier@InterDigital.com
Cc: seamoby@cdma-2000.org, mobile-ip@sunroof.eng.sun.com
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Tue, 27 Nov 2001 09:21:42 +0200
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hello all,

Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS
for seamless inter-operator, vertical handovers?  :)

Given the fact that many of the applicable protocols for such
a solution are not RFCs yet, I would like to suggest that such 
a solution is very interesting (for sure), but I think the
IETF would have a hard time standardizing such a beast.

Rather, I think getting about 10 smart engineers in a room
together for a couple of months could get a pretty impressive
demo together.

John


From owner-seamoby@diameter.org  Tue Nov 27 03:12:02 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA15777
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 03:12:01 -0500 (EST)
Received: (qmail 25993 invoked by alias); 27 Nov 2001 08:58:19 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 25987 invoked by uid 200); 27 Nov 2001 08:58:18 -0000
Received: (qmail 25982 invoked from network); 27 Nov 2001 08:58:17 -0000
Received: from bells.cs.ucl.ac.uk (128.16.5.31)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 08:58:17 -0000
Received: from bohemian.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.02997-0@bells.cs.ucl.ac.uk>; Tue, 27 Nov 2001 08:10:35 +0000
Message-ID: <3C034A7B.5F0C9B18@cs.ucl.ac.uk>
Date: Tue, 27 Nov 2001 08:10:35 +0000
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: t.pagtzis@cs.ucl.ac.uk
Organization: UCL/Mobile Systems Group
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: xiaoning <xiaoning@docomolabs-usa.com>
CC: "'IETF-Seamoby Working Group'" <seamoby@diameter.org>,
        "'Atsushi Takeshita'" <takeshita@docomolabs-usa.com>,
        "'Carl Williams'" <carlw@docomolabs-usa.com>,
        "'Daichi Funato'" <funato@docomolabs-usa.com>
Subject: Re: [seamoby] GAARD Draft
References: <000001c17558$065a2f30$356015ac@VAIOHE>
Content-Type: text/plain; charset=iso-8859-7
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Xiaoning,

  If you look at the approach that I follow for the RNV aquisition with
temporal reactive learning you will see that the approach is almost
identical. It is just that the names of your terms that change. I am
talking about a coverage area tuple, you describe it as an cached id.


Theo
UCL/Mobile Systems

Xiaoning He wrote:
> 
> Hi Theo
> 
> We really appreciate your comments on our draft. Since the draft is
> still at its .00 statuses, we didn't intent to neglect your work.
> Probably we just missed it.
> 
> My initial impression with your draft is that your draft is a
> comprehensive framework which proposed a new scheme for mobility. So, it
> will be very helpful if you can further let us know which part of your
> draft contains the similar contents as ours.
> 
> Thank you
> 
> Xiaoning He
> 
> -----Original Message-----
> From: owner-seamoby@diameter.org [mailto:owner-seamoby@diameter.org] On
> Behalf Of Theo Pagtzis
> Sent: Wednesday, November 21, 2001 4:02 PM
> To: xiaoning
> Cc: IETF-Seamoby Working Group; Atsushi Takeshita; Carl Williams; Daichi
> Funato
> Subject: Re: [seamoby] GAARD Draft
> 
> Hello Xiaoning,
> 
>   While I appreciate your work, I am surpized not to see my work
> referred anywhere in your proposal (like others), since I have already
> proposed something like that back in July where the core element
> revolves about the distinction between the mobility and routing
> neighbourhood.
> 
> Please see
> 
> http://search.ietf.org/internet-drafts/draft-pagtzis-seamoby-proactivev6
> -00.txt
> 
> Regards
> 
> Theo
> UCL/Mobile Systems Group
> 
> Xiaoning He wrote:
> >
> > Hello all
> >
> > We have submitted a draft for the SEAMOBY working group. I am not sure
> > when an announcement will be sent to this alias. You can access the
> > draft at following address
> >
> >
> http://www.inogroup.com/apps/docomo/publications/docs/draft-funato-seamo
> > by-gaard-00.txt
> >
> > FYI....
> >
> > Xiaoning He


From owner-seamoby@diameter.org  Tue Nov 27 08:23:04 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA25538
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 08:23:03 -0500 (EST)
Received: (qmail 28525 invoked by alias); 27 Nov 2001 14:09:01 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 28519 invoked by uid 200); 27 Nov 2001 14:09:01 -0000
Received: (qmail 28514 invoked from network); 27 Nov 2001 14:08:59 -0000
Received: from softdnserror (HELO meshpdc.meshnetworks.com) (205.245.27.196)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 14:08:59 -0000
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)
	id <XQXCXL7G>; Tue, 27 Nov 2001 08:21:41 -0500
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E048616638@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@MeshNetworks.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>
Cc: seamoby@cdma-2000.org
Subject: Who wants seamless handovers anyway?  was RE: [seamoby] draft-iet
	f-seamoby-ct-reqs-02.txt
Date: Tue, 27 Nov 2001 08:21:32 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi,

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> 
> Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS
> for seamless inter-operator, vertical handovers?  :)

Hopefully not.  There is a small but growing movement to make better use
use of the unlicensed bands (with high bits/Hz/sq meter) MAC protocols.
The ISP model is more appropriate, i.e. you pay for access but that's
it.  The IP pipe to the big I is the "service", i.e. no Telco/cell-like
operator needed.

Question: Who want's seamless handovers anyway?  
Question: Between what AND what?

I understand the term "vertical handover" to mean inter-technology hand-
over (especially from a subsumed pico-cell in(out)to a larger container
cell).  Multi-mode 11a/11b radios will be coming out soon with multiple
MACs, but these are likely to be limited to hot spot and hot region
communication in the near term.

802.11b and Bluetooth have lots of problems and don't provide good 
mobility.  The problems have been identified for the most part, but the 
fixes will take time to get into these MACs (if it is deemed worthwhile).
Multi-hopping with these MACs is  problematic and putting QoS on them is
currently near impossible due to inherent unfairness issues.  It is
really time to revisit MAC land with some improvements for seamless
mobility and as Barani mentioned there is work in the IEEE on handoff
stuff.  However, there is also work needed on the MACs (or to create
a new one) better suited for mobility and ad hoc networking. 

Handing off between cellular systems and WLANs/WPANs (at least with
today's MACs) is not all that useful and will not scale that well.  I 
know I sound like a curmudgeon, but I have looked pretty closely at
this possibility.  If you believe otherwise, can you explain why this
is useful and more importantly where (and how it could be profitable?)

> Given the fact that many of the applicable protocols for such
> a solution are not RFCs yet, I would like to suggest that such 
> a solution is very interesting (for sure), but I think the
> IETF would have a hard time standardizing such a beast.

Yes, we probably need some scrappy start ups to revolutionize free
wireless Internet for the masses not dissimilar from what Linux
has done with OS's.  Even in the U.S. this would be fought tooth and
nail and would likely lead to massive disruption in the operator's 
home turf.  The war has already been waged, its just that wireless is
a new battlefield between the "bellheads" and the Internet "freedom
fighters".  :-)

> Rather, I think getting about 10 smart engineers in a room
> together for a couple of months could get a pretty impressive
> demo together.

Its been done.  Its been shown and demoed.  Now what do we do?

73s,

Phil 
****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures. 


From owner-seamoby@diameter.org  Tue Nov 27 08:27:37 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA25795
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 08:27:37 -0500 (EST)
Received: (qmail 29056 invoked by alias); 27 Nov 2001 14:13:58 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29050 invoked by uid 200); 27 Nov 2001 14:13:58 -0000
Received: (qmail 29045 invoked from network); 27 Nov 2001 14:13:56 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 14:13:56 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fARDRMA17293
	for <seamoby@cdma-2000.org>; Tue, 27 Nov 2001 15:27:22 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T577ad2edbeac158f23134@esvir03nok.nokia.com>;
 Tue, 27 Nov 2001 15:26:38 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <XP21ZS8S>; Tue, 27 Nov 2001 15:26:36 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D91C0@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: PNeumiller@MeshNetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: Who wants seamless handovers anyway?  was RE: [seamoby] draft
	-iet f-seamoby-ct-reqs-02.txt
Date: Tue, 27 Nov 2001 15:26:30 +0200
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Phil,

> Sensitivity: Confidential

Any reason I need to treat this as confidentional?

> > Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS
> > for seamless inter-operator, vertical handovers?  :)
> 
> Hopefully not.  There is a small but growing movement to make 
> better use use of the unlicensed bands (with high bits/Hz/sq meter) 
> MAC protocols. The ISP model is more appropriate, i.e. you pay for 
> access but that's it.  The IP pipe to the big I is the "service", i.e. 
> no Telco/cell-like operator needed.

I think we've been down this road before :)  Anyhow, I think that 
telcos will soon need to move to your model.  Remember, at the begining
of the 90's ISPs used a similar metered approach to charging.

> Question: Who want's seamless handovers anyway?  
> Question: Between what AND what?

I think the folks that will want seamless handovers will be 
the service providers who want to provide a service.  Users
will usually take what they can get.  

> > Rather, I think getting about 10 smart engineers in a room
> > together for a couple of months could get a pretty impressive
> > demo together.
 
> Its been done.  Its been shown and demoed.  Now what do we do?

Take what we've learned and see if it is useful.  Standardize
the pieces that are useful and patent the rest!

John


From owner-seamoby@diameter.org  Tue Nov 27 09:52:02 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01057
	for <seamoby-archive@lists.ietf.org>; Tue, 27 Nov 2001 09:51:50 -0500 (EST)
Received: (qmail 29795 invoked by alias); 27 Nov 2001 15:34:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 29789 invoked by uid 200); 27 Nov 2001 15:34:10 -0000
Received: (qmail 29784 invoked from network); 27 Nov 2001 15:34:08 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 15:34:08 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN0958A3>; Tue, 27 Nov 2001 09:45:19 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9C0@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Carl Williams'" <carlw@docomolabs-usa.com>,
        mobile-ip@sunroof.eng.sun.com,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [mobile-ip] RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Tue, 27 Nov 2001 09:45:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17752.2231FED0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17752.2231FED0
Content-Type: text/plain;
	charset="iso-8859-1"

I was informed by the chair that we need an AD to sponsor such a BOF,
however I don't know if any AD is interested.
Perhaps if an AD is interested, he can get in touch.
 
-Sharif.
 
No, MIP is not sufficient, in my oppinion. There are many other issues
involved when the MN changes its AP from one WLAN to another. 
 
-          Fast, seamless handover.
-          Authentication and authorization.
-          Billing (especially if the two WLANs are controlled by different
operators).
-          Context transfer
-          Mobility management.
-          Quality-of-Service.
 
Now, the IETF has different protocol for these, but how they fit together
into the interworking problem should be looked at.
 
Also important, is to understand how the L2 functions in the WLANs
interoperate with the functions in the IP layer. Perhaps, some functions are
better done in L2, while others in the IP layer .....
 
WLANs are going to be deployed more and more now, in campuses, enterprise
networks, and also in home networking. And how to interconnect them is of
great importance.
 
Thus, I believe, if there were sufficient interest from people, IETF should
consider taking an active role in attempting to understand ALL the issues
and decide what (if anything) to do.
 
Thus, a BOF session on "Interconnecting 802.11 in IP Layer"  is a small
step.
 
Shahrier,
 
Is there plans for such a BOF?
 
Carl
 
 

------_=_NextPart_001_01C17752.2231FED0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C17729.01714710">
<title>RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
p.section1, li.section1, div.section1
	{mso-style-name:section1;
	margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#993366;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I was informed by the chair that we need an AD to sponsor such a =
BOF,
however I don&#8217;t know if any AD is =
interested.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Perhaps if an AD is interested, he can get in touch.<o:p></o:p></=
span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>-Sharif.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle22><font size=3D2 =
color=3D"#993366"
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<div style=3D'border:none;border-left:solid black 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>No, MIP is not =
sufficient,
in my oppinion. There are many other issues involved when the MN =
changes its AP
from one WLAN to another. <o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


</div>

<div style=3D'border:none;border-left:solid black 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Fast, seamless handover.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Authentication and =
authorization.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Billing (especially if the two WLANs are controlled by different
operators).<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Context transfer<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Mobility management.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:39.75pt;text-indent:-.25in;tab-stops:
list .5in;border:none;mso-border-left-alt:solid black =
1.5pt;padding:0in;
mso-padding-alt:0in 0in 0in 4.0pt'><span class=3DEmailStyle20><font =
size=3D2
color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman"'>-</span></font></span><span
class=3DEmailStyle20><font size=3D1 color=3Dnavy><span =
style=3D'font-size:7.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span><span class=3DEmailStyle20><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Quality-of-Service.<o:p></o:p></span></font></span></p>

</div>

<div style=3D'border:none;border-left:solid black 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>Now, the IETF has =
different
protocol for these, but how they fit together into the interworking =
problem
should be looked at.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>Also important, is =
to
understand how the L2 functions in the WLANs interoperate with the =
functions in
the IP layer. Perhaps, some functions are better done in L2, while =
others in
the IP layer &#8230;..<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>WLANs are going to =
be
deployed more and more now, in campuses, enterprise networks, and also =
in home
networking. And how to interconnect them is of great =
importance.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>Thus, I believe, if =
there
were sufficient interest from people, IETF should consider taking an =
active
role in attempting to understand ALL the issues and decide what (if =
anything)
to do.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><span
class=3DEmailStyle20><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>Thus, a BOF session =
on &#8220;Interconnecting
802.11 in IP Layer&#8221;<span style=3D"mso-spacerun: yes">&nbsp; =
</span>is a small
step.</span></font></span><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:3.75pt;border:none;mso-border-left-alt:
solid black 1.5pt;padding:0in;mso-padding-alt:0in 0in 0in 4.0pt'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font
color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p>=
</o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Shahrier,</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Is there plans for such a =
BOF?</span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Carl</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'>&nbsp;</span></font><font =
color=3Dblack><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:black'><span style=3D"mso-spacerun:
yes">&nbsp;</span></span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C17752.2231FED0--


From owner-seamoby@diameter.org  Tue Nov 27 11:00:31 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05628
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Nov 2001 11:00:17 -0500 (EST)
Received: (qmail 30460 invoked by alias); 27 Nov 2001 16:44:12 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 30454 invoked by uid 200); 27 Nov 2001 16:44:12 -0000
Received: (qmail 30449 invoked from network); 27 Nov 2001 16:44:10 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 27 Nov 2001 16:44:10 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fARFtnd15160
	for <seamoby@cdma-2000.org>; Tue, 27 Nov 2001 10:55:50 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Tue, 27 Nov 2001 10:56:13 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <XRDZL8BG>; Tue, 27 Nov 2001 10:55:07 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C01AA46AD@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        PNeumiller@MeshNetworks.com
Cc: seamoby@cdma-2000.org
Subject: RE: Who wants seamless handovers anyway? was RE: [seamoby] draft -iet 
         f-seamoby-ct-reqs-02.txt
Date: Tue, 27 Nov 2001 10:55:06 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C1775B.E25D7730"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1775B.E25D7730
Content-Type: text/plain;
	charset="ISO-8859-1"


The issue is not simply the charging model.
France Bouygues has announced a FF95 wireless Internet access
service that they hope will displace wireline Internet access
in France. 

It is based upon GPRS, and will work well with short messaging.
But there is much missing.

As for inter-network, inter-technology roaming: the one reason the
big operators (not all are telcos btw), are the major players in
wireless is that by the time an organization roles out a nationwide 
network, it has to end up looking like a "big operator", and it is
desperate for revenue to pay the bills.

The reason that why very wide area networks are required is that 
wireless = mobility. No on has sold a wireless service simply on
the value of displacing wires. If you need evidence, look at the
history of fixed wireless access; look at Metricom.

Networks that support mobility in small areas inevitably limit the
user population. Only those who derive great value in using a
service in a restricted geographical area will pay for the service.

So the real issue, if Phil's "internet rebellion" is to take place,
is how to connect a bunch of smaller wireless networks together - which,
if implies seamless inter-network handover. And, if you want to free
up the operators to use competitive technology (and free up the user
to use the most cost effective service), then inter-technology handover
would be very useful.

There are other, engineering reasons, for inter-network/inter-technology
handover: there is no one wireless technology that does it all. Satellites
provide excellent rural and open-water coverage, but are not very good for
urban cores or indoors. Terrestrial towers give wide area coverage for
the suburbs, and other low density areas, but are generally too expensive
and too cumbersome for urban coverage, and do not provide good indoor 
coverage. 

Wireless LANS - well, great for indoor, high density campus outdoor
coverage.
But the limited range means many base stations are required. Take the
coverage area of 802.11 and calculate the number of base stations required
to cover Manhattan and you will see the point. Just finding the real estate
is an ominous problem (one of the problems that killed telepoint in the US
was the churn on base station real estate; one estimate I heard was 15% per
month). And if real estate can be found, what about all the backhaul that
would be required to connect these base stations together?

I am not a Ludite, but there are real problems to be solved, and as yet,
no one has come up with the magic wireless networking solution. Every
technology has it's strengths and weaknesses, and to me, the solution has
always been the need to stitch these solutions together, seamlessly 
(and how's that for stretching a metaphor).

Gary


> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: November 27, 2001 08:27
> To: PNeumiller@MeshNetworks.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: Who wants seamless handovers anyway? was RE: [seamoby]
> draft -iet f-seamoby-ct-reqs-02.txt
> Sensitivity: Confidential
> 
> 
> Hi Phil,
> 
> > Sensitivity: Confidential
> 
> Any reason I need to treat this as confidentional?
> 
> > > Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS
> > > for seamless inter-operator, vertical handovers?  :)
> > 
> > Hopefully not.  There is a small but growing movement to make 
> > better use use of the unlicensed bands (with high bits/Hz/sq meter) 
> > MAC protocols. The ISP model is more appropriate, i.e. you pay for 
> > access but that's it.  The IP pipe to the big I is the 
> "service", i.e. 
> > no Telco/cell-like operator needed.
> 
> I think we've been down this road before :)  Anyhow, I think that 
> telcos will soon need to move to your model.  Remember, at 
> the begining
> of the 90's ISPs used a similar metered approach to charging.
> 
> > Question: Who want's seamless handovers anyway?  
> > Question: Between what AND what?
> 
> I think the folks that will want seamless handovers will be 
> the service providers who want to provide a service.  Users
> will usually take what they can get.  
> 
> > > Rather, I think getting about 10 smart engineers in a room
> > > together for a couple of months could get a pretty impressive
> > > demo together.
>  
> > Its been done.  Its been shown and demoed.  Now what do we do?
> 
> Take what we've learned and see if it is useful.  Standardize
> the pieces that are useful and patent the rest!
> 
> John
> 

------_=_NextPart_001_01C1775B.E25D7730
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: Who wants seamless handovers anyway? was RE: [seamoby] draft -iet  f-seamoby-ct-reqs-02.txt</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>The issue is not simply the charging model.</FONT>
<BR><FONT SIZE=2>France Bouygues has announced a FF95 wireless Internet access</FONT>
<BR><FONT SIZE=2>service that they hope will displace wireline Internet access</FONT>
<BR><FONT SIZE=2>in France. </FONT>
</P>

<P><FONT SIZE=2>It is based upon GPRS, and will work well with short messaging.</FONT>
<BR><FONT SIZE=2>But there is much missing.</FONT>
</P>

<P><FONT SIZE=2>As for inter-network, inter-technology roaming: the one reason the</FONT>
<BR><FONT SIZE=2>big operators (not all are telcos btw), are the major players in</FONT>
<BR><FONT SIZE=2>wireless is that by the time an organization roles out a nationwide </FONT>
<BR><FONT SIZE=2>network, it has to end up looking like a &quot;big operator&quot;, and it is</FONT>
<BR><FONT SIZE=2>desperate for revenue to pay the bills.</FONT>
</P>

<P><FONT SIZE=2>The reason that why very wide area networks are required is that </FONT>
<BR><FONT SIZE=2>wireless = mobility. No on has sold a wireless service simply on</FONT>
<BR><FONT SIZE=2>the value of displacing wires. If you need evidence, look at the</FONT>
<BR><FONT SIZE=2>history of fixed wireless access; look at Metricom.</FONT>
</P>

<P><FONT SIZE=2>Networks that support mobility in small areas inevitably limit the</FONT>
<BR><FONT SIZE=2>user population. Only those who derive great value in using a</FONT>
<BR><FONT SIZE=2>service in a restricted geographical area will pay for the service.</FONT>
</P>

<P><FONT SIZE=2>So the real issue, if Phil's &quot;internet rebellion&quot; is to take place,</FONT>
<BR><FONT SIZE=2>is how to connect a bunch of smaller wireless networks together - which,</FONT>
<BR><FONT SIZE=2>if implies seamless inter-network handover. And, if you want to free</FONT>
<BR><FONT SIZE=2>up the operators to use competitive technology (and free up the user</FONT>
<BR><FONT SIZE=2>to use the most cost effective service), then inter-technology handover</FONT>
<BR><FONT SIZE=2>would be very useful.</FONT>
</P>

<P><FONT SIZE=2>There are other, engineering reasons, for inter-network/inter-technology</FONT>
<BR><FONT SIZE=2>handover: there is no one wireless technology that does it all. Satellites</FONT>
<BR><FONT SIZE=2>provide excellent rural and open-water coverage, but are not very good for</FONT>
<BR><FONT SIZE=2>urban cores or indoors. Terrestrial towers give wide area coverage for</FONT>
<BR><FONT SIZE=2>the suburbs, and other low density areas, but are generally too expensive</FONT>
<BR><FONT SIZE=2>and too cumbersome for urban coverage, and do not provide good indoor </FONT>
<BR><FONT SIZE=2>coverage. </FONT>
</P>

<P><FONT SIZE=2>Wireless LANS - well, great for indoor, high density campus outdoor coverage.</FONT>
<BR><FONT SIZE=2>But the limited range means many base stations are required. Take the</FONT>
<BR><FONT SIZE=2>coverage area of 802.11 and calculate the number of base stations required</FONT>
<BR><FONT SIZE=2>to cover Manhattan and you will see the point. Just finding the real estate</FONT>
<BR><FONT SIZE=2>is an ominous problem (one of the problems that killed telepoint in the US</FONT>
<BR><FONT SIZE=2>was the churn on base station real estate; one estimate I heard was 15% per</FONT>
<BR><FONT SIZE=2>month). And if real estate can be found, what about all the backhaul that</FONT>
<BR><FONT SIZE=2>would be required to connect these base stations together?</FONT>
</P>

<P><FONT SIZE=2>I am not a Ludite, but there are real problems to be solved, and as yet,</FONT>
<BR><FONT SIZE=2>no one has come up with the magic wireless networking solution. Every</FONT>
<BR><FONT SIZE=2>technology has it's strengths and weaknesses, and to me, the solution has</FONT>
<BR><FONT SIZE=2>always been the need to stitch these solutions together, seamlessly </FONT>
<BR><FONT SIZE=2>(and how's that for stretching a metaphor).</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: john.loughney@nokia.com [<A HREF="mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: November 27, 2001 08:27</FONT>
<BR><FONT SIZE=2>&gt; To: PNeumiller@MeshNetworks.com</FONT>
<BR><FONT SIZE=2>&gt; Cc: seamoby@cdma-2000.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: Who wants seamless handovers anyway? was RE: [seamoby]</FONT>
<BR><FONT SIZE=2>&gt; draft -iet f-seamoby-ct-reqs-02.txt</FONT>
<BR><FONT SIZE=2>&gt; Sensitivity: Confidential</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hi Phil,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Sensitivity: Confidential</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Any reason I need to treat this as confidentional?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; for seamless inter-operator, vertical handovers?&nbsp; :)</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Hopefully not.&nbsp; There is a small but growing movement to make </FONT>
<BR><FONT SIZE=2>&gt; &gt; better use use of the unlicensed bands (with high bits/Hz/sq meter) </FONT>
<BR><FONT SIZE=2>&gt; &gt; MAC protocols. The ISP model is more appropriate, i.e. you pay for </FONT>
<BR><FONT SIZE=2>&gt; &gt; access but that's it.&nbsp; The IP pipe to the big I is the </FONT>
<BR><FONT SIZE=2>&gt; &quot;service&quot;, i.e. </FONT>
<BR><FONT SIZE=2>&gt; &gt; no Telco/cell-like operator needed.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I think we've been down this road before :)&nbsp; Anyhow, I think that </FONT>
<BR><FONT SIZE=2>&gt; telcos will soon need to move to your model.&nbsp; Remember, at </FONT>
<BR><FONT SIZE=2>&gt; the begining</FONT>
<BR><FONT SIZE=2>&gt; of the 90's ISPs used a similar metered approach to charging.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Question: Who want's seamless handovers anyway?&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Question: Between what AND what?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I think the folks that will want seamless handovers will be </FONT>
<BR><FONT SIZE=2>&gt; the service providers who want to provide a service.&nbsp; Users</FONT>
<BR><FONT SIZE=2>&gt; will usually take what they can get.&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Rather, I think getting about 10 smart engineers in a room</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; together for a couple of months could get a pretty impressive</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; demo together.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Its been done.&nbsp; Its been shown and demoed.&nbsp; Now what do we do?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Take what we've learned and see if it is useful.&nbsp; Standardize</FONT>
<BR><FONT SIZE=2>&gt; the pieces that are useful and patent the rest!</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; John</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1775B.E25D7730--


From owner-seamoby@diameter.org  Tue Nov 27 11:39:38 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08411
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Nov 2001 11:39:37 -0500 (EST)
Received: (qmail 31081 invoked by alias); 27 Nov 2001 17:25:58 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 31075 invoked by uid 200); 27 Nov 2001 17:25:58 -0000
Received: (qmail 31067 invoked by uid 500); 27 Nov 2001 17:25:56 -0000
Date: Tue, 27 Nov 2001 09:25:55 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: john.loughney@nokia.com
Cc: Sharif.Shahrier@InterDigital.com, seamoby@cdma-2000.org,
        mobile-ip@sunroof.eng.sun.com
Subject: Re: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Message-ID: <20011127092555.A31055@charizard.diameter.org>
Mail-Followup-To: john.loughney@nokia.com, Sharif.Shahrier@InterDigital.com,
	seamoby@cdma-2000.org, mobile-ip@sunroof.eng.sun.com
References: <0C1353ABB1DEB74DB067ADFF749C4EEF5D91A3@esebe004.NOE.Nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <0C1353ABB1DEB74DB067ADFF749C4EEF5D91A3@esebe004.NOE.Nokia.com>; from john.loughney@nokia.com on Tue, Nov 27, 2001 at 09:21:42AM +0200
Sender: owner-seamoby@diameter.org
Precedence: bulk

Agreed.... but who would fund this activity :(

PatC
On Tue, Nov 27, 2001 at 09:21:42AM +0200, john.loughney@nokia.com wrote:
> Hello all,
> 
> Doesn't this all boil down to the applicability AAA, CT, MIP, NSIS
> for seamless inter-operator, vertical handovers?  :)
> 
> Given the fact that many of the applicable protocols for such
> a solution are not RFCs yet, I would like to suggest that such 
> a solution is very interesting (for sure), but I think the
> IETF would have a hard time standardizing such a beast.
> 
> Rather, I think getting about 10 smart engineers in a room
> together for a couple of months could get a pretty impressive
> demo together.
> 
> John


From owner-seamoby@diameter.org  Tue Nov 27 11:45:58 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08858
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Nov 2001 11:45:57 -0500 (EST)
Received: (qmail 31678 invoked by alias); 27 Nov 2001 17:32:21 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 31672 invoked by uid 200); 27 Nov 2001 17:32:21 -0000
Received: (qmail 31664 invoked by uid 500); 27 Nov 2001 17:32:20 -0000
Date: Tue, 27 Nov 2001 09:32:19 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: "'Carl Williams'" <carlw@docomolabs-usa.com>,
        mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org
Subject: Re: [mobile-ip] RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Message-ID: <20011127093219.E31055@charizard.diameter.org>
Mail-Followup-To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>,
	'Carl Williams' <carlw@docomolabs-usa.com>,
	mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org
References: <A1170612471BD21185B90008C7FA0A0D0327F9C0@idcpa4.pa.interdigital.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <A1170612471BD21185B90008C7FA0A0D0327F9C0@idcpa4.pa.interdigital.com>; from Sharif.Shahrier@InterDigital.com on Tue, Nov 27, 2001 at 09:45:18AM -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

I'd recommend you send a proposed charter to Allison Mankin (mankin@isi.edu)

PatC
On Tue, Nov 27, 2001 at 09:45:18AM -0500, Shahrier, Sharif M. wrote:
> I was informed by the chair that we need an AD to sponsor such a BOF,
> however I don't know if any AD is interested.
> Perhaps if an AD is interested, he can get in touch.
>  
> -Sharif.
>  
> No, MIP is not sufficient, in my oppinion. There are many other issues
> involved when the MN changes its AP from one WLAN to another. 
>  
> -          Fast, seamless handover.
> -          Authentication and authorization.
> -          Billing (especially if the two WLANs are controlled by different
> operators).
> -          Context transfer
> -          Mobility management.
> -          Quality-of-Service.
>  
> Now, the IETF has different protocol for these, but how they fit together
> into the interworking problem should be looked at.
>  
> Also important, is to understand how the L2 functions in the WLANs
> interoperate with the functions in the IP layer. Perhaps, some functions are
> better done in L2, while others in the IP layer .....
>  
> WLANs are going to be deployed more and more now, in campuses, enterprise
> networks, and also in home networking. And how to interconnect them is of
> great importance.
>  
> Thus, I believe, if there were sufficient interest from people, IETF should
> consider taking an active role in attempting to understand ALL the issues
> and decide what (if anything) to do.
>  
> Thus, a BOF session on "Interconnecting 802.11 in IP Layer"  is a small
> step.
>  
> Shahrier,
>  
> Is there plans for such a BOF?
>  
> Carl
>  
>  


From owner-seamoby@diameter.org  Wed Nov 28 03:44:36 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26325
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Nov 2001 03:44:36 -0500 (EST)
Received: (qmail 1674 invoked by alias); 28 Nov 2001 09:30:58 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 1668 invoked by uid 200); 28 Nov 2001 09:30:57 -0000
Received: (qmail 1663 invoked from network); 28 Nov 2001 09:30:55 -0000
Received: from mgw-x2.nokia.com (131.228.20.22)
  by c900656-a.plstn1.sfba.home.com with SMTP; 28 Nov 2001 09:30:55 -0000
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fAS8iOA23191
	for <seamoby@cdma-2000.org>; Wed, 28 Nov 2001 10:44:28 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T577ef61c91ac158f23134@esvir03nok.nokia.com>;
 Wed, 28 Nov 2001 10:43:33 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <XP215GLH>; Wed, 28 Nov 2001 10:43:31 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D91C9@esebe004.NOE.Nokia.com>
From: john.loughney@nokia.com
To: pcalhoun@diameter.org
Cc: Sharif.Shahrier@InterDigital.com, seamoby@cdma-2000.org
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt
Date: Wed, 28 Nov 2001 10:43:29 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Pat,

> Agreed.... but who would fund this activity :(

The EU is quite good about things, for example these
two projects fall quite much into this area.

	www.ist-brain.org
	www.ist-mind.org

br,
John


From owner-seamoby@diameter.org  Wed Nov 28 07:41:27 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04092
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Nov 2001 07:41:26 -0500 (EST)
Received: (qmail 2617 invoked by alias); 28 Nov 2001 13:27:50 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 2611 invoked by uid 200); 28 Nov 2001 13:27:49 -0000
Received: (qmail 2606 invoked from network); 28 Nov 2001 13:27:47 -0000
Received: from smtp2.cluster.oleane.net (195.25.12.17)
  by c900656-a.plstn1.sfba.home.com with SMTP; 28 Nov 2001 13:27:47 -0000
Received: from oleane (upper-side.rain.fr [194.250.212.114]) by smtp2.cluster.oleane.net with SMTP id fASCeam21597 for <seamoby@cdma-2000.org>; Wed, 28 Nov 2001 13:40:36 +0100 (CET)
Message-ID: <007c01c17809$c05c5580$0601a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <seamoby@cdma-2000.org>
Subject: [seamoby] The third edition of IPCN
Date: Wed, 28 Nov 2001 13:39:41 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0079_01C17812.21D47240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0079_01C17812.21D47240
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

The third edition of IPCN (Intersection and competition of the mobile =
WAN and the WLAN) will stand in Paris next 23-26 April. The dead line =
for submitting abstracts has been extended to December 15th.
Please refer to:
http://www.upperside.fr/ipcn02/baipcn02intro.htm


------=_NextPart_000_0079_01C17812.21D47240
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial>
<DIV><FONT size=3D2>The third edition of <STRONG>IPCN</STRONG> (<SPAN=20
class=3Dtexte><B><FONT color=3D#666666>Intersection and competition of =
the mobile=20
WAN and the WLAN</FONT></B></SPAN>) will stand in Paris next 23-26 =
April. The=20
dead line for submitting abstracts has been extended to December=20
15th.</FONT></DIV>
<DIV><FONT size=3D2>Please refer to:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/ipcn02/baipcn02intro.htm">http://www.uppe=
rside.fr/ipcn02/baipcn02intro.htm</A></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0079_01C17812.21D47240--



From owner-seamoby@diameter.org  Thu Nov 29 06:07:08 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA20498
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Nov 2001 06:07:07 -0500 (EST)
Received: (qmail 4750 invoked by alias); 29 Nov 2001 11:52:44 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4744 invoked by uid 200); 29 Nov 2001 11:52:44 -0000
Received: (qmail 4739 invoked from network); 29 Nov 2001 11:52:42 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 29 Nov 2001 11:52:42 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20263;
	Thu, 29 Nov 2001 06:05:33 -0500 (EST)
Message-Id: <200111291105.GAA20263@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-ietf-seamoby-context-transfer-problem-stat-04.txt
Date: Thu, 29 Nov 2001 06:05:33 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting Working Group of the IETF.

	Title		: Problem Description: Reasons For Performing Context 
                          Transfers Between Nodes in an IP Access Network
	Author(s)	: J. Kempf
	Filename	: draft-ietf-seamoby-context-
                          transfer-problem-stat-04.txt
	Pages		: 12
	Date		: 28-Nov-01
	
In IP access networks that support host mobility, the routing paths 
between the host and the network may change frequently and rapidly. 
In some cases, the host may establish certain routing-related 
services on subnets that are left behind when the host moves. 
Examples of such services are AAA, header compression, and QoS. In 
order for the host to obtain those services on the new subnet, the 
host must explicitly re-establish the service by performing the 
necessary signaling flows from scratch. In some cases, this process 
would considerably slow the process of establishing the mobile host 
on the new subnet. An alternative is to transfer information on the 
existing state associated with these services, or context, to the 
new subnet, a process called 'context transfer'. This document 
discusses the desirability of context transfer for facilitating 
seamless IP mobility.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-seamoby-context-transfer-problem-stat-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-seamoby-context-transfer-problem-stat-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-seamoby-context-transfer-problem-stat-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011128143501.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-seamoby-context-transfer-problem-stat-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-seamoby-context-transfer-problem-stat-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011128143501.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Thu Nov 29 06:10:30 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA21037
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Nov 2001 06:10:30 -0500 (EST)
Received: (qmail 4990 invoked by alias); 29 Nov 2001 11:54:25 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 4982 invoked by uid 200); 29 Nov 2001 11:54:25 -0000
Received: (qmail 4968 invoked from network); 29 Nov 2001 11:54:21 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 29 Nov 2001 11:54:21 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20523;
	Thu, 29 Nov 2001 06:07:11 -0500 (EST)
Message-Id: <200111291107.GAA20523@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-koodli-paging-01.txt
Date: Thu, 29 Nov 2001 06:07:11 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Dormant Mode Handover Support in Mobile Networks
	Author(s)	: S. Faccin, R. Koodli et al.
	Filename	: draft-koodli-paging-01.txt
	Pages		: 31
	Date		: 28-Nov-01
	
This document defines an IP paging concept that supports IP dormancy
for hosts and Mobile Nodes.  The concept specifies a generic model
that can be applied to several mobility mechanisms (including Mobile
IPv6, Localized Mobility Managament) and is independent of the
layer-2 access technology and paging capabilities.  The model allows
for optimizations of the benefits of layer-2 paging when present,
while minimizing the impact on layer-2 paging.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-koodli-paging-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-koodli-paging-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-koodli-paging-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011128143845.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-koodli-paging-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-koodli-paging-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011128143845.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Thu Nov 29 11:18:23 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17845
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Nov 2001 11:18:22 -0500 (EST)
Received: (qmail 7149 invoked by alias); 29 Nov 2001 17:04:37 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 7143 invoked by uid 200); 29 Nov 2001 17:04:36 -0000
Received: (qmail 7138 invoked from network); 29 Nov 2001 17:04:35 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 29 Nov 2001 17:04:35 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN096DKL>; Thu, 29 Nov 2001 11:15:53 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9CB@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'mankin@isi.edu'" <mankin@isi.edu>,
        "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 
Date: Thu, 29 Nov 2001 11:15:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

According to this list ICMP TYPE values from 41-255 are reserved. Now, does
this mean that its possible for individuals to petition IANA, to use a TYPE
value from this range?

Also,  if I'm not mistaken, the ICMP TYPE is 6-bits. This means a maximum of
64 possible TYPE values are available. Thus, what would be the significance
of reserving values from 65-255, since we can't use them anyway?

I would appreciate it f someone could comment on this.

-Sharif.

 -----Original Message-----
From: 	Allison Mankin [mailto:mankin@isi.edu] 
Sent:	Monday, November 26, 2001 8:00 PM
To:	Shahrier, Sharif M.
Cc:	seamoby@cdma-2000.org
Subject:	Re: [seamoby] draft-ietf-seamoby-ct-reqs-02.txt 

> Could anyone please advise me where I can get the document that lists all 
> the standardized (so far) values for TYPE and CODE in the ICMP message? 

The definitive list is the IANA registry:
 
   http://www.iana.org/assignments/icmp-parameters

See also RFC 2780 (BCP 37) about how new ones get approved.


From owner-seamoby@diameter.org  Thu Nov 29 22:20:00 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04529
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Nov 2001 22:19:53 -0500 (EST)
Received: (qmail 8796 invoked by alias); 30 Nov 2001 04:04:21 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 8790 invoked by uid 200); 30 Nov 2001 04:04:21 -0000
Received: (qmail 8785 invoked from network); 30 Nov 2001 04:04:19 -0000
Received: from thumper.research.telcordia.com (128.96.41.1)
  by c900656-a.plstn1.sfba.home.com with SMTP; 30 Nov 2001 04:04:19 -0000
Received: from tari.research.telcordia.com (tari [207.3.232.66])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id fAU3GgkY023247
	for <seamoby@cdma-2000.org>; Thu, 29 Nov 2001 22:16:43 -0500 (EST)
Received: from catfish.research.telcordia.com (ohba@tari-dhcp166.research.telcordia.com [207.3.232.166])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id WAA22631
	for <seamoby@cdma-2000.org>; Thu, 29 Nov 2001 22:16:38 -0500 (EST)
Date: Thu, 29 Nov 2001 22:16:41 -0500
Message-ID: <87r8qh2bja.wl@catfish.research.telcordia.com>
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: seamoby@cdma-2000.org
Subject: [seamoby] comments on paging assessment draft
User-Agent: Wanderlust/2.7.6 (Too Funky) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 5)
 (Civil Service) (i386-debian-linux)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: owner-seamoby@diameter.org
Precedence: bulk



Thanks to the DMHA protocol evaluation team for their excellent job of
producing a useful document.  I think the assessment is reasonable
considering the fact that the work had to be done in such a limited
time period.

Here I have some comments for the assessment on our protocol (please
search "$ohba" for my comments).

Regards,
Yoshihiro Ohba


------------------------------------------------------------
  4.4    draft-ohba-seamoby-last-hop-dmha-02.txt 
    
   The following requirements were not fully met by draft-ohba-seamoby-
   last-hop-dmha-02.txt: 
   _ 
   Requirement 4.1:  Power Consumption 
    
   Registration to the TA through the DMA may not be optimal in terms 
   of power consumption, since a DMA Reg-ACK cannot be returned to the 
   host until the TA acknowledges the proxy registration request. 
   However, since the author also specified the direct communication of 
   the host with the TA, this requirement is overspecified to the 
   degree that can detract from efficiency. 

$ohba: 

I think there is of no difference in power consumption as to
whether the paging registration operation (not the paging area update
operation) is performed directly with the TA or indirectly via DMA,
because even if the direct registration were performed during the
paging registration operation, TA Registration ACK cannot be returned
until the TA successfully performs DMA registration with the DMA.

On the other hand, direct TA Registration would be useful 
in the case of paging area update operation, in which case 
TA Registration ACK can be returned immediately because DMA already 
has DMA state for the Host at the time of paging registration operation.  
That is the reason for defining the direct communication of 
the host with the TA for paging area update operation only.  

Note that paging area update operation can also be performed
indirectly via DMA.  Altough this may not be optimal in terms of total
number of message exchanges, but this would be useful if the Host 
wants to have only one security association with DMA, instead of 
two security associations, one with DMA and the other with TA.
   

   _ 
   Requirement 4.2: Scalability 
    
   The protocol tends to describe its operation with one DMA per link, 
   one TA (primarily) and multiple PAs, as shown in Figure 3. When the 
   protocol suggests that more than one TA can be present and each one 
   manages a specific set of hosts, it fails to specify how this is 
   achieved. 

$ohba: 

I agree that more description is necessary for how the protocol
operates with multiple-TAs.
    
   Requirement 4.4: Efficient Signaling Inactive Mode 
    
   The protocol underspecifies the requirement because it suggests that 
   successive paging operations are to follow a paging interval that 
   increases exponentially, but does not specify an initial and final 
   value that the exponential figure is allowed to reach. Is it 
   persistent in the paging retry? Does it time-out at all?  

$ohba: 

I assumed the latter.  The state for inactive hosts would be deleted
when DMA registration lifetime expires.  We could also have
another final value which is smaller than the DMA registration
lifetime for exponential backoff.

   _ 
   Requirement 4.6: Multiple Dormant Modes 
    
   The type of dormant modes that the protocol attempts to support is 
   based on a particular technology, while the protocol does not affect 
   the operation of the MAC layer at all. While one can claim that the 
   protocol combines L2 power saving features that contribute to power 
   conservation, this is not owed to or couple with the proposed 
   protocol. It is simply a manifestation of power savings through 
   special forms of MPDU scheduling. Any protocol can claim such 
   cooperation. Important aspect of dormancy like slotted dormant for 
   non-L2 layer has not been considered by the protocol. 

$ohba: 

Right, time-slotted dormant mode at L3 is not supported yet, I think
we still need more investigation on how accurate synchronization is
realized at L3, which would be required to support time-slotted
dormant mode at L3.
    
   Requirement 4.12: Orthogonality of PA and Subnets 
    
   The description of the protocol, although it mentions paging areas, 
   does not specify clearly how this is achieved since there is no 
   specific description of how the page message diffuses over an 
   topology of multiple subnets that are controlled by a single PA. 

$ohba: 

When a PA takes care of multiple subnets, there would be two cases.
If L2 paging is available, the PA just kicks L2 paging for the set of
L2 paging areas that covers the subnets.  On the other hand, if L2
paging is not used, all the ARs of those subnets should join the
multicast group which is used for carrying Paging messages, and the PA
multicasts the Paging messages to that multicast group address.  Each
AR then just forwards the multicast Paging messages on to its last hop
subnet(s).

I agree that this kind of description is missing in the document.  

   _ _
   Requirement 4.14: Robustness against Failures
    
   While the protocol specifies keep-alive signals between the peer 
   agents, it does not specify a scheme that allows recovery from 
   failure.  
   _ 
   Requirement 4.15: Reliability of Packet Delivery 
    
   The transport used in this protocol is UDP. The protocol does not 
   describe how the packet is forwarded to the host. In particular, it 
   does not describe what is the situation when the packet received at 
   the DMA is TCP. 

$ohba: 

TCP would not be an appropriate DMHA message carrier.  One reason is
that in some cases DMHA messages are multicast.  Another reason is
that the CoA of a Host may change while it is in dormant mode (and it
does not perform mobility binding update), in which case the Host
would use CoA for DMHA protocol exchanges but if TCP is used the TCP
connection would get lost after the CoA change.  Another reason is
that if a large number of Hosts are dormant, then the DMA would have
to maintain a large number of TCP connection states with dormant
Hosts, which would consume OS kernel memories at the DMA.

   _ 
     
   Requirement 4.17: Administrative Flexibility 
    
   The configuration of the paging areas is not quite automatic as 
   claimed. In particular the protocol does not specify how the page 
   area identifiers are assigned/allocated such that they can be 
   distributed to the individual paging agents.  
   _ 
   Requirement 4.18: Flexibility of PA Design 
    
   With respect to the claimed flexibility, the design is not clear in 
   Fig. 3. The TA propagates paging requests, why? 

$ohba:

There is a design choice as to whether the TA acts as a relay agent or
redirect agent for the Paging messages.  If TA acts as a redirect
agent, then it would not scale well if we assume the number of DMAs
and PAs are much larger than that of TAs, because each DMA has to have
a security association for each PA or for a set of PAs to send Paging
messages directly from DMA to PAs.  That is the reason for defining
the TA as a relay agent.

   _ 
   Requirement 4.19: Availability of Security Support 
    
   The protocol does not support encryption services. It only supports 
   authentication. For ESP security, it relies on mechanisms such as 
   IPsec.  

$ohba: 

Right. As I mentioned in the recent thread "DMHA and IPsec", IPsec
would not be appropriate for DMHA.  On the other hand, defining an
encryption mechanism is tough.  I think a PBK-like common security
mechanism which uses stable identifier for identifying a Host would be
really desired.

    
   In addition, the following general concerns were expressed about the 
   protocol design: 
    
     1) The protocol utilizes the DMA like the TA in the functional 
        architecture draft, but does not specify a method for the DMA 
        to discover an appropriate TA. The assumption seems to be that 
        there will be a single TA per administrative domain or multiple 
        TAs with the TA to DMA mapping manually configured.  

$ohba:  

The current assumption is latter.  

      
     2) The protocol assumes the dormant host can detect a paging area 
        change, which implies that time-slotted paging must be used if 
        there is no L2 paging channel support. However, the protocol 
        does not explicitly mention how it would support time-slotted 
        paging. 

$ohba: 

Please refer to my comments on Requirement 4.6.

 
     3) The proxy interactions between the DMA and TA on behalf of the 
        dormant host incur extraneous signaling and may lead to 
        inefficient power consumption.  
 
$ohba: 

Please refer to my comments on Requirement 4.1.

     4) The assumption that the DMA is located on the last hop subnet, 
        which is the foundation of the design, means that the PA is 
        unnecessary, and links the paging area directly to the subnet. 

$ohba:

I think there is some misunderstanding here.  DMA is assumed to be in
last-hop subnet because it is the place where any packet destined for
the dormant Host always reaches, but PA should be put anywhere and is
necessary, given that the relationship between subnets and paging
areas is orthogonal.


     5) The protocol specifies heartbeat messages between agent peers. 
        This method can identify a failed agent, but it cannot specify 
        how to recover from failure. 
 
     6) The protocol does not specify how a host chooses between DMAs 
        nor how a DMA chooses between TAs. 

------------------------------------------------------------


From owner-seamoby@diameter.org  Fri Nov 30 05:59:16 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02339
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Nov 2001 05:59:15 -0500 (EST)
Received: (qmail 9729 invoked by alias); 30 Nov 2001 11:45:18 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 9723 invoked by uid 200); 30 Nov 2001 11:45:18 -0000
Received: (qmail 9718 invoked from network); 30 Nov 2001 11:45:16 -0000
Received: from odin.ietf.org (HELO ietf.org) (132.151.1.176)
  by c900656-a.plstn1.sfba.home.com with SMTP; 30 Nov 2001 11:45:16 -0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02154;
	Fri, 30 Nov 2001 05:58:03 -0500 (EST)
Message-Id: <200111301058.FAA02154@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-koodli-seamoby-ctv6-02.txt
Date: Fri, 30 Nov 2001 05:58:03 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Context Transfer Framework for Seamless Mobility
	Author(s)	: R. Koodli, C. Perkins
	Filename	: draft-koodli-seamoby-ctv6-02.txt
	Pages		: 29
	Date		: 29-Nov-01
	
Mobile nodes enhance their connections across wireless media
by establishing various kinds of state (context), in order to
make practicable, secure, and economical use of the available
bandwidth.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-koodli-seamoby-ctv6-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-koodli-seamoby-ctv6-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-koodli-seamoby-ctv6-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011129143839.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-koodli-seamoby-ctv6-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-koodli-seamoby-ctv6-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011129143839.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-seamoby@diameter.org  Fri Nov 30 09:51:14 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13730
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Nov 2001 09:51:12 -0500 (EST)
Received: (qmail 12638 invoked by alias); 30 Nov 2001 15:36:38 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 12632 invoked by uid 200); 30 Nov 2001 15:36:37 -0000
Received: (qmail 12627 invoked from network); 30 Nov 2001 15:36:36 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 30 Nov 2001 15:36:36 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN096F6R>; Fri, 30 Nov 2001 09:47:56 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9D1@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: seamoby@cdma-2000.org
Subject: [seamoby] Requirements draft
Date: Fri, 30 Nov 2001 09:47:49 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C179AD.FB156130"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C179AD.FB156130
Content-Type: text/plain;
	charset="iso-8859-1"

 
Gary,
 
            I was wondering if you had issued the updated draft of the
requirements document for CT? If not, when would it be available?
 
-Sharif. 

------_=_NextPart_001_01C179AD.FB156130
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C17984.D9C3B410">
<title>RE: Who wants seamless handovers anyway? was RE: [seamoby] draft =
-iet
f-seamoby-ct-reqs-02.txt</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.para1, li.para1, div.para1
	{mso-style-name:para1;
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:.5in;
	line-height:200%;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-language:HE;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle19><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><=
![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>Gary,</span></font><font =
color=3Dnavy><span
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span>I
was wondering if you had issued the updated draft of the requirements =
document
for CT? If not, when would it be available?</span></font><font =
color=3Dnavy><span
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dnavy><span =
style=3D'color:navy;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>-Sharif.</span></font><font =
color=3Dblack><span
style=3D'color:black'> </span></font><font color=3Dblack><span =
style=3D'color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C179AD.FB156130--


From owner-seamoby@diameter.org  Fri Nov 30 10:15:09 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14989
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Nov 2001 10:15:08 -0500 (EST)
Received: (qmail 13188 invoked by alias); 30 Nov 2001 16:01:37 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13182 invoked by uid 200); 30 Nov 2001 16:01:37 -0000
Received: (qmail 13177 invoked from network); 30 Nov 2001 16:01:36 -0000
Received: from idcmail.interdigital.com (HELO idcpa4.pa.interdigital.com) (12.32.197.142)
  by c900656-a.plstn1.sfba.home.com with SMTP; 30 Nov 2001 16:01:36 -0000
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN096F0D>; Fri, 30 Nov 2001 10:12:57 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D0327F9D2@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: seamoby@cdma-2000.org
Subject:  [seamoby] INTERPRETATION QUESTION: CT REQUIREMENTS DRAFT
Date: Fri, 30 Nov 2001 10:12:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


I have a question for clarification in the context transfer requirements
draft.

4.5 "Any IP level signaling for Context Transfer" MUST be separated from the
actual transfer of context.


Now, the text inside "..." , does it refer to the IP level trigger signal
from the MN, (or) does it mean the signaling messages between the two ARs
for the actual context transfer?

I am guessing that it means the latter.

-Sharif.



From owner-seamoby@diameter.org  Fri Nov 30 11:04:19 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA18063
	for <seamoby-archive@lists.ietf.org>; Fri, 30 Nov 2001 11:04:17 -0500 (EST)
Received: (qmail 13751 invoked by alias); 30 Nov 2001 16:49:10 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 13745 invoked by uid 200); 30 Nov 2001 16:49:09 -0000
Received: (qmail 13740 invoked from network); 30 Nov 2001 16:49:08 -0000
Received: from zcars0m9.nortelnetworks.com (47.129.242.157)
  by c900656-a.plstn1.sfba.home.com with SMTP; 30 Nov 2001 16:49:08 -0000
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fAUG0pd08839
	for <seamoby@cdma-2000.org>; Fri, 30 Nov 2001 11:00:51 -0500 (EST)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Fri, 30 Nov 2001 11:01:16 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <X6VFFDJT>; Fri, 30 Nov 2001 11:00:13 -0500
Message-ID: <9FBD322B7824D511B36900508BF93C9C025A0074@zcard031.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Requirements draft
Date: Fri, 30 Nov 2001 11:00:17 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C179B8.1B0A5590"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C179B8.1B0A5590
Content-Type: text/plain;
	charset="ISO-8859-1"

The -02 version has been submitted to ietf.org and a copy was provided to
the wg chairs.
 
gary
-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: November 30, 2001 09:48
To: Kenward, Gary [WDLN2:AN10:EXCH]
Cc: seamoby@cdma-2000.org
Subject: [seamoby] Requirements draft
Sensitivity: Confidential


 
Gary,
 
            I was wondering if you had issued the updated draft of the
requirements document for CT? If not, when would it be available?
 
-Sharif. 

------_=_NextPart_001_01C179B8.1B0A5590
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<TITLE>RE: Who wants seamless handovers anyway? was RE: [seamoby] draft =
-iet f-seamoby-ct-reqs-02.txt</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C17984.D9C3B410" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>P.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN-LEFT: 0in; =
MARGIN-RIGHT: 0in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
P.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
LI.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
DIV.para1 {
	FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; LINE-HEIGHT: 200%; =
MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5in; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-style-name: para1; =
mso-bidi-language: HE
}
SPAN.EmailStyle19 {
	COLOR: navy; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US link=3Dblue style=3D"tab-interval: .5in" =
vLink=3Dblue>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D590030216-30112001>The=20
-02 version has been submitted to ietf.org and a copy was provided=20
to</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D590030216-30112001>the wg=20
chairs.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D590030216-30112001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D590030216-30112001>gary</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Shahrier, Sharif =
M.=20
  [mailto:Sharif.Shahrier@InterDigital.com]<BR><B>Sent:</B> November =
30, 2001=20
  09:48<BR><B>To:</B> Kenward, Gary [WDLN2:AN10:EXCH]<BR><B>Cc:</B>=20
  seamoby@cdma-2000.org<BR><B>Subject:</B> [seamoby] Requirements=20
  draft<BR><B>Sensitivity:</B> Confidential<BR><BR></DIV></FONT>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT color=3Dnavy =
face=3DArial=20
  size=3D2><SPAN=20
  style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><FONT color=3Dnavy face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: navy; FONT-SIZE: 12pt">Gary,</SPAN></FONT><FONT =
color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: navy; FONT-SIZE: 12pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT=20
  color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: navy; FONT-SIZE: 12pt"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>I was wondering if you had issued the updated draft of the =
requirements=20
  document for CT? If not, when would it be =
available?</SPAN></FONT><FONT=20
  color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: navy; FONT-SIZE: 12pt"><![if =
!supportEmptyParas]>&nbsp;<![endif]></SPAN></FONT><FONT=20
  color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"COLOR: navy; FONT-SIZE: 12pt">-Sharif.</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black"> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C179B8.1B0A5590--


From owner-seamoby@diameter.org  Fri Nov 30 20:58:18 2001
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20634
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Nov 2001 20:58:18 -0500 (EST)
Received: (qmail 15296 invoked by alias); 1 Dec 2001 02:44:44 -0000
Delivered-To: seamoby-list@charizard.diameter.org
Received: (qmail 15290 invoked by uid 200); 1 Dec 2001 02:44:43 -0000
Received: (qmail 15284 invoked by uid 500); 1 Dec 2001 02:44:41 -0000
Date: Fri, 30 Nov 2001 18:44:41 -0800
From: Pat Calhoun <pcalhoun@diameter.org>
To: seamoby@cdma-2000.org
Cc: mankin@isi.edu
Subject: [seamoby] Mailing List
Message-ID: <20011130184441.A15275@charizard.diameter.org>
Mail-Followup-To: seamoby@cdma-2000.org, mankin@isi.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

Following the recent @Home court decision, the seamoby mailing list may be
torn down. I would be interested in anyone that may have the resources to
host the mailing list.

At this time, it is still unclear on whether the @Home service will be
shutdown or not, but if it is, it could occur as soon as next Monday.

PatC


