From seamoby-admin@ietf.org  Tue Dec  4 11:18:22 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00201
	for <seamoby-archive@odin.ietf.org>; Tue, 4 Dec 2001 11:18:22 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23052
	for <seamoby-archive@lists.ietf.org>; Tue, 4 Dec 2001 11:18:25 -0500 (EST)
Date: Tue, 4 Dec 2001 11:18:25 -0500 (EST)
Message-Id: <200112041618.LAA23052@optimus.ietf.org>
From: seamoby-admin@ietf.org
Subject: Welcome To "Seamoby"! 
To: seamoby-archive@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>

Welcome to the Seamoby@ietf.org mailing list!

********** Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which
are addressed to

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

*********


To post to this list, send your email to:

  seamoby@ietf.org

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/seamoby

If you ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:

  https://www1.ietf.org/mailman/options/seamoby/seamoby-archive@lists.ietf.org


You can also make such adjustments via email by sending a message to:

  Seamoby-request@ietf.org

with the word `help' in the subject or body (don't include the
quotes), and you will get back a message with instructions.

You must know your password to change your options (including changing
the password, itself) or to unsubscribe.  It is:

  Zzch

If you forget your password, don't worry, you will receive a monthly
reminder telling you what all your ietf.org mailing list passwords
are, and how to unsubscribe or change your options.  There is also a
button on your options page that will email your current password to
you.

You may also have your password mailed to you automatically off of the
Web page noted above.


From seamoby-admin@ietf.org  Tue Dec  4 11:46:52 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01038
	for <seamoby-archive@odin.ietf.org>; Tue, 4 Dec 2001 11:46:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23978;
	Tue, 4 Dec 2001 11:30:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23939
	for <seamoby@optimus.ietf.org>; Tue, 4 Dec 2001 11:30:44 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.netlab.nec.de [195.37.70.1] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00411
	for <seamoby@ietf.org>; Tue, 4 Dec 2001 11:30:39 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace.heidelberg.ccrle.nec.de [192.168.102.1])
	by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id fB4GUAk11452
	for <seamoby@ietf.org>; Tue, 4 Dec 2001 17:30:10 +0100 (CET)
Received: from ccrle.nec.de (judiciary.heidelberg.ccrle.nec.de [192.168.102.83])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA04795
	for <seamoby@ietf.org>; Tue, 4 Dec 2001 17:30:16 +0100
Message-ID: <3C0CFA18.1C8C89D0@ccrle.nec.de>
Date: Tue, 04 Dec 2001 17:30:16 +0100
From: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Feedback on Paging protocol assessment, draft-renker-paging-ipv6-01.txt
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dear all,

these are some comments on the Seamoby DMHA protocol assessment draft.
The related proposal is <draft-renker-paging-ipv6-01.txt>. Numbers refer

to the respective chapter in the requirements document, as they are used

also in the assessment draft. Please feel free to comment on this.

Regards,

Marco

---------------

4.2 Scalability
At least one signaling handshake is required for registration of a MN
with its serving Paging Agent (PA). Dependent on the integration of
the Paging Agent into the mobility platform, if dedicated paging
trigger packet forwarding to the Paging Agent is to be made use of,
the mobility agents have to redirect packets to the PA instead of to
the MN directly. Therefore, the respective PA is to be registered
with the mobility agent for this purpose, which is one additional
handshake in case of MIP. This registration can be valid for the
entire allowed registration lifetime (which should be large). When
integrating the PA appropriately within a domain, packet filtering
for registered MNs could be made use of. This could avoid the
explicit registration of the PA with the mobility agent (but does not
solve the increased registration lifetime issue). As a general
comment, I advacoate the first approach described, but the Paging
Agent should support packet filtering/tracking as well. The concept
allows deployment of the PA from outside a domain (e.g. for
inter-domain paging). When following the establlishment of required
security associations, this would allow a MN to have its individual
Paging Agent (for example at home). For inter-domain paging, security
associations have to be taken care of, since the PA addresses the
paging related functional entities in individual domain's Access
Routers. Having more (assigned) PA should allow coping with the
scalability issue, even if more advanced paging strategies (not only
blanket polling) are to be deployed.

4.4 Efficient Signaling for Inactive Mode
The MN is either registered as IDLE or ACTIVE. When a MN is INACTIVE,
this is not an explicit state transition, which is to be signaled,
but could happen due to entering a location, where no wireless link
connection is available for any reason (e.g. due to obstacles) or
when the MN switches off due to unexpectied reasons (MN crashes).
Therefore, a MN never notifies the system of entering an inactive
state. It's up to the system to discover, that the MN is currently
not reachable. This is to be done only in case of an incoming paging
trigger packet. When the MN does not respond to paging request messages,

it's marked as 'not reachable' or 'inactive'.This behaviour is
described in D.4 of draft-renker-paging-ipv6-01.txt. From signaling
point of view, at least a search within the registered paging area is
to be done before the MN can be marked as 'not reachable' [exponential
backoff behaviour]. For this process, even enhanced paging strategies
(for example sequential polling) introduce no gain in signaling
avoidance. Tracking the idle MN by e.g. polling periodically or
expecting the MN to send 'heartbeat massages' in order to proof
that the MN is able to answer a possible Paging Request, is somehow
against the concepts of paging and idle mode support.

4.6
Early requirements of the paging protocol referred to a paging
protocol, which should be independent of link interface specifics.
What the Paging Agent in draft-renker-paging-ipv6-01.txt supports
is a L3 protocol, that is independent of link interface specifics
'up to the Access Routers'. An appropriate paging functional entity
in each Access Router can map the L3 Paging Requests to link specifics
(L2 wake up mechanisms, ...) in order to support hardware power saving
modes. If there are more modes possible per interface and the MN
should select one and store this mode with the system, then some more
message options would be required (which could be easily conveyed as
TLV-encoded (sub-)options. Specifics on access technology should not
(yet) be part of the paging architecture/protocol specification yet.
First We should focus on having a generic functional architecure,
which allows easily extensions like the one discussed in this section
(and others).

4.7 Independence of Mobility Protocol
Of course, in order to be generic, the explicit case is the choosen
signaling approach.

4.9 Dormant Mode Termination
When the MN has been paged, having first a nCoA registration with
the mobility agent avoids timing complications with PA de-registration.
Then the PA is to be notified of the MN's nCoA in order to allow
paging trigger packet's forwarding to the MN (mechanism: IPIP
encapsulation).

4.10 Network updates
When having static paging areas in a system, the MN updates
its Paging Agent with a new paging area identifier. For the
'implicit case', the PA could assign the packets source address prefix
to a static paging area. But, since the generic case (mobility
independent solution' is considered in Seamoby, the explicit
signaling case should be considered. In case of having individual
paging areas, these could require less system updates with respect
to leaving/entering paging areas.
In the latter case, individual AR identifier are for example to be
made use of instead of having one identifier for a static set of ARs
as a paging area. This allows more flexible paging area construction.

4.11 Efficient Utilization of L2
As decribed above and in draft-renker-paging-ipv6-01.txt, the
concept specifies paging relevant functional entities (FE) in
Access Routers, having knowledge on their respective access
technology. This FE makes use of L2 specifics on the access link
in order to support interworking of L3 /L2- paging and dormant modes.
Dependent on the mobility platform, the MN has to send updates to
the network frequently. When no connection is open and having the
requirements of entering the IDLE mode of
draft-renker-paging-ipv6-01.txt in mind, the MN should enter L3
dormancy. Dependent on the interface technology, these timers
and algorithms (L2/L3 dormancy) could be optimized.

4.12 Orthogonality of PA and subnets
Since multiple access technologies are to be used, some static
identifier must be used in order to address individual idle
mobile nodes. This should be the same for cellular and non-cellular
networks. This could be the home address for MIP managed networks.
We expect administrative domains supporting several access
technologies. Access Routers supporting different link technologies
can be grouped to a L3 paging area on a static basis as well as on
an individual basis. In a current project, we assume one Access
Router link interface supporting one ip subnet. Whether an individual
Access Router provides access to MNs with multiple L2 Access Points,
this does not influence the L3 paging area construction.

4.15 Reliability of Packet Delivery
The described mechanism, where encapsulated packets arrive at
the Paging Agent as paging trigger packets, makes use of
encapsulation (tunnelling) in order to forward the packet to
its final destination as soon as the new address (nCoA for MIP) is
known.

4.19 and the following: Security issues
Currently, as described in draft-renker-paging-ipv6-01.txt,
the concept makes use of IPSec for sender authentication. The concept
described on how the Paging Agent integrates to a security platform
(as discussed in the IETF). No details are described yet on SA
establishment mechanisms, but IPSec is currently used for providing
fields for sender authentication and integrity check.






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


From seamoby-admin@ietf.org  Thu Dec  6 00:06:34 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01213
	for <seamoby-archive@odin.ietf.org>; Thu, 6 Dec 2001 00:06:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22511;
	Wed, 5 Dec 2001 23:51:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22479
	for <seamoby@optimus.ietf.org>; Wed, 5 Dec 2001 23:51:54 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00929
	for <seamoby@ietf.org>; Wed, 5 Dec 2001 23:51:48 -0500 (EST)
Received: from T23KEMPF (dhcp86.docomo-usa.com [172.21.96.86])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fB64pK504191
	for <seamoby@ietf.org>; Wed, 5 Dec 2001 20:51:21 -0800 (PST)
Message-ID: <003301c17e11$6c980350$566015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@ietf.org>
Date: Wed, 5 Dec 2001 20:49: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
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Wireless Directorate
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

A couple people sent me a question about the Wireless Directorate, which
I mentioned in recent email. The Wireless Directorate was recently
formed to facilitate communication between WG chairs and ADs involved in
WGs that are concerned with wireless. With the growth in WGs looking at
wireless, it becomes more likely that issues may arise on the border
between two or more WG charters. In order to make sure they don't fall
through the cracks, the Wireless Directorate was formed. A similar
approach was taken with IPv6 and has been successful. The WG chairs and
ADs involved in wireless topics are members.

                jak


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


From seamoby-admin@ietf.org  Mon Dec 10 23:40:13 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21214
	for <seamoby-archive@odin.ietf.org>; Mon, 10 Dec 2001 23:40:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA26899;
	Mon, 10 Dec 2001 23:19:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA26868
	for <seamoby@optimus.ietf.org>; Mon, 10 Dec 2001 23:19:38 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20036
	for <seamoby@ietf.org>; Mon, 10 Dec 2001 23:19:36 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id WAA19461;
	Mon, 10 Dec 2001 22:19:06 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id fBB4J4s20875;
	Mon, 10 Dec 2001 22:19:04 -0600 (CST)
Message-ID: <3C15890F.2010209@alcatel.com>
Date: Mon, 10 Dec 2001 22:18:23 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: seamoby@ietf.org
References: <0C1353ABB1DEB74DB067ADFF749C4EEF6E5E06@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Re: [mobile-ip] L2 triggers draft
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

John et al.,
  I suggest having a pre BOF meeting here at SLC. Maybe Wednesday night?


john.loughney@nokia.com wrote:

>Hi all,
>
>>My opinion is, among existing working groups it best fits PILC.
>>
>>But, if we want to do a better job (more than L2 triggers), then I'd
>>recommend forming a new Sub-IP working group: IP over Wireless.
>>
>
>Its too late for Salt Lake City & maybe too early for Minneapolis,
>but I think a bof on this general area would be useful.  In 
>NSIS, there is some discussion on if/how you could tie air
>interface (layer 2) QoS properties into layer 3.  I think
>a BOF with some general discussion on the problem area(s), at
>least to give some scope to the problem would be very interesting.
>We want to make sure we don't go 'ocean-boiling' ....
>
>best regards,
>John
>

-- 
Behcet 




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


From seamoby-admin@ietf.org  Wed Dec 12 11:23:50 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12575
	for <seamoby-archive@odin.ietf.org>; Wed, 12 Dec 2001 11:23:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25739;
	Wed, 12 Dec 2001 11:05:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25711
	for <seamoby@optimus.ietf.org>; Wed, 12 Dec 2001 11:05:11 -0500 (EST)
Received: from EXCHSRV.stormventures.com ([65.107.25.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11814
	for <seamoby@ietf.org>; Wed, 12 Dec 2001 11:05:02 -0500 (EST)
Received: by EXCHSRV.stormventures.com with Internet Mail Service (5.5.2653.19)
	id <YVAFN9Z1>; Wed, 12 Dec 2001 08:04:36 -0800
Message-ID: <DC6C13921CCAFB49BCB8461164A3F4E38D2123@EXCHSRV.stormventures.com>
From: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Date: Wed, 12 Dec 2001 08:04:35 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C18326.B18601F0"
Subject: [Seamoby] WG Last Call: draft-ietf-seamoby-cardiscovery-issues-01.txt
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

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_01C18326.B18601F0
Content-Type: text/plain

All,

Given the changes that were raised and addressed during the previous last
call of the above document, another last call is needed. The last call will
expire January 4th.

PatC

------_=_NextPart_001_01C18326.B18601F0
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>WG Last Call: =
draft-ietf-seamoby-cardiscovery-issues-01.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>Given the changes that were raised and addressed =
during the previous last call of the above document, another last call =
is needed. The last call will expire January 4th.</FONT></P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C18326.B18601F0--

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


From seamoby-admin@ietf.org  Wed Dec 12 11:23:54 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12589
	for <seamoby-archive@odin.ietf.org>; Wed, 12 Dec 2001 11:23:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25871;
	Wed, 12 Dec 2001 11:06:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25840
	for <seamoby@optimus.ietf.org>; Wed, 12 Dec 2001 11:06:40 -0500 (EST)
Received: from EXCHSRV.stormventures.com ([65.107.25.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11901
	for <seamoby@ietf.org>; Wed, 12 Dec 2001 11:06:34 -0500 (EST)
Received: by EXCHSRV.stormventures.com with Internet Mail Service (5.5.2653.19)
	id <YVAFN9ZG>; Wed, 12 Dec 2001 08:06:08 -0800
Message-ID: <DC6C13921CCAFB49BCB8461164A3F4E38D2124@EXCHSRV.stormventures.com>
From: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Date: Wed, 12 Dec 2001 08:06:07 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C18326.E852F030"
Subject: [Seamoby] WG Last Call: draft-ietf-seamoby-paging-protocol-assessment-00.tx
 t
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

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_01C18326.E852F030
Content-Type: text/plain

The above document is in WG last call, which will expire on January 4th. Any
comments should be sent to the authors, or to the list (but I prefer the
latter).

Thanks,

PatC

------_=_NextPart_001_01C18326.E852F030
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>WG Last Call: =
draft-ietf-seamoby-paging-protocol-assessment-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The above document is in WG last call, which will =
expire on January 4th. Any comments should be sent to the authors, or =
to the list (but I prefer the latter).</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C18326.E852F030--

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


From seamoby-admin@ietf.org  Fri Dec 14 11:13:57 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01837
	for <seamoby-archive@odin.ietf.org>; Fri, 14 Dec 2001 11:13:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03421;
	Fri, 14 Dec 2001 11:00:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03385
	for <seamoby@ns.ietf.org>; Fri, 14 Dec 2001 11:00:06 -0500 (EST)
Received: from EXCHSRV.stormventures.com ([65.107.25.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01524
	for <seamoby@ietf.org>; Fri, 14 Dec 2001 11:00:02 -0500 (EST)
Received: by EXCHSRV.stormventures.com with Internet Mail Service (5.5.2653.19)
	id <YVAF3AS6>; Fri, 14 Dec 2001 07:59:32 -0800
Message-ID: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com>
From: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Date: Fri, 14 Dec 2001 07:59:24 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C184B8.4CD438B0"
Subject: [Seamoby] WG Last Call: draft-ietf-seamoby-ct-reqs-02.txt
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

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_01C184B8.4CD438B0
Content-Type: text/plain

All,

The above document addresses comments raised during the previous last call,
and requires another last call. Please send any comments to the WG mailing
list (or to the authors) by Jan 4th.

PatC

------_=_NextPart_001_01C184B8.4CD438B0
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>WG Last Call: draft-ietf-seamoby-ct-reqs-02.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>The above document addresses comments raised during =
the previous last call, and requires another last call. Please send any =
comments to the WG mailing list (or to the authors) by Jan =
4th.</FONT></P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C184B8.4CD438B0--

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


From seamoby-admin@ietf.org  Sat Dec 15 18:47:23 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08556
	for <seamoby-archive@odin.ietf.org>; Sat, 15 Dec 2001 18:47:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24873;
	Sat, 15 Dec 2001 18:32:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24844
	for <seamoby@ns.ietf.org>; Sat, 15 Dec 2001 18:31:59 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08471
	for <seamoby@ietf.org>; Sat, 15 Dec 2001 18:31:54 -0500 (EST)
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 RAA09849
	for <seamoby@ietf.org>; Sat, 15 Dec 2001 17:31:24 -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 fBFNVMm27154
	for <seamoby@ietf.org>; Sat, 15 Dec 2001 17:31:23 -0600 (CST)
Message-ID: <3C1BDB8B.4020101@alcatel.com>
Date: Sat, 15 Dec 2001 17:23:55 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dear All,
  According to the slides presented by WG cochair on Friday Dec. 14, 
2001 at IETF 52 (these slides have to be posted for public access, as 
other WGs do), the two drafts:
draft 1. draft-sarikaya-seamoby-mipv6hp-00.txt and
draft 2. draft-guri-seamoby-lahap-00.txt
were considered together because they were submitted by the same team and
since draft-sarikaya-seamoby-mipv6hp-00.txt
was based on hmipv6 both of them were eliminated, i.e. 
draft-guri-seamoby-lahap-00.txt was not at all considered, there were no 
slides on this draft..
  This raises several concerns on my side:
- the two drafts have only two authors in common, the two draft main 
authors are different and
more importantly the two drafts define two different paging protocols.
- draft 1 is an extension of Mobile IPv6. Its dependence on hmipv6 can 
easily be removed, as we intend to do it in the next version.
- draft 2 is completely based on the architecture defined in RFC 3154. 
Apart from many other aspects, it defines paging triggers.
- draft 2 was probably the only draft that generated some discussion on 
the maling list by people who have not submitted drafts, i.e., by 
external people .
- WG cochair Jim sent us private emails providing some useful feedback 
on the definition of an API for paging triggers. He even offered to 
collaborate on a joint draft. I have the emails and willing to 
distribute them on the mailing list if asked.

  Based on the above facts I hereby declare the paging protocol 
assessment to be moot.

Regards,

-- 
Behcet 




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


From seamoby-admin@ietf.org  Mon Dec 17 05:46:07 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29081
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 05:46:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00026;
	Mon, 17 Dec 2001 05:26:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA29993
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 05:26:15 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28973
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 05:26:11 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id fBHAQCJ22561
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 11:26:12 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Dec 17 11:25:54 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <YHKQNBF0>; Mon, 17 Dec 2001 11:26:08 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C131@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'Behcet Sarikaya'" <behcet.sarikaya@alcatel.com>,
        "'seamoby@ietf.org'"
	 <seamoby@ietf.org>
Subject: RE: [Seamoby] Paging Protocol Assessment Presentation at SLC
Date: Mon, 17 Dec 2001 11:25:47 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

  > access, as 
  > other WGs do), the two drafts:
  > draft 1. draft-sarikaya-seamoby-mipv6hp-00.txt and
  > draft 2. draft-guri-seamoby-lahap-00.txt
  > were considered together because they were submitted by the 
  > same team and
  > since draft-sarikaya-seamoby-mipv6hp-00.txt
  > was based on hmipv6 both of them were eliminated, 

=> I missed the early part of the meeting, but 
was that a reason ?? ie, just because it's based on HMIPv6 ?

Hesham


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


From seamoby-admin@ietf.org  Mon Dec 17 10:24:18 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05298
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 10:24:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07507;
	Mon, 17 Dec 2001 10:10:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07477
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 10:10:12 -0500 (EST)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04621
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 10:10:09 -0500 (EST)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id IAA07322 for <seamoby@ietf.org>; Mon, 17 Dec 2001 08:10:08 -0700 (MST)]
Received: [from m-il06-r3.mot.com (m-il06-r3.mot.com [129.188.137.194]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id IAB04775 for <seamoby@ietf.org>; Mon, 17 Dec 2001 08:10:08 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r3.mot.com with ESMTP; Mon, 17 Dec 2001 09:09:59 -0600
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 5A2812EC83; Mon, 17 Dec 2001 16:08:40 +0100 (CET)
To: manet@itd.nrl.navy.mil, seamoby@ietf.org, ipng@sunroof.eng.sun.com,
        irtf-rr@puck.nether.net
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 17 Dec 2001 15:07:00 +0100
Message-Id: <m3vgf63pq3.fsf@test9.crm.mot.com>
Lines: 80
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Seamoby] Announce: Mobile Networks monet mailing list
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

                   [Please apologize cross-posting]

Hi,

At the end of the bar bof on Mobile Networks at Salt Lake it was
suggested to re-send the information on how to join the monet mailing
list.

In order to join, please send mail to monet-request@crm.mot.com with
subscribe in the body.

An archive file is kept locally but not yet available publicly.  I can
send it personally.

Thank you,

Alex

PS: here's the original announcement sent earlier on Mobile IP list

Dear colleagues,

I would like to announce the monet (mobile network) mailing list for
future discussion of the mobile networks subject.

Until the last IETF meeting, Thierry Ernst has submitted several times
I-Ds and made presentations on the subject.  At IETF-51, I was
encouraged by the mobileip WG co-chair Phil Roberts to set up a
separate mailing list to further discuss the subject.  Since then,
there has been some discussions online and offline, to the extent that
a BOF may be on its way to address the subject.

Having sensed the need to have a proper forum of discussion on mobile
network, the Monet mailing list is created, so that we could discuss
and share:

- work out the problem scope/statement
- define terminology
- technical discussions
- define the solution requirements
- plan the necessary activities
- how to address the subject in IETF (creation of a BOF?)
- etc

To start with, I would like to put forward the following 2 I-Ds:
- draft-ernst-mobileip-v6-network-02.txt
- draft-ernst-mobileip-monetv6-00.txt

In particular I would like to solicit comments on
draft-ernst-mobileip-monetv6-00.txt about the problem scope and
solution requirements.

After London IETF a long discussion took place on the mobileip list
with respect to mobile networks and routers: terminology for "router"
and "mobile router", MR and router adjacency, interactions of mobile
networks with routing protocols, multiple Care-of-Addresses, mobile
routers as NAT's, tunnelling and routing headers, security aspects,
mobile networks as PANs and many other subjects.  Several solutions
could be designed as a result of those discussions.

Besides, I would also like to gather your ideas and comments on the
creation of a monet BOF.

I am looking forward to your participation in the monet mailing list
discussion. Subscribe to the monet mailing list by sending mail to

monet-request@crm.mot.com

with the word "subscribe" (without the quotes) in the body. You need to
subscribe to the list in order to send to the list. You can post to the list by
sending mail to monet@crm.mot.com. Unsubscribe by sending mail to
monet-request@crm.mot.com with the two
words "unsubscribe monet" (again without the quotes) in the body.

Cheers,
Hong-Yon Lach
Alexandru Petrescu
Christophe Janneteau
John Boot



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


From seamoby-admin@ietf.org  Mon Dec 17 13:08:20 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13775
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 13:08:20 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13242;
	Mon, 17 Dec 2001 12:54:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13213
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 12:54:47 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13393
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 12:54:45 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBHHs4J08736;
	Mon, 17 Dec 2001 09:54:04 -0800 (PST)
Message-ID: <005c01c18723$97c74a70$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>, <seamoby@ietf.org>
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com>
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC
Date: Mon, 17 Dec 2001 09:52:28 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Bechet,

The Wireless Directorate is still discussing what to do about L2
triggers. Based on feedback from
the Directorate, I made a decision not to pursue discussing a joint
draft on paging and handover triggers
with the other authors of the handover trigger draft. There has been no
decision about how
to continue the L2 triggers work in the Wireless Directorate yet, but
many people have expressed
the opinion that a BOF at IETF 53 is the right approach. If that
approach appeals to the
Area Directors, then you will have the opportunity to present your work
there, as will we with the
handover triggers.

As for your HMIPv6-based paging work, again as I mentioned at the
meeting,
the proposal was dependent on a specific LMM solution for MIPv6. Given
that
the MIP group has yet to decide on LMM requirements, I am actually quite
suprised that your team even submitted it. I don't think there is any
way the
Seamoby group could possibly accept a protocol proposal based on
a protocol that has yet to even complete the requirements phase in
another
working group, to say nothing of the dependence on Mobile IPv6, which
is something the Seamoby working group has tried to avoid. The
HMIPv6-based
paging proposal not only didn't satisfy the requirements, but it set up
a dependence
that could ultimately hamper taking the Seamoby protocol to proposed
standard, if
the Mobile IP group rejected HMIPv6 in favor of another LMM protocol.

With regard to the paging assessment, if you look at
draft-ietf-seamoby-paging-protocol-assessment-00.txt, you will see that
there is a separate
column for rating draft-guri-seamoby-lahap-00.txt, and a separate set of
comments. So, even
though both drafts were done by the same assessor (which is what I meant
by them
being bundled), the assessments were written up separately. However,
since
draft-guri-seamoby-lahap-00.txt does not present a complete solution for
IP paging, it was not possible to consider it on its own as the solution
for the Seamoby
IP paging protocol. That's another and perhaps more compelling reason
why it was not
accepted as the basis for the Seamoby protocol. I should have made this
clearer at the meeting.

As you may know, working group drafts are the product of the working
group, not
the editor, so your work, along with good work from the other protocol
proposal
authors, will be invaluable in generating a superior result. Rather than
"declaring the
assessment moot", I suggest you talk to Marco about folding some of your
work
into the working group draft, if that seems appropriate.  If not, then
perhaps
the venue of an L2 trigger BOF would be the right place to continue
the work. We will certainly need a good interface between IP paging and
Layer 2
paging in the final Seamoby paging protocol.

                    jak

----- Original Message -----
From: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
To: <seamoby@ietf.org>
Sent: Saturday, December 15, 2001 3:23 PM
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC


> Dear All,
>   According to the slides presented by WG cochair on Friday Dec. 14,
> 2001 at IETF 52 (these slides have to be posted for public access, as
> other WGs do), the two drafts:
> draft 1. draft-sarikaya-seamoby-mipv6hp-00.txt and
> draft 2. draft-guri-seamoby-lahap-00.txt
> were considered together because they were submitted by the same team
and
> since draft-sarikaya-seamoby-mipv6hp-00.txt
> was based on hmipv6 both of them were eliminated, i.e.
> draft-guri-seamoby-lahap-00.txt was not at all considered, there were
no
> slides on this draft..
>   This raises several concerns on my side:
> - the two drafts have only two authors in common, the two draft main
> authors are different and
> more importantly the two drafts define two different paging protocols.
> - draft 1 is an extension of Mobile IPv6. Its dependence on hmipv6 can
> easily be removed, as we intend to do it in the next version.
> - draft 2 is completely based on the architecture defined in RFC 3154.
> Apart from many other aspects, it defines paging triggers.
> - draft 2 was probably the only draft that generated some discussion
on
> the maling list by people who have not submitted drafts, i.e., by
> external people .
> - WG cochair Jim sent us private emails providing some useful feedback
> on the definition of an API for paging triggers. He even offered to
> collaborate on a joint draft. I have the emails and willing to
> distribute them on the mailing list if asked.
>
>   Based on the above facts I hereby declare the paging protocol
> assessment to be moot.
>
> Regards,
>
> --
> Behcet
>
>
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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


From seamoby-admin@ietf.org  Mon Dec 17 13:13:12 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13894
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 13:13:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13713;
	Mon, 17 Dec 2001 13:00:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13667
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 13:00:29 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13572
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 13:00:27 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBHHxsJ08995;
	Mon, 17 Dec 2001 09:59:55 -0800 (PST)
Message-ID: <007401c18724$68b50230$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Hesham Soliman \(ERA\)" <hesham.soliman@era.ericsson.se>,
        "'Behcet Sarikaya'" <behcet.sarikaya@alcatel.com>, <seamoby@ietf.org>
References: <4DA6EA82906FD511BE2F00508BCF053801C4C131@Esealnt861.al.sw.ericsson.se>
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC
Date: Mon, 17 Dec 2001 09:58:18 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hesham,

The Mobile IP group has yet to complete requirements for LMM, much less
select a protocol. Should the Mobile
IP group decide ultimately to select an LMM solution other than HMIPv6,
it would make taking a Seamoby protocol
based on HMIPv6 to proposed standard much more difficult. In addition,
one of the primary requirements behind
all Seamoby protocols is independence of mobility protocol. A paging
protocol explicitly based on Mobile IP,
and Mobile IPv6 specifically, therefore does not satisfy this
requirment.

            jak

----- Original Message -----
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'Behcet Sarikaya'" <behcet.sarikaya@alcatel.com>;
<seamoby@ietf.org>
Sent: Monday, December 17, 2001 2:25 AM
Subject: RE: [Seamoby] Paging Protocol Assessment Presentation at SLC


>   > access, as
>   > other WGs do), the two drafts:
>   > draft 1. draft-sarikaya-seamoby-mipv6hp-00.txt and
>   > draft 2. draft-guri-seamoby-lahap-00.txt
>   > were considered together because they were submitted by the
>   > same team and
>   > since draft-sarikaya-seamoby-mipv6hp-00.txt
>   > was based on hmipv6 both of them were eliminated,
>
> => I missed the early part of the meeting, but
> was that a reason ?? ie, just because it's based on HMIPv6 ?
>
> Hesham
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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


From seamoby-admin@ietf.org  Mon Dec 17 13:28:08 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14263
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 13:28:08 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14143;
	Mon, 17 Dec 2001 13:16:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14116
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 13:16:44 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14027
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 13:16:41 -0500 (EST)
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 MAA06758;
	Mon, 17 Dec 2001 12:16:13 -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 fBHIGDm20064;
	Mon, 17 Dec 2001 12:16:13 -0600 (CST)
Message-ID: <3C1E373E.EC319C74@alcatel.com>
Date: Mon, 17 Dec 2001 12:19:42 -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: James Kempf <kempf@docomolabs-usa.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com> <005c01c18723$97c74a70$7e6015ac@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Jim,
  Are you going to post or not the slides you presented at SLC?


James Kempf wrote:

>
> With regard to the paging assessment, if you look at
> draft-ietf-seamoby-paging-protocol-assessment-00.txt, you will see that
> there is a separate
> column for rating draft-guri-seamoby-lahap-00.txt, and a separate set of
> comments. So, even
> though both drafts were done by the same assessor (which is what I meant
> by them
> being bundled), the assessments were written up separately. However,
> since
> draft-guri-seamoby-lahap-00.txt does not present a complete solution for
> IP paging,

Sorry I do not get this argument.
The assessment draft gave marks to all drafts and the marks
draft-guri-seamoby-lahap-00.txt received were not less than the marks others
received if not more.
It was your final personal decision presented in the drafts that made
comments on specifics of each draft. There, unfortunately were no slides,
i.e. no assessment of draft-guri-seamoby-lahap-00.txt and it said that the
decision on this draft was based on draft-sarikaya-seamoby-mipv6hp-00.txt.

This was the main point of my previous mail.
Good to remind.  Let's come to the point. Shall we?

--
Behcet


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


From seamoby-admin@ietf.org  Mon Dec 17 13:43:37 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14601
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 13:43:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14678;
	Mon, 17 Dec 2001 13:30:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14643
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 13:30:32 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14309
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 13:30:29 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBHIU0J10273;
	Mon, 17 Dec 2001 10:30:00 -0800 (PST)
Message-ID: <00f801c18728$9cb16e80$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
Cc: <seamoby@ietf.org>
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com> <005c01c18723$97c74a70$7e6015ac@T23KEMPF> <3C1E373E.EC319C74@alcatel.com>
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC
Date: Mon, 17 Dec 2001 10:28:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,

The slides will be part of the record of the meeting, including the
minutes. When that is complete, Pat or I
will announce to the mailing list where to find them. There is no point
in mailing out the bits to everyone.

            jak

----- Original Message -----
From: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <seamoby@ietf.org>
Sent: Monday, December 17, 2001 10:19 AM
Subject: Re: [Seamoby] Paging Protocol Assessment Presentation at SLC


> Jim,
>   Are you going to post or not the slides you presented at SLC?
>
>
> James Kempf wrote:
>
> >
> > With regard to the paging assessment, if you look at
> > draft-ietf-seamoby-paging-protocol-assessment-00.txt, you will see
that
> > there is a separate
> > column for rating draft-guri-seamoby-lahap-00.txt, and a separate
set of
> > comments. So, even
> > though both drafts were done by the same assessor (which is what I
meant
> > by them
> > being bundled), the assessments were written up separately. However,
> > since
> > draft-guri-seamoby-lahap-00.txt does not present a complete solution
for
> > IP paging,
>
> Sorry I do not get this argument.
> The assessment draft gave marks to all drafts and the marks
> draft-guri-seamoby-lahap-00.txt received were not less than the marks
others
> received if not more.
> It was your final personal decision presented in the drafts that made
> comments on specifics of each draft. There, unfortunately were no
slides,
> i.e. no assessment of draft-guri-seamoby-lahap-00.txt and it said that
the
> decision on this draft was based on
draft-sarikaya-seamoby-mipv6hp-00.txt.
>
> This was the main point of my previous mail.
> Good to remind.  Let's come to the point. Shall we?
>
> --
> Behcet
>
>


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


From seamoby-admin@ietf.org  Mon Dec 17 16:02:52 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18193
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 16:02:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA18651;
	Mon, 17 Dec 2001 15:51:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA18622
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 15:51:25 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17918
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 15:51:21 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA18088;
	Mon, 17 Dec 2001 14:50:41 -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 fBHKlir24452;
	Mon, 17 Dec 2001 14:47:45 -0600 (CST)
Message-ID: <3C1E5AC1.2FE98AD1@alcatel.com>
Date: Mon, 17 Dec 2001 14:51:13 -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: James Kempf <kempf@docomolabs-usa.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Paging Triggers
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com> <005c01c18723$97c74a70$7e6015ac@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hi Jim,
  I am afraid your comments on paging triggers could be misunderstood as if
Seamoby WG chairs are against defining paging triggers.
  You know what Raj Patil (MIP WG) said in a recent mail:
>L2 triggers will not be discussed in the MIP WG meeting at SLC. While we
>do
>realize the importance of L2 triggers in enabling low-latency (MIPv4)
>and fast
>handoff (MIPv6), it is still undetermined as to in what WG or area of
>the IETF
>to do work related to this.
which I interpret as saying that MIP WG is supportive of  trigger work.
  If you are against I have a feeling that you have to make your case why
you are for defining triggers for low latency and fast handoff and not for
paging.

Regards,

James Kempf wrote:

> Bechet,
>
> The Wireless Directorate is still discussing what to do about L2
> triggers. Based on feedback from
> the Directorate, I made a decision not to pursue discussing a joint
> draft on paging and handover triggers
> with the other authors of the handover trigger draft. There has been no
> decision about how
> to continue the L2 triggers work in the Wireless Directorate yet, but
> many people have expressed
> the opinion that a BOF at IETF 53 is the right approach. If that
> approach appeals to the
> Area Directors, then you will have the opportunity to present your work
> there, as will we with the
> handover triggers.

--
Behcet


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


From seamoby-admin@ietf.org  Mon Dec 17 16:23:31 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18716
	for <seamoby-archive@odin.ietf.org>; Mon, 17 Dec 2001 16:23:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19240;
	Mon, 17 Dec 2001 16:11:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19213
	for <seamoby@ns.ietf.org>; Mon, 17 Dec 2001 16:11:42 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18387
	for <seamoby@ietf.org>; Mon, 17 Dec 2001 16:11:37 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBHLBAJ17777;
	Mon, 17 Dec 2001 13:11:10 -0800 (PST)
Message-ID: <01f001c1873f$20248c00$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
Cc: <seamoby@ietf.org>
References: <DC6C13921CCAFB49BCB8461164A3F4E38D216B@EXCHSRV.stormventures.com> <3C1BDB8B.4020101@alcatel.com> <005c01c18723$97c74a70$7e6015ac@T23KEMPF> <3C1E5AC1.2FE98AD1@alcatel.com>
Subject: Re: [Seamoby] Paging Triggers
Date: Mon, 17 Dec 2001 13:09:33 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,

>   I am afraid your comments on paging triggers could be misunderstood
as if
> Seamoby WG chairs are against defining paging triggers.
>   You know what Raj Patil (MIP WG) said in a recent mail:
> >L2 triggers will not be discussed in the MIP WG meeting at SLC. While
we
> >do
> >realize the importance of L2 triggers in enabling low-latency (MIPv4)
> >and fast
> >handoff (MIPv6), it is still undetermined as to in what WG or area of
> >the IETF
> >to do work related to this.
> which I interpret as saying that MIP WG is supportive of  trigger
work.
>   If you are against I have a feeling that you have to make your case
why
> you are for defining triggers for low latency and fast handoff and not
for
> paging.
>

As Raj says for MIP and handover triggers, I believe the L2 triggers for
paging work has
some promise and is worthy of further investigation. However, we need
to define the right context within IETF for the work. Hopefully,
we will get this straightened out shortly.

            jak


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


From seamoby-admin@ietf.org  Tue Dec 18 11:23:15 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20958
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 11:23:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27138;
	Tue, 18 Dec 2001 11:01:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27109
	for <seamoby@ns.ietf.org>; Tue, 18 Dec 2001 11:01:43 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20462
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 11:01:38 -0500 (EST)
Received: from haskins.ee.surrey.ac.uk ([131.227.89.14] ident=exim)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.16 #1)
	id 16GMgR-0007TJ-00
	for seamoby@ietf.org; Tue, 18 Dec 2001 16:01:35 +0000
Received: from eep2kc (helo=localhost)
	by haskins.ee.surrey.ac.uk with local-esmtp (Exim 2.12 #5)
	id 16GMgQ-0002yJ-00
	for seamoby@ietf.org; Tue, 18 Dec 2001 16:01:34 +0000
Date: Tue, 18 Dec 2001 16:01:34 +0000 (GMT)
From: Kar Ann Chew <k.chew@eim.surrey.ac.uk>
X-X-Sender: eep2kc@haskins.ee.surrey.ac.uk
To: seamoby@ietf.org
Message-ID: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanner: exiscan *16GMgR-0007TJ-00*zte6tOiJ.sI* (SECM, UniS)
Subject: [Seamoby] Defining Paging Area
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org


Hi,
A simple question - How should Paging Areas be defined in IP network?

Most of the paging proposals mention how to detect change of PA, and
procedure of updating related entities, but not on how a PA is defined?.

Anyone, any pointers/advice on how to make paging area definition?  Or we
can simply leave is to cell planning people?

Cheers,
	Karann
++++++++++++++++++++++++++++++++++++++++++
Karann Chew
Mobile Communications Research Group
Centre for Communication Systems Research
University of Surrey, Guildford
Surrey GU2 7XH, United Kingdom
Tel: +44 (0) 1483-876001
Fax: +44 (0) 1483-876011
++++++++++++++++++++++++++++++++++++++++++


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


From seamoby-admin@ietf.org  Tue Dec 18 12:02:31 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21939
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 12:02:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28401;
	Tue, 18 Dec 2001 11:45:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28374
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 11:45:22 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21477
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 11:45:17 -0500 (EST)
Received: from inrialpes.fr (lalena.inrialpes.fr [194.199.24.114])
	by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBIGjDP13657;
	Tue, 18 Dec 2001 17:45:13 +0100 (MET)
Message-ID: <3C1F72F3.55010169@inrialpes.fr>
Date: Tue, 18 Dec 2001 17:46:43 +0100
From: Pars MUTAF <pars.mutaf@inrialpes.fr>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Kar Ann Chew <k.chew@eim.surrey.ac.uk>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit


Hello!


Kar Ann Chew wrote:

> Hi,
> A simple question - How should Paging Areas be defined in IP network?
>
> Most of the paging proposals mention how to detect change of PA, and
> procedure of updating related entities, but not on how a PA is defined?.

> Anyone, any pointers/advice on how to make paging area definition?

Our draft on DPAC (Dynamic Paging Area Configuration) might
interest you.

It is available at:
http://www.inrialpes.fr/planete/people/mutaf/draft-mutaf-dpac-00.txt

We will update it soon. Please do not hesistate to comment on it.




> Or we
> can simply leave is to cell planning people?
>

This is also possible.

But, after years of (others') cellular experience, manual paging area
configuration has proven difficult and not efficient "at all".  Now,
with IP paging, we have the chance to change that.

Hence the motivation for paging area auto-configuration in
RFC3154.




Regards,
pars




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


From seamoby-admin@ietf.org  Tue Dec 18 12:17:22 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22231
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 12:17:20 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28803;
	Tue, 18 Dec 2001 11:55:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28765
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 11:55:47 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21798
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 11:55:42 -0500 (EST)
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 fBIGtXQ21650;
	Tue, 18 Dec 2001 11:55:33 -0500
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
To: "'Pars MUTAF'" <pars.mutaf@inrialpes.fr>,
        "'Kar Ann Chew'" <k.chew@eim.surrey.ac.uk>
Cc: <seamoby@ietf.org>, "Xiaowei Zhang \(E-mail\)" <xzhang@comet.columbia.edu>,
        "Javier Gomez-Castellanos \(E-mail\)" <javierg@comet.columbia.edu>,
        "Andrew Campbell \(E-mail\)" <campbell@comet.columbia.edu>
Subject: RE: [Seamoby] Defining Paging Area
Date: Tue, 18 Dec 2001 11:52:31 -0500
Message-ID: <00aa01c187e4$62fa2b20$ca413b80@SWEETPEA>
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 CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3C1F72F3.55010169@inrialpes.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit


Hello Kar:

Following on Pars' note on IP paging, we developed the P-MIP 
protocol. While the P-MIP Internet Draft did not go into setting
up paging areas the following paper does. The 
approach discussed there contrast the work
from the INRIA team, which I like too. 

You can find the paper:

"Design and Performance of Mobile IP Paging," X. Zhang, J. 
Castellanos, and A. Campbell, ACM/Kluwer Mobile Networks 
and Applications (MONET), Special issue on Modeling Analysis 
and Simulation of Wireless and Mobile Systems, Vol 7, No. 2, 
March 2002 (to be published),

on the P-MIP page:

http://www.comet.columbia.edu/pmip/

The ns-2 source code is available there too. 

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


> -----Original Message-----
> From: seamoby-admin@ietf.org 
> [mailto:seamoby-admin@ietf.org]On Behalf Of
> Pars MUTAF
> Sent: Tuesday, December 18, 2001 11:47 AM
> To: Kar Ann Chew
> Cc: seamoby@ietf.org
> Subject: Re: [Seamoby] Defining Paging Area
> 
> 
> 
> Hello!
> 
> 
> Kar Ann Chew wrote:
> 
> > Hi,
> > A simple question - How should Paging Areas be defined in 
> IP network?
> >
> > Most of the paging proposals mention how to detect change of PA, and
> > procedure of updating related entities, but not on how a PA 
> is defined?.
> 
> > Anyone, any pointers/advice on how to make paging area definition?
> 
> Our draft on DPAC (Dynamic Paging Area Configuration) might
> interest you.
> 
> It is available at:
> http://www.inrialpes.fr/planete/people/mutaf/draft-mutaf-dpac-00.txt
> 
> We will update it soon. Please do not hesistate to comment on it.
> 
> 
> 
> 
> > Or we
> > can simply leave is to cell planning people?
> >
> 
> This is also possible.
> 
> But, after years of (others') cellular experience, manual paging area
> configuration has proven difficult and not efficient "at all".  Now,
> with IP paging, we have the chance to change that.
> 
> Hence the motivation for paging area auto-configuration in
> RFC3154.
> 
> 
> 
> 
> Regards,
> pars
> 
> 
> 
> 
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

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


From seamoby-admin@ietf.org  Tue Dec 18 12:37:51 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22599
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 12:37:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00238;
	Tue, 18 Dec 2001 12:22:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00207
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 12:22:01 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22300
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 12:21:55 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace [192.168.102.1])
	by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id fBIHLSA51390;
	Tue, 18 Dec 2001 18:21:28 +0100 (CET)
Received: from ccrle.nec.de (zipo.heidelberg.ccrle.nec.de [192.168.102.84])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA01736;
	Tue, 18 Dec 2001 18:21:36 +0100
Message-ID: <3C1F7B20.61FA6C15@ccrle.nec.de>
Date: Tue, 18 Dec 2001 18:21:36 +0100
From: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kar Ann Chew <k.chew@eim.surrey.ac.uk>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hi,
in addition to the feedback already sent to the list, please be referred to
draft-renker-paging-ipv6-01.txt as well, which has some sections on L3 Paging
Areas and also appropriate references to the respective documents/papers.
Hope this helps.

Marco

Kar Ann Chew wrote:

> Hi,
> A simple question - How should Paging Areas be defined in IP network?
>
> Most of the paging proposals mention how to detect change of PA, and
> procedure of updating related entities, but not on how a PA is defined?.
>
> Anyone, any pointers/advice on how to make paging area definition?  Or we
> can simply leave is to cell planning people?
>
> Cheers,
>         Karann
> ++++++++++++++++++++++++++++++++++++++++++
> Karann Chew
> Mobile Communications Research Group
> Centre for Communication Systems Research
> University of Surrey, Guildford
> Surrey GU2 7XH, United Kingdom
> Tel: +44 (0) 1483-876001
> Fax: +44 (0) 1483-876011
> ++++++++++++++++++++++++++++++++++++++++++
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby





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


From seamoby-admin@ietf.org  Tue Dec 18 12:38:26 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22611
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 12:38:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29991;
	Tue, 18 Dec 2001 12:14:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29951
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 12:14:03 -0500 (EST)
Received: from phoebe.eim.surrey.ac.uk (IDENT:exim@phoebe.eim.surrey.ac.uk [131.227.74.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22181
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 12:13:57 -0500 (EST)
Received: from haskins.ee.surrey.ac.uk ([131.227.89.14] ident=exim)
	by phoebe.eim.surrey.ac.uk with esmtp (Exim 3.16 #1)
	id 16GNoV-0004Ox-00; Tue, 18 Dec 2001 17:13:59 +0000
Received: from eep2kc (helo=localhost)
	by haskins.ee.surrey.ac.uk with local-esmtp (Exim 2.12 #5)
	id 16GNoM-0003Bh-00; Tue, 18 Dec 2001 17:13:50 +0000
Date: Tue, 18 Dec 2001 17:13:50 +0000 (GMT)
From: Karann Chew <k.chew@eim.surrey.ac.uk>
X-X-Sender: eep2kc@haskins.ee.surrey.ac.uk
To: Sridhar Gurivireddy <Sridhar.Gurivireddy@usa.alcatel.com>
cc: seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
In-Reply-To: <3C1F7642.41A0A5B@usa.alcatel.com>
Message-ID: <Pine.SOL.4.43.0112181706430.5355-100000@haskins.ee.surrey.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanner: exiscan *16GNoV-0004Ox-00*zDUcx8ilMSw* (SECM, UniS)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org


Thanks Guri.

> Layer 2 paging area is something which is defined by access technology.
> Usually, it's a collection of access points(in 4G) under the same SGSN or
> under the same GGSN.
> So, if a layer 2 registration is required for every change in SGSN, then area
> covered by SGSN is layer 2 paging area.

I understand those related to cellular (2.5g 3g etc) network, where
network architecture is well defined.  ie. crossing SGSN, do a inter-SGSN
routing area update (something like paging update), crossing Routing Area,
do a intra-sgsn  update, etc.

What I would like to find out is that, how we define the paging area in
IP, in general, where the network topology can be aribitary.

> You can define your own layer 3 paging areas..{ A IP paging protocol can define
> it...}

So, I'll take the answer as "You can define however you like if you can
justify it, b'cos there's no standard at the moment".  Is that right?

Thanks everyone for pointer.  I've read some of them, and will read the
rest that I haven't came across.

Cheers,
	Karann




>
> Karann Chew wrote:
>
> > Hi,
> >
> > > Layer 2 paging area is the area in which a MN can move in the access network
> > > without making any network updates.(Known as routing area in GSM)
> >
> > > Layer 3 paging area is the area in which MN can move (possibly across multple
> > > L2 paging areas) without making any additional paging IP
> > registrations(of Mobile IP).{ A
> > > concept, applicable to 3G and 4G
> > > networks, MN's IP address can change due to change in the IP subnet }
> >
> > Yes, I understand that.  Let me make my question clearer - suppose I have
> > 100s of access point laid in a city, and want to group them into different
> > PA, how do I  do that?  How do I define the PA among them?  Based on
> > traffic analysis?  Cell coverage?  Or any IP-specific mechanism?
> >
> > By the way, may I have a copy of your draft please?
> >
> > Cheers,
> >         Karann
> >
> > > You can read my Internet Draft on aprotocol for IP paging
> > > Link aided host alerting protocol
> > >
> > > Hope this helps,
> > > Sridhar Gurivireddy.
> > >
> > >
> > >
> > >
> > > Kar Ann Chew wrote:
> > >
> > > > Hi,
> > > > A simple question - How should Paging Areas be defined in IP network?
> > > >
> > > > Most of the paging proposals mention how to detect change of PA, and
> > > > procedure of updating related entities, but not on how a PA is defined?.
> > > >
> > > > Anyone, any pointers/advice on how to make paging area definition?  Or we
> > > > can simply leave is to cell planning people?
> > > >
> > > > Cheers,
> > > >         Karann
> > > > ++++++++++++++++++++++++++++++++++++++++++
> > > > Karann Chew
> > > > Mobile Communications Research Group
> > > > Centre for Communication Systems Research
> > > > University of Surrey, Guildford
> > > > Surrey GU2 7XH, United Kingdom
> > > > Tel: +44 (0) 1483-876001
> > > > Fax: +44 (0) 1483-876011
> > > > ++++++++++++++++++++++++++++++++++++++++++
> > > >
> > > > _______________________________________________
> > > > Seamoby mailing list
> > > > Seamoby@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/seamoby
> > >
> > > --
> > > Sridhar Guriviredddy,
> > > Mobile IP & 3GPP2 case
> > > Network Strategic Group,
> > > Alcatel, Richardson, TX-75080
> > >
> > > Ph:  972.996.2048 (o) 972.897.7025(M) 972.671.7437(H)
> > >
> > >
> > >
>
> --
> Sridhar Guriviredddy,
> Mobile IP & 3GPP2 case
> Network Strategic Group,
> Alcatel, Richardson, TX-75080
>
> Ph:  972.996.2048 (o) 972.897.7025(M) 972.671.7437(H)
>
>
>


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


From seamoby-admin@ietf.org  Tue Dec 18 13:02:32 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23049
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 13:02:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01160;
	Tue, 18 Dec 2001 12:48:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01131
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 12:48:15 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22849
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 12:48:11 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBIHl9825088;
	Tue, 18 Dec 2001 09:47:09 -0800 (PST)
Message-ID: <00af01c187eb$cac66af0$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>, <seamoby@ietf.org>
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
Subject: Re: [Seamoby] Defining Paging Area
Date: Tue, 18 Dec 2001 09:45: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
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Kar Ann,

This is an entirely open question at this point. There is one draft out
there on the issue (draft-mutaf-dpac-00.txt),
but this just one approach, others are possible.

One of the major advantages of IP paging over strictly L2 paging is the
ability to do dynamic paging area configuration.
At some point, it might be useful to look into a protocol for dynamic
paging area configuration, but, for now,
I think it is more important that we get a paging protocol defined. Of
course, any paging area configuration protocol would
need to be independent of the policy used to configure the paging area.

            jak


----- Original Message -----
From: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>
To: <seamoby@ietf.org>
Sent: Tuesday, December 18, 2001 8:01 AM
Subject: [Seamoby] Defining Paging Area


>
> Hi,
> A simple question - How should Paging Areas be defined in IP network?
>
> Most of the paging proposals mention how to detect change of PA, and
> procedure of updating related entities, but not on how a PA is
defined?.
>
> Anyone, any pointers/advice on how to make paging area definition?  Or
we
> can simply leave is to cell planning people?
>
> Cheers,
> Karann
> ++++++++++++++++++++++++++++++++++++++++++
> Karann Chew
> Mobile Communications Research Group
> Centre for Communication Systems Research
> University of Surrey, Guildford
> Surrey GU2 7XH, United Kingdom
> Tel: +44 (0) 1483-876001
> Fax: +44 (0) 1483-876011
> ++++++++++++++++++++++++++++++++++++++++++
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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


From seamoby-admin@ietf.org  Tue Dec 18 20:04:39 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02593
	for <seamoby-archive@odin.ietf.org>; Tue, 18 Dec 2001 20:04:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA14068;
	Tue, 18 Dec 2001 19:45:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA14039
	for <seamoby@optimus.ietf.org>; Tue, 18 Dec 2001 19:45:27 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02201
	for <seamoby@ietf.org>; Tue, 18 Dec 2001 19:45:24 -0500 (EST)
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 SAA11399;
	Tue, 18 Dec 2001 18:44:56 -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 fBJ0iur28248;
	Tue, 18 Dec 2001 18:44:56 -0600 (CST)
Message-ID: <3C1FE3D5.5D9061EA@alcatel.com>
Date: Tue, 18 Dec 2001 18:48:21 -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: Kar Ann Chew <k.chew@eim.surrey.ac.uk>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hi Kar Ann,
  If you read:
draft-sarikaya-seamoby-mipv6hp-00.txt
and
draft-guri-seamoby-lahap-00.txt

you will see defined Layer 2 paging areas (I think that architecture picture
in draft-sarikaya-seamoby-mipv6hp is slightly more informative)
and Layer 3 PAs. L2 PAs are as in 2.5G and 3G cellular networks so mobile
operators define and set up such PAs. There are connected to APs which are L2
entities. They are static.
  As for L3 PAs, we defined them as collections of IP subnets with a Paging
Agent. There is multicast address for each PA and the paging agent can
address each PA by a single request message. This is I think a good design
and it had previously been proposed (I believe in HAWAII). These PAs are also
static.
  What Pars and Claude talk about as PAs I think is a cell level or L1
concept. I am having difficulty in understanding their theory. Hopefully they
will further develop it using L2 or L3 ideas so that we can grasp the theory
of dynamic paging areas. Only thereafter some standardization can be thought
of.

Hope this helps, I do not think that it is all mysterious these PAs. In
general IP paging concepts are much better understood now then before. Don't
they?

Regards,

Kar Ann Chew wrote:

> Hi,
> A simple question - How should Paging Areas be defined in IP network?
>
> Most of the paging proposals mention how to detect change of PA, and
> procedure of updating related entities, but not on how a PA is defined?.
>
> Anyone, any pointers/advice on how to make paging area definition?  Or we
> can simply leave is to cell planning people?
>
> Cheers,
>         Karann
> ++++++++++++++++++++++++++++++++++++++++++
> Karann Chew
> Mobile Communications Research Group
> Centre for Communication Systems Research
> University of Surrey, Guildford
> Surrey GU2 7XH, United Kingdom
> Tel: +44 (0) 1483-876001
> Fax: +44 (0) 1483-876011
> ++++++++++++++++++++++++++++++++++++++++++
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

--
Behcet


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


From seamoby-admin@ietf.org  Wed Dec 19 06:09:17 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26888
	for <seamoby-archive@odin.ietf.org>; Wed, 19 Dec 2001 06:09:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08434;
	Wed, 19 Dec 2001 05:53:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08403
	for <seamoby@optimus.ietf.org>; Wed, 19 Dec 2001 05:53:12 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26718
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 05:53:07 -0500 (EST)
Received: from inrialpes.fr (lalena.inrialpes.fr [194.199.24.114])
	by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBJAqtP03947;
	Wed, 19 Dec 2001 11:52:56 +0100 (MET)
Message-ID: <3C2071E4.7D29DC85@inrialpes.fr>
Date: Wed, 19 Dec 2001 11:54:28 +0100
From: Pars MUTAF <pars.mutaf@inrialpes.fr>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
CC: Kar Ann Chew <k.chew@eim.surrey.ac.uk>, seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <3C1FE3D5.5D9061EA@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit


Hello,


Behcet Sarikaya wrote:

>
>   What Pars and Claude talk about as PAs I think is a cell level or L1
> concept. I am having difficulty in understanding their theory. Hopefully they
> will further develop it using L2 or L3 ideas so that we can grasp the theory
> of dynamic paging areas. Only thereafter some standardization can be thought
> of.

Thank you for your comments (but I assume that your "L1" statement
was a joke).

A clarification: DPAC configures L3 paging areas.

Seems like there is an ambiguity in the current version of the DPAC text.
In fact, we should have chosen the term "IP subnet" instead of "cell". We
were thinking about "L3 cells" . An L3 cell comprises one or more L2
cells. An L3 cell is nothing but an IP subnet.

I'll change the text and adopt the same terminology (i.e. IP subnet)
as RFC3132 (IP paging problem statement).

Regards,
pars




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


From seamoby-admin@ietf.org  Wed Dec 19 09:42:33 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28583
	for <seamoby-archive@odin.ietf.org>; Wed, 19 Dec 2001 09:42:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14130;
	Wed, 19 Dec 2001 09:27:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14101
	for <seamoby@optimus.ietf.org>; Wed, 19 Dec 2001 09:27:54 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28400
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 09:27:45 -0500 (EST)
Received: from inrialpes.fr (lalena.inrialpes.fr [194.199.24.114])
	by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBJERUP10020;
	Wed, 19 Dec 2001 15:27:31 +0100 (MET)
Message-ID: <3C20A42F.1002FBC1@inrialpes.fr>
Date: Wed, 19 Dec 2001 15:29:03 +0100
From: Pars MUTAF <pars.mutaf@inrialpes.fr>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
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@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <00af01c187eb$cac66af0$7e6015ac@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit


Hello,

James Kempf wrote:

> Kar Ann,
>
> This is an entirely open question at this point. There is one draft out
> there on the issue (draft-mutaf-dpac-00.txt),
> but this just one approach, others are possible.

I agree that others are possible. We might have a different scheme
in another mobility scenario. I'd like emphasize which scenario our
DPAC is being designed for:

For example,  consider the case where a user moves towards a new
country which is "far far away" from his home town and
"for the first time in his life". This newly visited country might be
"Papua New Guina" for example.

Such big moves are allowed by Mobile IP. Our proposition
guarantees the availability of paging areas to the above user during
his trip. Because paging areas will be already configured using the
samples generated by the inhabitants of Papua. Currently, our
proposition is the "unique" policy (as far as I know) which has this
property. I think this is because there wasn't such a need before
Mobile IP.

But, in another scenario (movements inside a building for
example), one can imagine other policies which might be more
efficient than our proposition (more efficient in terms of paging
area shape, registration rate etc).

One can think of our proposition as a policy mostly suitable for
"public access networks".

From this point of view, it seems like we've monopolized the
term "dynamic paging area configuration" which is in fact
generic. I think we can change the title of our draft if WG
consensus says to do so.


> One of the major advantages of IP paging over strictly L2 paging is the
> ability to do dynamic paging area configuration.

So, if IP paging becomes a real success, this may have a major
influence on the way the L2 engineers and cellular operators think?
I mean, in this case L2 paging areas may disappear in the future?
(the role of L2 being dormant mode support in a given subnet).

What do you think?

(please note that this is just a question, not an argument)

If this is possible, one should think of dynamic paging area
configuration (in its generic sense)  as the key factor in IP paging
protocol design.

Comments? Thanks.

Regards,
pars




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


From seamoby-admin@ietf.org  Wed Dec 19 13:01:00 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02856
	for <seamoby-archive@odin.ietf.org>; Wed, 19 Dec 2001 13:00:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21865;
	Wed, 19 Dec 2001 12:36:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21835
	for <seamoby@optimus.ietf.org>; Wed, 19 Dec 2001 12:36:15 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02294
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 12:36:10 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBJHZ3812589;
	Wed, 19 Dec 2001 09:35:03 -0800 (PST)
Message-ID: <007a01c188b3$450ae530$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Pars MUTAF" <pars.mutaf@inrialpes.fr>
Cc: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>, <seamoby@ietf.org>
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <00af01c187eb$cac66af0$7e6015ac@T23KEMPF> <3C20A42F.1002FBC1@inrialpes.fr>
Subject: Re: [Seamoby] Defining Paging Area
Date: Wed, 19 Dec 2001 09:33: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
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Pars,

> > One of the major advantages of IP paging over strictly L2 paging is
the
> > ability to do dynamic paging area configuration.
>
> So, if IP paging becomes a real success, this may have a major
> influence on the way the L2 engineers and cellular operators think?
> I mean, in this case L2 paging areas may disappear in the future?
> (the role of L2 being dormant mode support in a given subnet).
>

It is hard to tell, of course, but I think there are reasons for having
L2 paging support that are independent of static paging areas.
Having a separate paging channel that can contact the mobile
when it is in dormant mode and a paging area beacon channel
may result in better power efficiency on the mobile, for example.

What I hope will disappear are the static Location Area Identifiers
that are tied to GGSN/PDSN, i.e., to a particular subnet. These
are essentially data paging areas in the 3G standards. Static
subnet to paging area mappings tend to constrain network topology,
since they push for larger leaf subnets. Particularly with micro-
or picocells, flexibility in network design might lead to better
routing efficiency.

There is also the issue of multiple wireless interfaces on a
single device. What if there are 5 wireless interfaces on
a device? Confining the details of handling 5 different
L2 paging protocols to the last hop and letting IP
handle the details in the network seems like the correct
abstraction level, and is the traditional role IP has
played in hiding the details of L2.

            jak




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


From seamoby-admin@ietf.org  Wed Dec 19 13:31:25 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03581
	for <seamoby-archive@odin.ietf.org>; Wed, 19 Dec 2001 13:31:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23376;
	Wed, 19 Dec 2001 13:09:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23343
	for <seamoby@optimus.ietf.org>; Wed, 19 Dec 2001 13:09:24 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03008
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 13:09:21 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA04635
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 10:08:53 -0800 (PST)
X-Delivered-For: <seamoby@ietf.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBJI8qW32647
	for <seamoby@ietf.org>; Wed, 19 Dec 2001 10:08:52 -0800
X-mProtect:  Wed, 19 Dec 2001 10:08:52 -0800 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd4YPSVc; Wed, 19 Dec 2001 10:08:51 PST
Message-ID: <3C20D7B3.8EE2A4CE@iprg.nokia.com>
Date: Wed, 19 Dec 2001 10:08:51 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] dropped mails
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

hi,

mails sent by James Kempf, Behcet Sarikaya and Pars Mustaf 
are being blocked by our mail server. please stop continuing
on that thread. dont press 'reply'. compose a new mail.

Vijay

-------- Original Message --------
Subject: ALERT - An Undeliverable Email Message Was Intended For You!
Date: Wed, 19 Dec 2001 09:36:44 -0800
From: notify@darknet.iprg.nokia.com
To: vijayd@iprg.nokia.com

An Email Message intended for you was undeliverable.
The message: Re: [Seamoby] Defining Paging Area
contained the Exploit: MIME EXPLOIT - multiple CTE flds

The blocked message was sent by: "James Kempf"
<kempf@docomolabs-usa.com>

Message Blocked

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


From seamoby-admin@ietf.org  Thu Dec 20 06:43:40 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05939
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 06:43:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA04070;
	Thu, 20 Dec 2001 06:18:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA04042
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 06:18:53 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05671
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 06:18:49 -0500 (EST)
Received: from inrialpes.fr (glandon.inrialpes.fr [194.199.24.105])
	by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBKBIdP05323;
	Thu, 20 Dec 2001 12:18:39 +0100 (MET)
Message-ID: <3C21C911.CF71E695@inrialpes.fr>
Date: Thu, 20 Dec 2001 12:18:41 +0100
From: Claude Castelluccia <claude.castelluccia@inrialpes.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
CC: Kar Ann Chew <k.chew@eim.surrey.ac.uk>, seamoby@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <3C1FE3D5.5D9061EA@alcatel.com>
Content-Type: multipart/alternative;
 boundary="------------DFF55F12990E238C72DC9A34"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org


--------------DFF55F12990E238C72DC9A34
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Behcet Sarikaya wrote:

>   What Pars and Claude talk about as PAs I think is a cell level or L1
> concept. I am having difficulty in understanding their theory. Hopefully they
> will further develop it using L2 or L3 ideas so that we can grasp the theory
> of dynamic paging areas. Only thereafter some standardization can be thought
> of.

Behcet, all of our work is about L3 paging!
Why would we submit something about L1 or L2 paging area
configuration to Seamoby????
I am really surprised about your statement...

Claude.

--

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes
ph:  +33 4.76.61.52.15 (fax: 52.52)
http://www.inrialpes.fr/planete/



--------------DFF55F12990E238C72DC9A34
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Behcet Sarikaya wrote:
<blockquote TYPE=CITE>&nbsp; What Pars and Claude talk about as PAs I think
is a cell level or L1
<br>concept. I am having difficulty in understanding their theory. Hopefully
they
<br>will further develop it using L2 or L3 ideas so that we can grasp the
theory
<br>of dynamic paging areas. Only thereafter some standardization can be
thought
<br>of.</blockquote>
Behcet, all of our work is about L3 paging!
<br>Why would we submit something about L1 or L2 paging area
<br>configuration to Seamoby????
<br>I am really surprised about your statement...
<p>Claude.
<pre>--&nbsp;

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes&nbsp;&nbsp;
ph:&nbsp; +33 4.76.61.52.15 (fax: 52.52)
<A HREF="http://www.inrialpes.fr/planete/">http://www.inrialpes.fr/planete/</A></pre>
&nbsp;</html>

--------------DFF55F12990E238C72DC9A34--


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


From seamoby-admin@ietf.org  Thu Dec 20 06:43:40 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05950
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 06:43:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03852;
	Thu, 20 Dec 2001 06:14:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03824
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 06:14:41 -0500 (EST)
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05616
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 06:14:37 -0500 (EST)
Received: from inrialpes.fr (glandon.inrialpes.fr [194.199.24.105])
	by ebene.inrialpes.fr (8.11.6/8.11.6) with ESMTP id fBKBESP05201;
	Thu, 20 Dec 2001 12:14:29 +0100 (MET)
Message-ID: <3C21C815.5EC0A78@inrialpes.fr>
Date: Thu, 20 Dec 2001 12:14:29 +0100
From: Claude Castelluccia <claude.castelluccia@inrialpes.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
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@ietf.org
Subject: Re: [Seamoby] Defining Paging Area
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <00af01c187eb$cac66af0$7e6015ac@T23KEMPF>
Content-Type: multipart/alternative;
 boundary="------------D98F0B79AF34CF2D76ED3CE7"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org


--------------D98F0B79AF34CF2D76ED3CE7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hello James,

James Kempf wrote:

> Kar Ann,
>
> This is an entirely open question at this point. There is one draft out
> there on the issue (draft-mutaf-dpac-00.txt),
> but this just one approach, others are possible.
>
> One of the major advantages of IP paging over strictly L2 paging is the
> ability to do dynamic paging area configuration.

i agree but not only dynamic paging area configuration but also *per-host*
paging
area (i.e. IP provides the abilitity to customize the PA to each mobile
hosts' particular
communication and mobility pattern...

As you mentioned DPAC is only one approach but we are also working
on an architecture that is, i think, more general. This architecture is
described in
an upcoming SIGCOMM CCR issue and can be dowload at :
http://www.inrialpes.fr/planete/people/ccastel/sigcomm.ps

The WG comments on this paper would be very useful...

> At some point, it might be useful to look into a protocol for dynamic
> paging area configuration, but, for now,
> I think it is more important that we get a paging protocol defined. Of
> course, any paging area configuration protocol would
> need to be independent of the policy used to configure the paging area.
>

I agree , we need to make sure that any IP paging protocols that will be
standardized
can efficiently support Dynamic PA....but this is a very difficult task
without considering
Dynamic PA (and its requirements) from the start   (a bit like security and
MIPv6 ;-))

regards,
Claude.

>
>             jak
>
> ----- Original Message -----
> From: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>
> To: <seamoby@ietf.org>
> Sent: Tuesday, December 18, 2001 8:01 AM
> Subject: [Seamoby] Defining Paging Area
>
> >
> > Hi,
> > A simple question - How should Paging Areas be defined in IP network?
> >
> > Most of the paging proposals mention how to detect change of PA, and
> > procedure of updating related entities, but not on how a PA is
> defined?.
> >
> > Anyone, any pointers/advice on how to make paging area definition?  Or
> we
> > can simply leave is to cell planning people?
> >
> > Cheers,
> > Karann
> > ++++++++++++++++++++++++++++++++++++++++++
> > Karann Chew
> > Mobile Communications Research Group
> > Centre for Communication Systems Research
> > University of Surrey, Guildford
> > Surrey GU2 7XH, United Kingdom
> > Tel: +44 (0) 1483-876001
> > Fax: +44 (0) 1483-876011
> > ++++++++++++++++++++++++++++++++++++++++++
> >
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
> >
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

--

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes
ph:  +33 4.76.61.52.15 (fax: 52.52)
http://www.inrialpes.fr/planete/



--------------D98F0B79AF34CF2D76ED3CE7
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Hello James,
<p>James Kempf wrote:
<blockquote TYPE=CITE>Kar Ann,
<p>This is an entirely open question at this point. There is one draft
out
<br>there on the issue (draft-mutaf-dpac-00.txt),
<br>but this just one approach, others are possible.
<p>One of the major advantages of IP paging over strictly L2 paging is
the
<br>ability to do dynamic paging area configuration.</blockquote>
i agree but not only dynamic paging area configuration but also *per-host*
paging
<br>area (i.e. IP provides the abilitity to customize the PA&nbsp;to each
mobile hosts' particular
<br>communication and mobility pattern...
<p>As you mentioned DPAC&nbsp;is only one approach but we are also working
<br>on an architecture that is, i think, more general. This architecture
is described in
<br>an upcoming SIGCOMM&nbsp;CCR&nbsp;issue and can be dowload at :
<br><A HREF="http://www.inrialpes.fr/planete/people/ccastel/sigcomm.ps">http://www.inrialpes.fr/planete/people/ccastel/sigcomm.ps</A>
<p>The WG&nbsp;comments on this paper would be very useful...
<blockquote TYPE=CITE>At some point, it might be useful to look into a
protocol for dynamic
<br>paging area configuration, but, for now,
<br>I think it is more important that we get a paging protocol defined.
Of
<br>course, any paging area configuration protocol would
<br>need to be independent of the policy used to configure the paging area.
<br>&nbsp;</blockquote>
I agree , we need to make sure that any IP&nbsp;paging protocols that will
be standardized
<br>can efficiently support Dynamic PA....but this is a very difficult
task without considering
<br>Dynamic PA&nbsp;(and its requirements)&nbsp;from the start&nbsp;&nbsp;
(a bit like security and MIPv6 ;-))
<p>regards,
<br>Claude.
<blockquote TYPE=CITE>&nbsp;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
jak
<p>----- Original Message -----
<br>From: "Kar Ann Chew" &lt;k.chew@eim.surrey.ac.uk>
<br>To: &lt;seamoby@ietf.org>
<br>Sent: Tuesday, December 18, 2001 8:01 AM
<br>Subject: [Seamoby] Defining Paging Area
<p>>
<br>> Hi,
<br>> A simple question - How should Paging Areas be defined in IP network?
<br>>
<br>> Most of the paging proposals mention how to detect change of PA,
and
<br>> procedure of updating related entities, but not on how a PA is
<br>defined?.
<br>>
<br>> Anyone, any pointers/advice on how to make paging area definition?&nbsp;
Or
<br>we
<br>> can simply leave is to cell planning people?
<br>>
<br>> Cheers,
<br>> Karann
<br>> ++++++++++++++++++++++++++++++++++++++++++
<br>> Karann Chew
<br>> Mobile Communications Research Group
<br>> Centre for Communication Systems Research
<br>> University of Surrey, Guildford
<br>> Surrey GU2 7XH, United Kingdom
<br>> Tel: +44 (0) 1483-876001
<br>> Fax: +44 (0) 1483-876011
<br>> ++++++++++++++++++++++++++++++++++++++++++
<br>>
<br>>
<br>> _______________________________________________
<br>> Seamoby mailing list
<br>> Seamoby@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/seamoby">https://www1.ietf.org/mailman/listinfo/seamoby</a>
<br>>
<p>_______________________________________________
<br>Seamoby mailing list
<br>Seamoby@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/seamoby">https://www1.ietf.org/mailman/listinfo/seamoby</a></blockquote>

<pre>--&nbsp;

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes&nbsp;&nbsp;
ph:&nbsp; +33 4.76.61.52.15 (fax: 52.52)
<A HREF="http://www.inrialpes.fr/planete/">http://www.inrialpes.fr/planete/</A></pre>
&nbsp;</html>

--------------D98F0B79AF34CF2D76ED3CE7--


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


From seamoby-admin@ietf.org  Thu Dec 20 10:38:58 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09710
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 10:38:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12989;
	Thu, 20 Dec 2001 10:11:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12958
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 10:11:19 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08589
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 10:11:16 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace [192.168.102.1])
	by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id fBKFAqA00545
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 16:10:52 +0100 (CET)
Received: from ccrle.nec.de (zipo.heidelberg.ccrle.nec.de [192.168.102.84])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA26445
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 16:11:00 +0100
Message-ID: <3C21FF83.907EF43C@ccrle.nec.de>
Date: Thu, 20 Dec 2001 16:10:59 +0100
From: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Seamoby <seamoby@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] proposal on next steps in paging
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dear all,

in order to proceed with DMHA protocol specification, I propose the
following:
Since the current base-line document is maybe a bit overloaded for being
the first Seamoby WG draft, I will take out the Mobile IPv6 specific
options out of the main part, but keep the generic explicit signaling in
the document. Mobile IPv6 specific optimization could be kept in the
documents annex or in a separate document (what do you think?).
Furthermore, my opinion is that the concept should allow deployment of
several paging strategies, as currently described in the draft. But
maybe it is reasonable to extract the sections on paging strategies out
of the current draft keeping them in a separate document, which could be
further evaluated and extended. This would allow to get a first
framework draft, which is clearly arranged and open for further
specification of open issues.
What about the following:
Coming up with a first famework draft end of January, possibly having
some further ideas and issues already addressed by then. Then we have
about one month in order to prepare a second version ready for
submission right in time for IETF#53.

First issues to be addressed with respect to the base-line concept
should be the issues described in the assessment draft. Maybe this is a
good starting point for proceeding. As mentioned in Salt Lake already,
all protocol proposals have very good ideas, which should be discussed
and considered to be folded into a common WG DMHA protocol draft.
Comments are appreciated.

I am looking forward to working with you all on bringing the DMHA
protocol specification ahead.

Regards,

Marco


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


From seamoby-admin@ietf.org  Thu Dec 20 12:13:35 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13013
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 12:13:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16944;
	Thu, 20 Dec 2001 11:55:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16912
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 11:55:45 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12277
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 11:55:41 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBKGsU801031;
	Thu, 20 Dec 2001 08:54:30 -0800 (PST)
Message-ID: <007c01c18976$c48bff60$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Claude Castelluccia" <claude.castelluccia@inrialpes.fr>,
        "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
Cc: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>, <seamoby@ietf.org>
References: <Pine.SOL.4.43.0112181555170.5355-100000@haskins.ee.surrey.ac.uk> <3C1FE3D5.5D9061EA@alcatel.com> <3C21C911.CF71E695@inrialpes.fr>
Subject: Re: [Seamoby] Defining Paging Area
Date: Thu, 20 Dec 2001 08:52:53 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Claude,

I believe Bechet's difficulty was with the terminology of the paper
(cells, etc.)
rather than the content. Pars has already indicated that the term
subnets should probably been used instead of cells.

            jak

----- Original Message -----
From: "Claude Castelluccia" <claude.castelluccia@inrialpes.fr>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
Cc: "Kar Ann Chew" <k.chew@eim.surrey.ac.uk>; <seamoby@ietf.org>
Sent: Thursday, December 20, 2001 3:18 AM
Subject: Re: [Seamoby] Defining Paging Area


> Behcet Sarikaya wrote:
>
> >   What Pars and Claude talk about as PAs I think is a cell level or
L1
> > concept. I am having difficulty in understanding their theory.
Hopefully they
> > will further develop it using L2 or L3 ideas so that we can grasp
the theory
> > of dynamic paging areas. Only thereafter some standardization can be
thought
> > of.
>
> Behcet, all of our work is about L3 paging!
> Why would we submit something about L1 or L2 paging area
> configuration to Seamoby????
> I am really surprised about your statement...
>
> Claude.
>
> --
>
> ----------------------------------------
> Claude CASTELLUCCIA, INRIA Rhone-Alpes
> ph:  +33 4.76.61.52.15 (fax: 52.52)
> http://www.inrialpes.fr/planete/
>
>
>


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


From seamoby-admin@ietf.org  Thu Dec 20 13:21:53 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15444
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 13:21:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20090;
	Thu, 20 Dec 2001 13:09:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20061
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 13:09:50 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15125
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 13:09:47 -0500 (EST)
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 MAA01293;
	Thu, 20 Dec 2001 12:09:19 -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 fBKI9Ir15559;
	Thu, 20 Dec 2001 12:09:18 -0600 (CST)
Message-ID: <3C222A2A.E141CBBC@alcatel.com>
Date: Thu, 20 Dec 2001 12:12:58 -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: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
CC: Seamoby <seamoby@ietf.org>
Subject: Re: [Seamoby] proposal on next steps in paging
References: <3C21FF83.907EF43C@ccrle.nec.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hi Marco,
  There is a very important issue with the way paging protocol assessment
was concluded, i.e. one of the candidate proposals was not eliminated in a
way which is not acceptable. As I said in one of my previous emails, the
assessment result is moot.
  I do not we can proceed without this issue being resolved satisfactorily.

  Regards,

Marco Liebsch wrote:

> Dear all,
>
> in order to proceed with DMHA protocol specification, I propose the
> following:
> Since the current base-line document is maybe a bit overloaded for being
> the first Seamoby WG draft, I will take out the Mobile IPv6 specific
> options out of the main part, but keep the generic explicit signaling in
> the document. Mobile IPv6 specific optimization could be kept in the
> documents annex or in a separate document (what do you think?).
> Furthermore, my opinion is that the concept should allow deployment of
> several paging strategies, as currently described in the draft. But
> maybe it is reasonable to extract the sections on paging strategies out
> of the current draft keeping them in a separate document, which could be
> further evaluated and extended. This would allow to get a first
> framework draft, which is clearly arranged and open for further
> specification of open issues.
> What about the following:
> Coming up with a first famework draft end of January, possibly having
> some further ideas and issues already addressed by then. Then we have
> about one month in order to prepare a second version ready for
> submission right in time for IETF#53.
>
> First issues to be addressed with respect to the base-line concept
> should be the issues described in the assessment draft. Maybe this is a
> good starting point for proceeding. As mentioned in Salt Lake already,
> all protocol proposals have very good ideas, which should be discussed
> and considered to be folded into a common WG DMHA protocol draft.
> Comments are appreciated.
>
> I am looking forward to working with you all on bringing the DMHA
> protocol specification ahead.
>
> Regards,
>
> Marco
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

--
Behcet


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


From seamoby-admin@ietf.org  Thu Dec 20 13:45:15 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16224
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 13:45:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20968;
	Thu, 20 Dec 2001 13:32:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20924
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 13:32:34 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15719
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 13:32:26 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBKIVi804817;
	Thu, 20 Dec 2001 10:31:44 -0800 (PST)
Message-ID: <023d01c18984$5a170130$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>,
        "Marco Liebsch" <Marco.Liebsch@ccrle.nec.de>
Cc: "Seamoby" <seamoby@ietf.org>
References: <3C21FF83.907EF43C@ccrle.nec.de> <3C222A2A.E141CBBC@alcatel.com>
Subject: Re: [Seamoby] proposal on next steps in paging
Date: Thu, 20 Dec 2001 10:30: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
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,

>   There is a very important issue with the way paging protocol
assessment
> was concluded, i.e. one of the candidate proposals was not eliminated
in a
> way which is not acceptable. As I said in one of my previous emails,
the
> assessment result is moot.
>   I do not we can proceed without this issue being resolved
satisfactorily.
>

I had taken from your previous email response on this topic that you
were
willing to work with Marco and the working group to assure
that the Seamoby protocol reflected the work in
draft-guri-seamboy-lahap-00.txt,
which I presume is the source your discontent. And also to work with
me and whoever else is interested in moving toward finding an IETF home
for
the L2 trigger work on paging which you've been doing. However, it now
seems that this is not the case.

What do you consider satisfactory resolution?

            jak




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


From seamoby-admin@ietf.org  Thu Dec 20 15:54:43 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20274
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 15:54:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25593;
	Thu, 20 Dec 2001 15:43:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25556
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 15:43:27 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19945
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 15:43:23 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBKKgt809758
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 12:42:55 -0800 (PST)
Message-ID: <034401c18996$ad640ec0$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@ietf.org>
Date: Thu, 20 Dec 2001 12:41:18 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] CAR Discovery Requirements Slide from Govind
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

        REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS

1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs


2. MUST support L2 devices of different technologies


3. MUST support for L2 devices (and ARs) in private/site-local spaces


4. MUST communicate capability information between GAARs in a secure and
reliable manner


5. MUST use standard format for capabilities..
 and this is TBD

6. Protocol applicability - SHOULD (show of hands indicated that a MUST
is needed here) support inter-domain as well as Intra-domain scope


7. MUST NOT introduce network elements dedicated to CAR discovery.


8. SHOULD minimize involvement of ARs which are not GAARs in CAR
discovery


9. MUST NOT depend on a particular mobility management protocol





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


From seamoby-admin@ietf.org  Thu Dec 20 20:19:55 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26306
	for <seamoby-archive@odin.ietf.org>; Thu, 20 Dec 2001 20:19:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02282;
	Thu, 20 Dec 2001 20:07:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02252
	for <seamoby@optimus.ietf.org>; Thu, 20 Dec 2001 20:07:17 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26193
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 20:07:15 -0500 (EST)
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 fBL16iJZ014457
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 20:06:44 -0500 (EST)
Received: from localhost (ohba@tari-dhcp1.research.telcordia.com [207.3.232.115])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id UAA09337
	for <seamoby@ietf.org>; Thu, 20 Dec 2001 20:06:38 -0500 (EST)
Date: Thu, 20 Dec 2001 19:05:42 -0500
To: seamoby@ietf.org
Message-ID: <20011221000542.GE1492@catfish>
Mail-Followup-To: seamoby@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 19
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Subject: [Seamoby] comments on the paging protocol assessment draft
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

I have a couple of comments to the paging assessment draft
(draft-ietf-seamoby-protocol-assessment-00.txt).

First thing is the process of selection. The criteria for selection
from the proposals, and the result should be included in the
assessment draft.  Specifically, the selected protocol is the one
having the largest number of the lowest ratings, i.e., containing six
1's, and neither having the largest number of the highest ratings nor
having the highest avarage rate.  There is a logical leap between the
ratings and the final selection. So I think that selection team had
some criteria other than the ratings.

And the second thing is that the comments that were posted by some of
the authors of the candidate protocols before the SLC meeting should
also be reflected to the assessment draft, if those comments are
relevant.

Regards,
Yoshihiro Ohba

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


From seamoby-admin@ietf.org  Fri Dec 21 05:36:19 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21204
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 05:36:19 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA25335;
	Fri, 21 Dec 2001 05:21:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA25306
	for <seamoby@optimus.ietf.org>; Fri, 21 Dec 2001 05:21:10 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20994
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 05:21:05 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace [192.168.102.1])
	by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id fBLAKgA07248;
	Fri, 21 Dec 2001 11:20:42 +0100 (CET)
Received: from ccrle.nec.de (zipo.heidelberg.ccrle.nec.de [192.168.102.84])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id LAA22736;
	Fri, 21 Dec 2001 11:20:49 +0100
Message-ID: <3C230D01.798213F4@ccrle.nec.de>
Date: Fri, 21 Dec 2001 11:20:49 +0100
From: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
CC: Seamoby <seamoby@ietf.org>
Subject: Re: [Seamoby] proposal on next steps in paging
References: <3C21FF83.907EF43C@ccrle.nec.de> <3C222A2A.E141CBBC@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,
you are not satisfied working together on the WG's protocol specification
bringing all the good ideas into the base-line concept? What do you propose how
to proceed then? Please tell me.

Marco

Behcet Sarikaya wrote:

> Hi Marco,
>   There is a very important issue with the way paging protocol assessment
> was concluded, i.e. one of the candidate proposals was not eliminated in a
> way which is not acceptable. As I said in one of my previous emails, the
> assessment result is moot.
>   I do not we can proceed without this issue being resolved satisfactorily.
>
>   Regards,
>
> Marco Liebsch wrote:
>
> > Dear all,
> >
> > in order to proceed with DMHA protocol specification, I propose the
> > following:
> > Since the current base-line document is maybe a bit overloaded for being
> > the first Seamoby WG draft, I will take out the Mobile IPv6 specific
> > options out of the main part, but keep the generic explicit signaling in
> > the document. Mobile IPv6 specific optimization could be kept in the
> > documents annex or in a separate document (what do you think?).
> > Furthermore, my opinion is that the concept should allow deployment of
> > several paging strategies, as currently described in the draft. But
> > maybe it is reasonable to extract the sections on paging strategies out
> > of the current draft keeping them in a separate document, which could be
> > further evaluated and extended. This would allow to get a first
> > framework draft, which is clearly arranged and open for further
> > specification of open issues.
> > What about the following:
> > Coming up with a first famework draft end of January, possibly having
> > some further ideas and issues already addressed by then. Then we have
> > about one month in order to prepare a second version ready for
> > submission right in time for IETF#53.
> >
> > First issues to be addressed with respect to the base-line concept
> > should be the issues described in the assessment draft. Maybe this is a
> > good starting point for proceeding. As mentioned in Salt Lake already,
> > all protocol proposals have very good ideas, which should be discussed
> > and considered to be folded into a common WG DMHA protocol draft.
> > Comments are appreciated.
> >
> > I am looking forward to working with you all on bringing the DMHA
> > protocol specification ahead.
> >
> > Regards,
> >
> > Marco
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
>
> --
> Behcet




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


From seamoby-admin@ietf.org  Fri Dec 21 11:19:09 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25806
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 11:19:08 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06565;
	Fri, 21 Dec 2001 11:07:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06536
	for <seamoby@optimus.ietf.org>; Fri, 21 Dec 2001 11:07:22 -0500 (EST)
Received: from EXCHSRV.stormventures.com ([65.107.25.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25643
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 11:07:18 -0500 (EST)
Received: by EXCHSRV.stormventures.com with Internet Mail Service (5.5.2653.19)
	id <YVAF317Y>; Fri, 21 Dec 2001 08:06:45 -0800
Message-ID: <DC6C13921CCAFB49BCB8461164A3F4E38D21B4@EXCHSRV.stormventures.com>
From: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>
To: "'Behcet Sarikaya'" <behcet.sarikaya@alcatel.com>,
        Marco Liebsch
	 <Marco.Liebsch@ccrle.nec.de>
Cc: Seamoby <seamoby@ietf.org>
Subject: RE: [Seamoby] proposal on next steps in paging
Date: Fri, 21 Dec 2001 08:06:44 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C18A39.7C51D030"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

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_01C18A39.7C51D030
Content-Type: text/plain

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I thought that James addressed this issue already. Please point to
the statement in the assessment draft that you object to. I believe
that James already made it clear that although a single person
reviewed both drafts, they were reviewed independently, and both had
ties to specific external protocols, which the review committee found
innapropriate.

So could you please qualify your objection?

PatC

- -----Original Message-----
From: Behcet Sarikaya [mailto:behcet.sarikaya@alcatel.com] 
Sent: Thursday, December 20, 2001 10:13 AM
To: Marco Liebsch
Cc: Seamoby
Subject: Re: [Seamoby] proposal on next steps in paging


Hi Marco,
  There is a very important issue with the way paging protocol
assessment was concluded, i.e. one of the candidate proposals was not
eliminated in a way which is not acceptable. As I said in one of my
previous emails, the assessment result is moot.
  I do not we can proceed without this issue being resolved
satisfactorily.

  Regards,

Marco Liebsch wrote:

> Dear all,
>
> in order to proceed with DMHA protocol specification, I propose the
> following:
> Since the current base-line document is maybe a bit overloaded for 
> being the first Seamoby WG draft, I will take out the Mobile IPv6 
> specific options out of the main part, but keep the generic
> explicit  signaling in the document. Mobile IPv6 specific
> optimization could be  kept in the documents annex or in a separate
> document (what do you  think?). Furthermore, my opinion is that the
> concept should allow  deployment of several paging strategies, as
> currently described in the  draft. But maybe it is reasonable to
> extract the sections on paging  strategies out of the current draft
> keeping them in a separate 
> document, which could be further evaluated and extended. This would
>  allow to get a first framework draft, which is clearly arranged
> and  open for further specification of open issues. What about the 
> following: Coming up with a first famework draft end of January, 
> possibly having some further ideas and issues already addressed by 
> then. Then we have about one month in order to prepare a second 
> version ready for submission right in time for IETF#53.
>
> First issues to be addressed with respect to the base-line concept 
> should be the issues described in the assessment draft. Maybe this
> is  a good starting point for proceeding. As mentioned in Salt Lake
> already, all protocol proposals have very good ideas, which should
> be  discussed and considered to be folded into a common WG DMHA
> protocol  draft. Comments are appreciated.
>
> I am looking forward to working with you all on bringing the DMHA 
> protocol specification ahead.
>
> Regards,
>
> Marco
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby

- --
Behcet


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

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPCNeFDN1fXKoxmisEQIzYwCfRAcn1cTd41mIiQKDtT8/kTG5VdMAoIml
sD1Kf3kDvri9+SexYP+BgIlP
=9UqC
-----END PGP SIGNATURE-----

------_=_NextPart_001_01C18A39.7C51D030
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Seamoby] proposal on next steps in paging</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>-----BEGIN PGP SIGNED MESSAGE-----</FONT>
<BR><FONT SIZE=2>Hash: SHA1</FONT>
</P>

<P><FONT SIZE=2>I thought that James addressed this issue already. Please point to</FONT>
<BR><FONT SIZE=2>the statement in the assessment draft that you object to. I believe</FONT>
<BR><FONT SIZE=2>that James already made it clear that although a single person</FONT>
<BR><FONT SIZE=2>reviewed both drafts, they were reviewed independently, and both had</FONT>
<BR><FONT SIZE=2>ties to specific external protocols, which the review committee found</FONT>
<BR><FONT SIZE=2>innapropriate.</FONT>
</P>

<P><FONT SIZE=2>So could you please qualify your objection?</FONT>
</P>

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

<P><FONT SIZE=2>- -----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Behcet Sarikaya [<A HREF="mailto:behcet.sarikaya@alcatel.com">mailto:behcet.sarikaya@alcatel.com</A>] </FONT>
<BR><FONT SIZE=2>Sent: Thursday, December 20, 2001 10:13 AM</FONT>
<BR><FONT SIZE=2>To: Marco Liebsch</FONT>
<BR><FONT SIZE=2>Cc: Seamoby</FONT>
<BR><FONT SIZE=2>Subject: Re: [Seamoby] proposal on next steps in paging</FONT>
</P>
<BR>

<P><FONT SIZE=2>Hi Marco,</FONT>
<BR><FONT SIZE=2>&nbsp; There is a very important issue with the way paging protocol</FONT>
<BR><FONT SIZE=2>assessment was concluded, i.e. one of the candidate proposals was not</FONT>
<BR><FONT SIZE=2>eliminated in a way which is not acceptable. As I said in one of my</FONT>
<BR><FONT SIZE=2>previous emails, the assessment result is moot.</FONT>
<BR><FONT SIZE=2>&nbsp; I do not we can proceed without this issue being resolved</FONT>
<BR><FONT SIZE=2>satisfactorily.</FONT>
</P>

<P><FONT SIZE=2>&nbsp; Regards,</FONT>
</P>

<P><FONT SIZE=2>Marco Liebsch wrote:</FONT>
</P>

<P><FONT SIZE=2>&gt; Dear all,</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; in order to proceed with DMHA protocol specification, I propose the</FONT>
<BR><FONT SIZE=2>&gt; following:</FONT>
<BR><FONT SIZE=2>&gt; Since the current base-line document is maybe a bit overloaded for </FONT>
<BR><FONT SIZE=2>&gt; being the first Seamoby WG draft, I will take out the Mobile IPv6 </FONT>
<BR><FONT SIZE=2>&gt; specific options out of the main part, but keep the generic</FONT>
<BR><FONT SIZE=2>&gt; explicit&nbsp; signaling in the document. Mobile IPv6 specific</FONT>
<BR><FONT SIZE=2>&gt; optimization could be&nbsp; kept in the documents annex or in a separate</FONT>
<BR><FONT SIZE=2>&gt; document (what do you&nbsp; think?). Furthermore, my opinion is that the</FONT>
<BR><FONT SIZE=2>&gt; concept should allow&nbsp; deployment of several paging strategies, as</FONT>
<BR><FONT SIZE=2>&gt; currently described in the&nbsp; draft. But maybe it is reasonable to</FONT>
<BR><FONT SIZE=2>&gt; extract the sections on paging&nbsp; strategies out of the current draft</FONT>
<BR><FONT SIZE=2>&gt; keeping them in a separate </FONT>
<BR><FONT SIZE=2>&gt; document, which could be further evaluated and extended. This would</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; allow to get a first framework draft, which is clearly arranged</FONT>
<BR><FONT SIZE=2>&gt; and&nbsp; open for further specification of open issues. What about the </FONT>
<BR><FONT SIZE=2>&gt; following: Coming up with a first famework draft end of January, </FONT>
<BR><FONT SIZE=2>&gt; possibly having some further ideas and issues already addressed by </FONT>
<BR><FONT SIZE=2>&gt; then. Then we have about one month in order to prepare a second </FONT>
<BR><FONT SIZE=2>&gt; version ready for submission right in time for IETF#53.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; First issues to be addressed with respect to the base-line concept </FONT>
<BR><FONT SIZE=2>&gt; should be the issues described in the assessment draft. Maybe this</FONT>
<BR><FONT SIZE=2>&gt; is&nbsp; a good starting point for proceeding. As mentioned in Salt Lake</FONT>
<BR><FONT SIZE=2>&gt; already, all protocol proposals have very good ideas, which should</FONT>
<BR><FONT SIZE=2>&gt; be&nbsp; discussed and considered to be folded into a common WG DMHA</FONT>
<BR><FONT SIZE=2>&gt; protocol&nbsp; draft. Comments are appreciated.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; I am looking forward to working with you all on bringing the DMHA </FONT>
<BR><FONT SIZE=2>&gt; protocol specification ahead.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; Regards,</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; Marco</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; _______________________________________________</FONT>
<BR><FONT SIZE=2>&gt; Seamoby mailing list</FONT>
<BR><FONT SIZE=2>&gt; Seamoby@ietf.org <A HREF="https://www1.ietf.org/mailman/listinfo/seamoby" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/seamoby</A></FONT>
</P>

<P><FONT SIZE=2>- --</FONT>
<BR><FONT SIZE=2>Behcet</FONT>
</P>
<BR>

<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Seamoby mailing list</FONT>
<BR><FONT SIZE=2>Seamoby@ietf.org</FONT>
<BR><FONT SIZE=2><A HREF="https://www1.ietf.org/mailman/listinfo/seamoby" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/seamoby</A></FONT>
</P>

<P><FONT SIZE=2>-----BEGIN PGP SIGNATURE-----</FONT>
<BR><FONT SIZE=2>Version: PGPfreeware 7.0.3 for non-commercial use &lt;<A HREF="http://www.pgp.com" TARGET="_blank">http://www.pgp.com</A>&gt;</FONT>
</P>

<P><FONT SIZE=2>iQA/AwUBPCNeFDN1fXKoxmisEQIzYwCfRAcn1cTd41mIiQKDtT8/kTG5VdMAoIml</FONT>
<BR><FONT SIZE=2>sD1Kf3kDvri9+SexYP+BgIlP</FONT>
<BR><FONT SIZE=2>=9UqC</FONT>
<BR><FONT SIZE=2>-----END PGP SIGNATURE-----</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C18A39.7C51D030--

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


From seamoby-admin@ietf.org  Fri Dec 21 12:28:52 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27265
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 12:28:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09042;
	Fri, 21 Dec 2001 12:16:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09013
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 12:16:19 -0500 (EST)
Received: from hotmail.com (f164.law9.hotmail.com [64.4.9.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26854
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 12:16:14 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 21 Dec 2001 09:15:48 -0800
Received: from 63.78.179.5 by lw9fd.law9.hotmail.msn.com with HTTP;
	Fri, 21 Dec 2001 17:15:48 GMT
X-Originating-IP: [63.78.179.5]
From: "Govind Krishnamurthi" <govs23@hotmail.com>
To: seamoby@ietf.org
Date: Fri, 21 Dec 2001 12:15:48 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F164USVeHV30TrbGn3S0000c6f7@hotmail.com>
X-OriginalArrivalTime: 21 Dec 2001 17:15:48.0442 (UTC) FILETIME=[2234EBA0:01C18A43]
Subject: [Seamoby] CAR DiscoveryProtocol Requirements...
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Hello all,
To add to James' mail. Please let us know if any of these
requirements need to be modified or whether any other requirements
are needed.


Regards,
Govind.




        REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
>
>1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
>
>
>2. MUST support L2 devices of different technologies
>
>
>3. MUST support for L2 devices (and ARs) in private/site-local spaces
>
>
>4. MUST communicate capability information between GAARs in a secure and
>reliable manner
>
>
>5. MUST use standard format for capabilities..
>  and this is TBD
>
>6. Protocol applicability - SHOULD (show of hands indicated that a MUST
>is needed here) support inter-domain as well as Intra-domain scope
>
>
>7. MUST NOT introduce network elements dedicated to CAR discovery.
>
>
>8. SHOULD minimize involvement of ARs which are not GAARs in CAR
>discovery
>
>
>9. MUST NOT depend on a particular mobility management protocol
>
>
>
>
>
>_______________________________________________
>Seamoby mailing list
>Seamoby@ietf.org
>https://www1.ietf.org/mailman/listinfo/seamoby






_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


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


From seamoby-admin@ietf.org  Fri Dec 21 12:48:31 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27719
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 12:48:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09731;
	Fri, 21 Dec 2001 12:36:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09701
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 12:36:53 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27452
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 12:36:43 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id fBLHaiJ23424
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 18:36:44 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Fri Dec 21 18:36:28 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKBZZBL>; Fri, 21 Dec 2001 18:28:09 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C18A@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'Govind Krishnamurthi'" <govs23@hotmail.com>, seamoby@ietf.org
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 18:36:26 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

I hope the deadline is not today is it ?

Hesham

  > -----Original Message-----
  > From: Govind Krishnamurthi [mailto:govs23@hotmail.com]
  > Sent: Friday, December 21, 2001 6:16 PM
  > To: seamoby@ietf.org
  > Subject: [Seamoby] CAR DiscoveryProtocol Requirements...
  > 
  > 
  > Hello all,
  > To add to James' mail. Please let us know if any of these
  > requirements need to be modified or whether any other requirements
  > are needed.
  > 
  > 
  > Regards,
  > Govind.
  > 
  > 
  > 
  > 
  >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
  > >
  > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
  > >
  > >
  > >2. MUST support L2 devices of different technologies
  > >
  > >
  > >3. MUST support for L2 devices (and ARs) in 
  > private/site-local spaces
  > >
  > >
  > >4. MUST communicate capability information between GAARs 
  > in a secure and
  > >reliable manner
  > >
  > >
  > >5. MUST use standard format for capabilities..
  > >  and this is TBD
  > >
  > >6. Protocol applicability - SHOULD (show of hands 
  > indicated that a MUST
  > >is needed here) support inter-domain as well as Intra-domain scope
  > >
  > >
  > >7. MUST NOT introduce network elements dedicated to CAR discovery.
  > >
  > >
  > >8. SHOULD minimize involvement of ARs which are not GAARs in CAR
  > >discovery
  > >
  > >
  > >9. MUST NOT depend on a particular mobility management protocol
  > >
  > >
  > >
  > >
  > >
  > >_______________________________________________
  > >Seamoby mailing list
  > >Seamoby@ietf.org
  > >https://www1.ietf.org/mailman/listinfo/seamoby
  > 
  > 
  > 
  > 
  > 
  > 
  > _________________________________________________________________
  > Chat with friends online, try MSN Messenger: 
http://messenger.msn.com


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

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


From seamoby-admin@ietf.org  Fri Dec 21 12:58:18 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27947
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 12:58:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09840;
	Fri, 21 Dec 2001 12:46:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09810
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 12:46:18 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27672
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 12:46:16 -0500 (EST)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace [192.168.102.1])
	by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id fBLHjqA12534
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 18:45:52 +0100 (CET)
Received: from ccrle.nec.de (zipo.heidelberg.ccrle.nec.de [192.168.102.84])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA27526
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 18:45:59 +0100
Message-ID: <3C237557.A8C73256@ccrle.nec.de>
Date: Fri, 21 Dec 2001 18:45:59 +0100
From: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Organization: NEC Europe Ltd.
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Seamoby <seamoby@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] framework for DMHA protocol
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dear all,
I will try to structure a draft framework, which is then for discussion
on the list, taking first the protocol as it is now and moving the
Mobile IPv6 options to be considered for MIP optimization purposes into
the Annex (open). We have to think about extensions and address the
parts the assessment draft refers to. Until first framework is
available, please be referred to the current version of the base-line
concept draft-renker-paging-ipv6-01.txt and also think of issues to be
clarifed with respect to what is already written. So we can address
these issues and have enhancements in the first draft version, which
could be submitted end of January, if the WG agrees and we proceed. What
do you think?

I wish you all a merry Christmas and a happy new year. I will be back in
the office around Jan, 10th.

Marco





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


From seamoby-admin@ietf.org  Fri Dec 21 13:19:17 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28534
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:19:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10580;
	Fri, 21 Dec 2001 13:08:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10552
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:08:05 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28184
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:08:02 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBLI7S819189;
	Fri, 21 Dec 2001 10:07:28 -0800 (PST)
Message-ID: <01a501c18a4a$20669010$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Hesham Soliman \(ERA\)" <hesham.soliman@era.ericsson.se>,
        "'Govind Krishnamurthi'" <govs23@hotmail.com>, <seamoby@ietf.org>
References: <4DA6EA82906FD511BE2F00508BCF053801C4C18A@Esealnt861.al.sw.ericsson.se>
Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 10:05:51 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

There is no deadline (yet) on comments for requirements. I believe Last
Call on the CAR discovery problem
statement draft runs out next week.

            jak

----- Original Message -----
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'Govind Krishnamurthi'" <govs23@hotmail.com>; <seamoby@ietf.org>
Sent: Friday, December 21, 2001 9:36 AM
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...


> I hope the deadline is not today is it ?
>
> Hesham
>
>   > -----Original Message-----
>   > From: Govind Krishnamurthi [mailto:govs23@hotmail.com]
>   > Sent: Friday, December 21, 2001 6:16 PM
>   > To: seamoby@ietf.org
>   > Subject: [Seamoby] CAR DiscoveryProtocol Requirements...
>   >
>   >
>   > Hello all,
>   > To add to James' mail. Please let us know if any of these
>   > requirements need to be modified or whether any other requirements
>   > are needed.
>   >
>   >
>   > Regards,
>   > Govind.
>   >
>   >
>   >
>   >
>   >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
>   > >
>   > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
>   > >
>   > >
>   > >2. MUST support L2 devices of different technologies
>   > >
>   > >
>   > >3. MUST support for L2 devices (and ARs) in
>   > private/site-local spaces
>   > >
>   > >
>   > >4. MUST communicate capability information between GAARs
>   > in a secure and
>   > >reliable manner
>   > >
>   > >
>   > >5. MUST use standard format for capabilities..
>   > >  and this is TBD
>   > >
>   > >6. Protocol applicability - SHOULD (show of hands
>   > indicated that a MUST
>   > >is needed here) support inter-domain as well as Intra-domain
scope
>   > >
>   > >
>   > >7. MUST NOT introduce network elements dedicated to CAR
discovery.
>   > >
>   > >
>   > >8. SHOULD minimize involvement of ARs which are not GAARs in CAR
>   > >discovery
>   > >
>   > >
>   > >9. MUST NOT depend on a particular mobility management protocol
>   > >
>   > >
>   > >
>   > >
>   > >
>   > >_______________________________________________
>   > >Seamoby mailing list
>   > >Seamoby@ietf.org
>   > >https://www1.ietf.org/mailman/listinfo/seamoby
>   >
>   >
>   >
>   >
>   >
>   >
>   > _________________________________________________________________
>   > Chat with friends online, try MSN Messenger:
> http://messenger.msn.com
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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


From seamoby-admin@ietf.org  Fri Dec 21 13:50:55 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29201
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:50:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11714;
	Fri, 21 Dec 2001 13:34:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11683
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:34:15 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28867
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:34:12 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA16714;
	Fri, 21 Dec 2001 10:33:44 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBLIXii14632;
	Fri, 21 Dec 2001 10:33:44 -0800
X-mProtect:  Fri, 21 Dec 2001 10:33:44 -0800 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdKipIlN; Fri, 21 Dec 2001 10:33:42 PST
Message-ID: <3C238086.BAC7566E@iprg.nokia.com>
Date: Fri, 21 Dec 2001 10:33:42 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Govind Krishnamurthi <govs23@hotmail.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
References: <F164USVeHV30TrbGn3S0000c6f7@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

hi all,

Govind Krishnamurthi wrote:
> 
> Hello all,
> To add to James' mail. Please let us know if any of these
> requirements need to be modified or whether any other requirements
> are needed.
> 
> Regards,
> Govind.
> 
>         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
> >
> >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
> >
> >
> >2. MUST support L2 devices of different technologies
> >
> >
> >3. MUST support for L2 devices (and ARs) in private/site-local spaces

Remove 3. everything else is fine.

Vijay


> >
> >
> >4. MUST communicate capability information between GAARs in a secure and
> >reliable manner
> >
> >
> >5. MUST use standard format for capabilities..
> >  and this is TBD
> >
> >6. Protocol applicability - SHOULD (show of hands indicated that a MUST
> >is needed here) support inter-domain as well as Intra-domain scope
> >
> >
> >7. MUST NOT introduce network elements dedicated to CAR discovery.
> >
> >
> >8. SHOULD minimize involvement of ARs which are not GAARs in CAR
> >discovery
> >
> >
> >9. MUST NOT depend on a particular mobility management protocol
> >
> >
> >
> >
> >
> >_______________________________________________
> >Seamoby mailing list
> >Seamoby@ietf.org
> >https://www1.ietf.org/mailman/listinfo/seamoby
> 
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
> 
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

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


From seamoby-admin@ietf.org  Fri Dec 21 13:53:28 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29263
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:53:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11809;
	Fri, 21 Dec 2001 13:38:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11778
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:38:24 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28925
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:38:21 -0500 (EST)
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 fBLIboJZ026387;
	Fri, 21 Dec 2001 13:37:51 -0500 (EST)
Received: from localhost (ohba@tari-dhcp1.research.telcordia.com [207.3.232.115])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id NAA11292;
	Fri, 21 Dec 2001 13:37:45 -0500 (EST)
Date: Fri, 21 Dec 2001 12:36:44 -0500
To: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>
Cc: Seamoby <seamoby@ietf.org>
Subject: Re: [Seamoby] framework for DMHA protocol
Message-ID: <20011221173644.GA709@catfish>
Mail-Followup-To: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>,
	Seamoby <seamoby@ietf.org>
References: <3C237557.A8C73256@ccrle.nec.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <3C237557.A8C73256@ccrle.nec.de>
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 23
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

I agree with Marco on the plan.

Yoshihiro Ohba

On Fri, Dec 21, 2001 at 06:45:59PM +0100, Marco Liebsch wrote:
> Dear all,
> I will try to structure a draft framework, which is then for discussion
> on the list, taking first the protocol as it is now and moving the
> Mobile IPv6 options to be considered for MIP optimization purposes into
> the Annex (open). We have to think about extensions and address the
> parts the assessment draft refers to. Until first framework is
> available, please be referred to the current version of the base-line
> concept draft-renker-paging-ipv6-01.txt and also think of issues to be
> clarifed with respect to what is already written. So we can address
> these issues and have enhancements in the first draft version, which
> could be submitted end of January, if the WG agrees and we proceed. What
> do you think?
> 
> I wish you all a merry Christmas and a happy new year. I will be back in
> the office around Jan, 10th.
> 
> Marco
> 

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


From seamoby-admin@ietf.org  Fri Dec 21 13:53:40 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29280
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:53:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11870;
	Fri, 21 Dec 2001 13:39:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11840
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:39:16 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28942
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:39:12 -0500 (EST)
From: Dirk.Trossen@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBLIdCC25943
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 20:39:12 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57f789bd24ac158f2504f@esvir05nok.ntc.nokia.com>;
 Fri, 21 Dec 2001 20:39:13 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <ZHA66VYZ>; Fri, 21 Dec 2001 20:38:50 +0200
Message-ID: <DC504E9C3384054C8506D3E6BB012460382D9E@bsebe001.NOE.Nokia.com>
To: vijayd@iprg.nokia.com, govs23@hotmail.com
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 20:37:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Hi,

is there any specific reason why you want to remove private
address space considerations? 

Regards,



Dirk

> -----Original Message-----
> From: ext Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> Sent: Friday, December 21, 2001 1:34 PM
> To: Govind Krishnamurthi
> Cc: seamoby@ietf.org
> Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> 
> 
> hi all,
> 
> Govind Krishnamurthi wrote:
> > 
> > Hello all,
> > To add to James' mail. Please let us know if any of these
> > requirements need to be modified or whether any other requirements
> > are needed.
> > 
> > Regards,
> > Govind.
> > 
> >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
> > >
> > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
> > >
> > >
> > >2. MUST support L2 devices of different technologies
> > >
> > >
> > >3. MUST support for L2 devices (and ARs) in 
> private/site-local spaces
> 
> Remove 3. everything else is fine.
> 
> Vijay
> 
> 
> > >
> > >
> > >4. MUST communicate capability information between GAARs 
> in a secure and
> > >reliable manner
> > >
> > >
> > >5. MUST use standard format for capabilities..
> > >  and this is TBD
> > >
> > >6. Protocol applicability - SHOULD (show of hands 
> indicated that a MUST
> > >is needed here) support inter-domain as well as Intra-domain scope
> > >
> > >
> > >7. MUST NOT introduce network elements dedicated to CAR discovery.
> > >
> > >
> > >8. SHOULD minimize involvement of ARs which are not GAARs in CAR
> > >discovery
> > >
> > >
> > >9. MUST NOT depend on a particular mobility management protocol
> > >
> > >
> > >
> > >
> > >
> > >_______________________________________________
> > >Seamoby mailing list
> > >Seamoby@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/seamoby
> > 
> > _________________________________________________________________
> > Chat with friends online, try MSN Messenger: 
> http://messenger.msn.com
> > 
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
> 
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

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


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


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

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

all other requirements are fine.

Vijay

"Trossen Dirk (NRC/Boston)" wrote:
> 
> Hi,
> 
> is there any specific reason why you want to remove private
> address space considerations?
> 
> Regards,
> 
> Dirk
> 
> > -----Original Message-----
> > From: ext Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > Sent: Friday, December 21, 2001 1:34 PM
> > To: Govind Krishnamurthi
> > Cc: seamoby@ietf.org
> > Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> >
> >
> > hi all,
> >
> > Govind Krishnamurthi wrote:
> > >
> > > Hello all,
> > > To add to James' mail. Please let us know if any of these
> > > requirements need to be modified or whether any other requirements
> > > are needed.
> > >
> > > Regards,
> > > Govind.
> > >
> > >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
> > > >
> > > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
> > > >
> > > >
> > > >2. MUST support L2 devices of different technologies
> > > >
> > > >
> > > >3. MUST support for L2 devices (and ARs) in
> > private/site-local spaces
> >
> > Remove 3. everything else is fine.
> >
> > Vijay
> >
> >
> > > >
> > > >
> > > >4. MUST communicate capability information between GAARs
> > in a secure and
> > > >reliable manner
> > > >
> > > >
> > > >5. MUST use standard format for capabilities..
> > > >  and this is TBD
> > > >
> > > >6. Protocol applicability - SHOULD (show of hands
> > indicated that a MUST
> > > >is needed here) support inter-domain as well as Intra-domain scope
> > > >
> > > >
> > > >7. MUST NOT introduce network elements dedicated to CAR discovery.
> > > >
> > > >
> > > >8. SHOULD minimize involvement of ARs which are not GAARs in CAR
> > > >discovery
> > > >
> > > >
> > > >9. MUST NOT depend on a particular mobility management protocol
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >_______________________________________________
> > > >Seamoby mailing list
> > > >Seamoby@ietf.org
> > > >https://www1.ietf.org/mailman/listinfo/seamoby
> > >
> > > _________________________________________________________________
> > > Chat with friends online, try MSN Messenger:
> > http://messenger.msn.com
> > >
> > > _______________________________________________
> > > Seamoby mailing list
> > > Seamoby@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/seamoby
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
> >

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


From seamoby-admin@ietf.org  Fri Dec 21 14:09:58 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29689
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 14:09:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12243;
	Fri, 21 Dec 2001 13:55:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12212
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 13:55:05 -0500 (EST)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29333
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 13:55:02 -0500 (EST)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBLItCQ20767
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 12:55:12 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57f5e0c623ac12f254079@davir01nok.americas.nokia.com>;
 Fri, 21 Dec 2001 12:55:03 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 21 Dec 2001 12:55:09 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Seamoby] CAR DiscoveryProtocol Requirements...
Date: Fri, 21 Dec 2001 13:55:02 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB01246008D54F@bsebe001.NOE.Nokia.com>
Thread-Topic: [Seamoby] CAR DiscoveryProtocol Requirements...
Thread-Index: AcGKTxNepc5uffY/EdWxMQAIx6TWeAAAHrUQ
From: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
To: "'Vijay Devarapalli'" <vijayd@IPRG.nokia.com>
Cc: "Govind Krishnamurthi" <govs23@hotmail.com>, <seamoby@ietf.org>
X-OriginalArrivalTime: 21 Dec 2001 18:55:09.0479 (UTC) FILETIME=[0342FB70:01C18A51]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA12213
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 8bit

Hi Vijay,

two comments:
- we are considering IPV4 as well IPV6, which brings naturally private
address spaces into play. As long as we are not considering entirely
public routers, any solution has to deal with this problem, which
therefore
makes it a requirement.

- It's certainly debatable that it makes a solution 'very complicated',
in particular since I don't know what kind of 'measure' you applied
for your statement. However, I'm sure that every requirement on its own 
makes the overall solution more complicated (this is certainly true for 
some others on the list of requirements). However, removing requirements

just for the sake of making life easier doesn't seem to be the right
way. 

Regards,



Dirk

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijayd@IPRG.nokia.com]
> Sent: Friday, December 21, 2001 1:41 PM
> To: Trossen Dirk (NRC/Boston)
> Cc: Govind Krishnamurthi; seamoby@ietf.org
> Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> 
> 
> 
> how about "it makes the CAR discovery protocol very 
> complicated".
> 
> and tell me why its there in the first place..
> 
> all other requirements are fine.
> 
> Vijay
> 
> "Trossen Dirk (NRC/Boston)" wrote:
> > 
> > Hi,
> > 
> > is there any specific reason why you want to remove private
> > address space considerations?
> > 
> > Regards,
> > 
> > Dirk
> > 
> > > -----Original Message-----
> > > From: ext Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > Sent: Friday, December 21, 2001 1:34 PM
> > > To: Govind Krishnamurthi
> > > Cc: seamoby@ietf.org
> > > Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> > >
> > >
> > > hi all,
> > >
> > > Govind Krishnamurthi wrote:
> > > >
> > > > Hello all,
> > > > To add to James' mail. Please let us know if any of these
> > > > requirements need to be modified or whether any other 
> requirements
> > > > are needed.
> > > >
> > > > Regards,
> > > > Govind.
> > > >
> > > >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
> > > > >
> > > > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
> > > > >
> > > > >
> > > > >2. MUST support L2 devices of different technologies
> > > > >
> > > > >
> > > > >3. MUST support for L2 devices (and ARs) in
> > > private/site-local spaces
> > >
> > > Remove 3. everything else is fine.
> > >
> > > Vijay
> > >
> > >
> > > > >
> > > > >
> > > > >4. MUST communicate capability information between GAARs
> > > in a secure and
> > > > >reliable manner
> > > > >
> > > > >
> > > > >5. MUST use standard format for capabilities..
> > > > >  and this is TBD
> > > > >
> > > > >6. Protocol applicability - SHOULD (show of hands
> > > indicated that a MUST
> > > > >is needed here) support inter-domain as well as 
> Intra-domain scope
> > > > >
> > > > >
> > > > >7. MUST NOT introduce network elements dedicated to 
> CAR discovery.
> > > > >
> > > > >
> > > > >8. SHOULD minimize involvement of ARs which are not 
> GAARs in CAR
> > > > >discovery
> > > > >
> > > > >
> > > > >9. MUST NOT depend on a particular mobility management protocol
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >Seamoby mailing list
> > > > >Seamoby@ietf.org
> > > > >https://www1.ietf.org/mailman/listinfo/seamoby
> > > >
> > > > 
> _________________________________________________________________
> > > > Chat with friends online, try MSN Messenger:
> > > http://messenger.msn.com
> > > >
> > > > _______________________________________________
> > > > Seamoby mailing list
> > > > Seamoby@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/seamoby
> > >
> > > _______________________________________________
> > > Seamoby mailing list
> > > Seamoby@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/seamoby
> > >
> 

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


From seamoby-admin@ietf.org  Fri Dec 21 14:18:28 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29938
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 14:18:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA12898;
	Fri, 21 Dec 2001 14:02:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA12867
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 14:02:55 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29591
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 14:02:52 -0500 (EST)
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 NAA23597;
	Fri, 21 Dec 2001 13:02:24 -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 fBLJ2Om15892;
	Fri, 21 Dec 2001 13:02:24 -0600 (CST)
Message-ID: <3C23881F.90F37A2F@alcatel.com>
Date: Fri, 21 Dec 2001 13:06:07 -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: James Kempf <kempf@docomolabs-usa.com>
CC: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>, Seamoby <seamoby@ietf.org>
Subject: Re: [Seamoby] proposal on next steps in paging
References: <3C21FF83.907EF43C@ccrle.nec.de> <3C222A2A.E141CBBC@alcatel.com> <023d01c18984$5a170130$7e6015ac@T23KEMPF>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Jim,
  I am going to  be positive and conciliatory as much as I can. Please see
Yoshi's email, he also has a strong point there.
  The satisfactory resolution I think relies on an agreement in
architecture. Let's agree on an architecture based on the entities defined
in RFC 3154 and then I do not care who does the editing.
  Considering the different pieces of IP paging protocol, the right
architecture would place the entities as follows:
DMA- takes care of paging registration, packet capturing in dormant mode
and starting the paging. Therefore DMA must be placed high in the
architecture possibly together with the Paging Agent. DMA could be mapped
to the MAP of hmipv6 in case of domain-based mobility or paging, or DMA
could be mapped to HA of mipv6 in case of home agent based paging.
TA- tracks the mobility in dormant mode. see below.
Paging areas. Whereever available, L2 paging areas must be used. L2 paging
areas are under the subnet. We must define how to interface with L2 paging
areas. In here paging triggers can prove useful. L2 paging areas can
probably be better utilized with the help of paging triggers.
On links with no L2 paging areas we must define L3 paging areas. L3 paging
areas must be IP subnet based. We must define how to interface, configure
L3 paging areas. Paging triggers can have some limited use here.
Paging Agent. Paging agent is placed somewhere in the Internet. It
interacts with DMA and then takes care of paging. Therefore the paging
agent behaviour can be defined based on the paging areas (L2 or L3).
TA- tracks the mobility in dormant mode. In case of L3 paging areas, TA
must be on the subnet. In case of L2 paging areas TA becomes less
important.
  We may develop an architecture document before going on the details of
the protocol in an ununderstandable rush. Once we have the architecture, I
think that the protocol design will follow smoothly and will deal with the
PDUs and on-link support for dormant mode and time-slot based paging and so
on..

Regards,

James Kempf wrote:

> Behcet,
>
> >   There is a very important issue with the way paging protocol
> assessment
> > was concluded, i.e. one of the candidate proposals was not eliminated
> in a
> > way which is not acceptable. As I said in one of my previous emails,
> the
> > assessment result is moot.
> >   I do not we can proceed without this issue being resolved
> satisfactorily.
> >
>
> I had taken from your previous email response on this topic that you
> were
> willing to work with Marco and the working group to assure
> that the Seamoby protocol reflected the work in
> draft-guri-seamboy-lahap-00.txt,
> which I presume is the source your discontent. And also to work with
> me and whoever else is interested in moving toward finding an IETF home
> for
> the L2 trigger work on paging which you've been doing. However, it now
> seems that this is not the case.
>
> What do you consider satisfactory resolution?
>
>             jak
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

--
Behcet


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


From seamoby-admin@ietf.org  Fri Dec 21 14:30:23 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00289
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 14:30:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13146;
	Fri, 21 Dec 2001 14:15:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13097
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 14:15:22 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29874
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 14:15:18 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA19558;
	Fri, 21 Dec 2001 11:14:51 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBLJEnn05548;
	Fri, 21 Dec 2001 11:14:49 -0800
X-mProtect:  Fri, 21 Dec 2001 11:14:49 -0800 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd8CSjIR; Fri, 21 Dec 2001 11:14:48 PST
Message-ID: <3C238A29.4E4E19C1@iprg.nokia.com>
Date: Fri, 21 Dec 2001 11:14:49 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
CC: Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
References: <DC504E9C3384054C8506D3E6BB01246008D54F@bsebe001.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dirk,

can you make IKE create an SA between two nodes (one having
a public address and another having a private address)?

does AAA route based on private address realm?

as for as I know neither is possible. (maybe I am wrong).

if an ISP wants context tranfer between two routers,
let it allocate public addresses for both.

Vijay


"Trossen Dirk (NRC/Boston)" wrote:
> 
> Hi Vijay,
> 
> two comments:
> - we are considering IPV4 as well IPV6, which brings naturally private
> address spaces into play. As long as we are not considering entirely
> public routers, any solution has to deal with this problem, which
> therefore
> makes it a requirement.
> 
> - It's certainly debatable that it makes a solution 'very complicated',
> in particular since I don't know what kind of 'measure' you applied
> for your statement. However, I'm sure that every requirement on its own
> makes the overall solution more complicated (this is certainly true for
> some others on the list of requirements). However, removing requirements
> 
> just for the sake of making life easier doesn't seem to be the right
> way.
> 
> Regards,
> 
> Dirk
> 
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijayd@IPRG.nokia.com]
> > Sent: Friday, December 21, 2001 1:41 PM
> > To: Trossen Dirk (NRC/Boston)
> > Cc: Govind Krishnamurthi; seamoby@ietf.org
> > Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> >
> >
> >
> > how about "it makes the CAR discovery protocol very
> > complicated".
> >
> > and tell me why its there in the first place..
> >
> > all other requirements are fine.
> >
> > Vijay
> >
> > "Trossen Dirk (NRC/Boston)" wrote:
> > >
> > > Hi,
> > >
> > > is there any specific reason why you want to remove private
> > > address space considerations?
> > >
> > > Regards,
> > >
> > > Dirk
> > >
> > > > -----Original Message-----
> > > > From: ext Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > Sent: Friday, December 21, 2001 1:34 PM
> > > > To: Govind Krishnamurthi
> > > > Cc: seamoby@ietf.org
> > > > Subject: Re: [Seamoby] CAR DiscoveryProtocol Requirements...
> > > >
> > > >
> > > > hi all,
> > > >
> > > > Govind Krishnamurthi wrote:
> > > > >
> > > > > Hello all,
> > > > > To add to James' mail. Please let us know if any of these
> > > > > requirements need to be modified or whether any other
> > requirements
> > > > > are needed.
> > > > >
> > > > > Regards,
> > > > > Govind.
> > > > >
> > > > >         REQUIREMENTS FOR CAR DISCOVERY PROTOCOLS
> > > > > >
> > > > > >1. MUST translate L2 Ids (APs and ARs) to L3 Ids of ARs
> > > > > >
> > > > > >
> > > > > >2. MUST support L2 devices of different technologies
> > > > > >
> > > > > >
> > > > > >3. MUST support for L2 devices (and ARs) in
> > > > private/site-local spaces
> > > >
> > > > Remove 3. everything else is fine.
> > > >
> > > > Vijay
> > > >
> > > >
> > > > > >
> > > > > >
> > > > > >4. MUST communicate capability information between GAARs
> > > > in a secure and
> > > > > >reliable manner
> > > > > >
> > > > > >
> > > > > >5. MUST use standard format for capabilities..
> > > > > >  and this is TBD
> > > > > >
> > > > > >6. Protocol applicability - SHOULD (show of hands
> > > > indicated that a MUST
> > > > > >is needed here) support inter-domain as well as
> > Intra-domain scope
> > > > > >
> > > > > >
> > > > > >7. MUST NOT introduce network elements dedicated to
> > CAR discovery.
> > > > > >
> > > > > >
> > > > > >8. SHOULD minimize involvement of ARs which are not
> > GAARs in CAR
> > > > > >discovery
> > > > > >
> > > > > >
> > > > > >9. MUST NOT depend on a particular mobility management protocol
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >_______________________________________________
> > > > > >Seamoby mailing list
> > > > > >Seamoby@ietf.org
> > > > > >https://www1.ietf.org/mailman/listinfo/seamoby
> > > > >
> > > > >
> > _________________________________________________________________
> > > > > Chat with friends online, try MSN Messenger:
> > > > http://messenger.msn.com
> > > > >
> > > > > _______________________________________________
> > > > > Seamoby mailing list
> > > > > Seamoby@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/seamoby
> > > >
> > > > _______________________________________________
> > > > Seamoby mailing list
> > > > Seamoby@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/seamoby
> > > >
> >

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


From seamoby-admin@ietf.org  Fri Dec 21 14:35:42 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00394
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 14:35:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13315;
	Fri, 21 Dec 2001 14:22:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13289
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 14:22:29 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00054
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 14:22:25 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBLJLG822411;
	Fri, 21 Dec 2001 11:21:16 -0800 (PST)
Message-ID: <020201c18a54$6f78acb0$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Marco Liebsch" <Marco.Liebsch@ccrle.nec.de>,
        "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Seamoby" <seamoby@ietf.org>
References: <3C237557.A8C73256@ccrle.nec.de> <20011221173644.GA709@catfish>
Subject: Re: [Seamoby] framework for DMHA protocol
Date: Fri, 21 Dec 2001 11:19:39 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Marco and Yoshi,

Great!

We have yet to hear from RajeevK on this, and Behcet still seems to have
some concerns, but in the interest of moving forward, I think you should
proceed.
If Behcet is willing to discuss his concerns, perhaps we can address
them before
you get too far into editing. I don't know where RajeevK is (he wasn't
at IETF),
but perhaps some of his co-authors could comment.


            jak


----- Original Message -----
From: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
To: "Marco Liebsch" <Marco.Liebsch@ccrle.nec.de>
Cc: "Seamoby" <seamoby@ietf.org>
Sent: Friday, December 21, 2001 9:36 AM
Subject: Re: [Seamoby] framework for DMHA protocol


> I agree with Marco on the plan.
>
> Yoshihiro Ohba
>
> On Fri, Dec 21, 2001 at 06:45:59PM +0100, Marco Liebsch wrote:
> > Dear all,
> > I will try to structure a draft framework, which is then for
discussion
> > on the list, taking first the protocol as it is now and moving the
> > Mobile IPv6 options to be considered for MIP optimization purposes
into
> > the Annex (open). We have to think about extensions and address the
> > parts the assessment draft refers to. Until first framework is
> > available, please be referred to the current version of the
base-line
> > concept draft-renker-paging-ipv6-01.txt and also think of issues to
be
> > clarifed with respect to what is already written. So we can address
> > these issues and have enhancements in the first draft version, which
> > could be submitted end of January, if the WG agrees and we proceed.
What
> > do you think?
> >
> > I wish you all a merry Christmas and a happy new year. I will be
back in
> > the office around Jan, 10th.
> >
> > Marco
> >
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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


From seamoby-admin@ietf.org  Fri Dec 21 14:50:52 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00717
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 14:50:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13995;
	Fri, 21 Dec 2001 14:37:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13966
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 14:37:16 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00416
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 14:37:12 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBLJag823032;
	Fri, 21 Dec 2001 11:36:42 -0800 (PST)
Message-ID: <021401c18a56$97540110$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@ietf.org>, "Yoshihiro Ohba" <yohba@tari.toshiba.com>
References: <20011221000542.GE1492@catfish>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Date: Fri, 21 Dec 2001 11:35:05 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Yoshi,


> First thing is the process of selection. The criteria for selection
> from the proposals, and the result should be included in the
> assessment draft.  Specifically, the selected protocol is the one
> having the largest number of the lowest ratings, i.e., containing six
> 1's, and neither having the largest number of the highest ratings nor
> having the highest avarage rate.  There is a logical leap between the
> ratings and the final selection. So I think that selection team had
> some criteria other than the ratings.
>

Yes, this wasn't clear. As I believe was discussed on the list, the
final decision was not made by the selection team, it was made
in consultation between the WG chairs and our AD. We based
our decision on the selection team's assessment and recommended
course of action(s). There was a judgement call involved, and the
judgement was based to a certain degree on what requirements
we felt were most important, in addition to process considerations.

In particular, as I mentioned in my previous email to Behcet,
independence
from mobility protocol was considered a first priority requirement,
because
this has been a foundational principle of all Seamoby work. In addition,
we
did not want the protocol to be encumbered by or dependent upon the
process of another working group, as this would set up a dependence
between our work and the work of another working group that could
result in delays. Finally, requirements originating out of the problem
statement
had higher priority than other requirements. So, for example, the
requirement of indepenence of paging area from subnet topology
was identified in the problem statement and therefore had higher
priority. These requirements are ones that we believe will give IP
paging
an advantage over current practice, and therefore are likely to serve as
an
incentive for implementation and deployment.

> And the second thing is that the comments that were posted by some of
> the authors of the candidate protocols before the SLC meeting should
> also be reflected to the assessment draft, if those comments are
> relevant.
>

The assessment is meant to be a record of the assessment team
deliberations
and not a complete transcript of the working group's dialog on the
process.
The comments posted by the authors are part of the mailing list archive.

However, I should probably remove the sentence in the abstract that says
the assessment draft will make a recommendation, since it doesn't.

Thank you for posting this. It is very important that the decision
making process
be transparent, and I agree that the WG chairs have not done a very good
job of explaining it. I hope this makes things clearer.


                jak




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


From seamoby-admin@ietf.org  Fri Dec 21 15:07:44 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01030
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 15:07:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14354;
	Fri, 21 Dec 2001 14:55:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14323
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 14:55:20 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00791
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 14:55:16 -0500 (EST)
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 fBLJsdJZ002651;
	Fri, 21 Dec 2001 14:54:40 -0500 (EST)
Received: from localhost (ohba@tari-dhcp1.research.telcordia.com [207.3.232.115])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id OAA11507;
	Fri, 21 Dec 2001 14:54:33 -0500 (EST)
Date: Fri, 21 Dec 2001 13:53:34 -0500
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Cc: James Kempf <kempf@docomolabs-usa.com>,
        Marco Liebsch <Marco.Liebsch@ccrle.nec.de>, Seamoby <seamoby@ietf.org>
Subject: Re: [Seamoby] proposal on next steps in paging
Message-ID: <20011221185334.GB709@catfish>
Mail-Followup-To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>,
	James Kempf <kempf@docomolabs-usa.com>,
	Marco Liebsch <Marco.Liebsch@ccrle.nec.de>,
	Seamoby <seamoby@ietf.org>
References: <3C21FF83.907EF43C@ccrle.nec.de> <3C222A2A.E141CBBC@alcatel.com> <023d01c18984$5a170130$7e6015ac@T23KEMPF> <3C23881F.90F37A2F@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <3C23881F.90F37A2F@alcatel.com>
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 88
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

On Fri, Dec 21, 2001 at 01:06:07PM -0600, Behcet Sarikaya wrote:
> Jim,
>   I am going to  be positive and conciliatory as much as I can. Please see
> Yoshi's email, he also has a strong point there.
>   The satisfactory resolution I think relies on an agreement in
> architecture. Let's agree on an architecture based on the entities defined
> in RFC 3154 and then I do not care who does the editing.
>   Considering the different pieces of IP paging protocol, the right
> architecture would place the entities as follows:
> DMA- takes care of paging registration, packet capturing in dormant mode
> and starting the paging. Therefore DMA must be placed high in the
> architecture possibly together with the Paging Agent. DMA could be mapped
> to the MAP of hmipv6 in case of domain-based mobility or paging, or DMA
> could be mapped to HA of mipv6 in case of home agent based paging.
> TA- tracks the mobility in dormant mode. see below.
> Paging areas. Whereever available, L2 paging areas must be used. L2 paging
> areas are under the subnet. We must define how to interface with L2 paging

One technical thing.  L2 paging area as well as L3 paging area is
orthogonal to IP subnet.  While there is a case in which an IP subnet 
contains one or more L2 paging areas, there may be other case in 
which an L2 paging area covers multiple IP subnets.

Yoshihiro Ohba

> areas. In here paging triggers can prove useful. L2 paging areas can
> probably be better utilized with the help of paging triggers.
> On links with no L2 paging areas we must define L3 paging areas. L3 paging
> areas must be IP subnet based. We must define how to interface, configure
> L3 paging areas. Paging triggers can have some limited use here.
> Paging Agent. Paging agent is placed somewhere in the Internet. It
> interacts with DMA and then takes care of paging. Therefore the paging
> agent behaviour can be defined based on the paging areas (L2 or L3).
> TA- tracks the mobility in dormant mode. In case of L3 paging areas, TA
> must be on the subnet. In case of L2 paging areas TA becomes less
> important.
>   We may develop an architecture document before going on the details of
> the protocol in an ununderstandable rush. Once we have the architecture, I
> think that the protocol design will follow smoothly and will deal with the
> PDUs and on-link support for dormant mode and time-slot based paging and so
> on..
> 
> Regards,
> 
> James Kempf wrote:
> 
> > Behcet,
> >
> > >   There is a very important issue with the way paging protocol
> > assessment
> > > was concluded, i.e. one of the candidate proposals was not eliminated
> > in a
> > > way which is not acceptable. As I said in one of my previous emails,
> > the
> > > assessment result is moot.
> > >   I do not we can proceed without this issue being resolved
> > satisfactorily.
> > >
> >
> > I had taken from your previous email response on this topic that you
> > were
> > willing to work with Marco and the working group to assure
> > that the Seamoby protocol reflected the work in
> > draft-guri-seamboy-lahap-00.txt,
> > which I presume is the source your discontent. And also to work with
> > me and whoever else is interested in moving toward finding an IETF home
> > for
> > the L2 trigger work on paging which you've been doing. However, it now
> > seems that this is not the case.
> >
> > What do you consider satisfactory resolution?
> >
> >             jak
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
> 
> --
> Behcet
> 
> 
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

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


From seamoby-admin@ietf.org  Fri Dec 21 15:53:08 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01865
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 15:53:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15634;
	Fri, 21 Dec 2001 15:40:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15604
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 15:40:03 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01602
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 15:39:59 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBLKdJ825466;
	Fri, 21 Dec 2001 12:39:19 -0800 (PST)
Message-ID: <027201c18a5f$566fd3a0$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
Cc: "Marco Liebsch" <Marco.Liebsch@ccrle.nec.de>, "Seamoby" <seamoby@ietf.org>
References: <3C21FF83.907EF43C@ccrle.nec.de> <3C222A2A.E141CBBC@alcatel.com> <023d01c18984$5a170130$7e6015ac@T23KEMPF> <3C23881F.90F37A2F@alcatel.com>
Subject: Re: [Seamoby] proposal on next steps in paging
Date: Fri, 21 Dec 2001 12:37:41 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,

>   I am going to  be positive and conciliatory as much as I can. Please
see
> Yoshi's email, he also has a strong point there.

Yes, I agree that we need to make sure everyone understands the
decision process.

>   The satisfactory resolution I think relies on an agreement in
> architecture. Let's agree on an architecture based on the entities
defined
> in RFC 3154 and then I do not care who does the editing.

I believe that is implied. But remember: RFC 3154 is a functional
architecture. The network architecture may cause the functional
entities in RFC 3154 to be grouped into larger entities so some
of the interfaces become internal interfaces and are not
exposed in the protocol. The network entities are those
between which the protocol is defined.

>   Considering the different pieces of IP paging protocol, the right
> architecture would place the entities as follows:
> DMA- takes care of paging registration, packet capturing in dormant
mode
> and starting the paging. Therefore DMA must be placed high in the
> architecture possibly together with the Paging Agent. DMA could be
mapped
> to the MAP of hmipv6 in case of domain-based mobility or paging, or
DMA
> could be mapped to HA of mipv6 in case of home agent based paging.

Well, there is the meta-issue of identifying the DMA with a mobility
specific architectural element, such as the HA or MAP, as we discussed.
Note that this is not saying that an implementation could not combine
a mobility architectural element and paging in one process or on
one host, just that they need to be separable from a network
interface standpoint.

Then there is a scalability issue in mapping the DMA to the HA or MAP.

There is also an issue in initiating a page from the HA. The HA might
be far across the Internet from the paging area where the MN is
located. There may be security and other (like latency) concerns
associated with having the DMA in another domain.

Thus, I think having the DMA in the same administrative domain as
the paging area is important.

> TA- tracks the mobility in dormant mode. see below.
> Paging areas. Whereever available, L2 paging areas must be used. L2
paging
> areas are under the subnet. We must define how to interface with L2
paging
> areas. In here paging triggers can prove useful. L2 paging areas can
> probably be better utilized with the help of paging triggers.

I agree, and I am attempting to set up some kind of IETF context in
which we can discuss paging triggers.

> On links with no L2 paging areas we must define L3 paging areas.

Actually, I think L3 paging areas may be needed regardless of whether
L2 paging areas are available or not. Suppose a mobile device
has 5 interfaces, each of which supports its own L2 paging
protocol. By confining the L2 paging to the last hop, it may be
possible to unify paging in the network and increase interoperability.
For this purpose, there may need to be some map between the
L2 paging areas and an L3 paging area.

>L3 paging
> areas must be IP subnet based.

As was discussed in the problem statement, one key aspect
of IP paging is to get away from a one to one mapping
between subnets and IP paging. This is the case
with current 3G networks (i.e. Location Area Identifiers)
and it is an aspect of inflexibility that the problem statement
identified may be a problem going forward toward
micro- and picocells.

>We must define how to interface, configure
> L3 paging areas.

Well, I certainly agree as the recent discussion on
paging area configuration should indicate. The
issue here is that it is not currently on the Seamoby
charter. My inclination is to wait until the paging
protocol is almost complete before requesting any
addition, but it certainly is a major candidate,
and we can consider requesting that it
be put on the charter if the working
group feels strongly about it.

>Paging triggers can have some limited use here.
> Paging Agent. Paging agent is placed somewhere in the Internet. It
> interacts with DMA and then takes care of paging. Therefore the paging
> agent behaviour can be defined based on the paging areas (L2 or L3).

I view the Paging Agent as the entity that initiates the actual page
directly
to the MN. This may be an L2 page or it may be an L3 page. I view it as
similar to
the last hop router.

> TA- tracks the mobility in dormant mode. In case of L3 paging areas,
TA
> must be on the subnet. In case of L2 paging areas TA becomes less
> important.

There must be a TA per paging area, not per subnet. In the case of
L2 paging areas, the TA is identified as the entity that is taking
the L2 paging area update and coverting it into an L3 paging
area update. So it plays an important role there. It is a candidate
to group with the PA, IMHO, since they both play an L2 to
L3 transition role if there is L2 paging support.

>   We may develop an architecture document before going on the details
of
> the protocol in an ununderstandable rush. Once we have the
architecture, I
> think that the protocol design will follow smoothly and will deal with
the
> PDUs and on-link support for dormant mode and time-slot based paging
and so
> on..
>
>

I consider RFC 3154, on which you are a co-author, as sufficient
architecture.
Actually, it is far more architecture than is typically done in IETF and
we got some amount of flak for that during its preparation.

I really think we have enough preparation to move forward on the
protocol
design. If you have some ideas about taking the functional architectural
elements that are identified in RFC 3154 and grouping them differently
from the way they are grouped in draft-renker-paging-ipv6-01.txt, then
I suggest you communicate them with Marco and the working group.
What you've outlined above doesn't give me a clear idea about how
you would accomplish such a grouping, however. I agree that the
paging protocol document should have a section that clearly
defines how the functional elements in RFC 3154 map to
network entities between which the protocol would be exchanged.

                    jak


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


From seamoby-admin@ietf.org  Fri Dec 21 16:52:10 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02808
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 16:52:10 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17146;
	Fri, 21 Dec 2001 16:38:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17113
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 16:38:56 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02648
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 16:38:51 -0500 (EST)
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 fBLLboJZ011496;
	Fri, 21 Dec 2001 16:37:50 -0500 (EST)
Received: from localhost (ohba@tari-dhcp1.research.telcordia.com [207.3.232.115])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id QAA11834;
	Fri, 21 Dec 2001 16:37:44 -0500 (EST)
Date: Fri, 21 Dec 2001 15:36:45 -0500
To: James Kempf <kempf@docomolabs-usa.com>
Cc: seamoby@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Message-ID: <20011221203645.GD709@catfish>
Mail-Followup-To: James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org,
	Yoshihiro Ohba <yohba@tari.toshiba.com>
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <021401c18a56$97540110$7e6015ac@T23KEMPF>
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 124
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Jim,

Thanks for the response.

Additional comments are in-line.  Note that I'm not objecting the
selection since it would be better to be constructive, but just to
make things clearer and have a correct understanding of the result 
as much as possible.

On Fri, Dec 21, 2001 at 11:35:05AM -0800, James Kempf wrote:
> Yoshi,
> 
> 
> > First thing is the process of selection. The criteria for selection
> > from the proposals, and the result should be included in the
> > assessment draft.  Specifically, the selected protocol is the one
> > having the largest number of the lowest ratings, i.e., containing six
> > 1's, and neither having the largest number of the highest ratings nor
> > having the highest avarage rate.  There is a logical leap between the
> > ratings and the final selection. So I think that selection team had
> > some criteria other than the ratings.
> >
> 
> Yes, this wasn't clear. As I believe was discussed on the list, the
> final decision was not made by the selection team, it was made
> in consultation between the WG chairs and our AD. We based
> our decision on the selection team's assessment and recommended
> course of action(s). There was a judgement call involved, and the
> judgement was based to a certain degree on what requirements
> we felt were most important, in addition to process considerations.
> 
> In particular, as I mentioned in my previous email to Behcet,
> independence
> from mobility protocol was considered a first priority requirement,
> because
> this has been a foundational principle of all Seamoby work. In addition,
> we

As assessment team correctly evaluated,
draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies independency
from mobility protocol.

> did not want the protocol to be encumbered by or dependent upon the
> process of another working group, as this would set up a dependence
> between our work and the work of another working group that could
> result in delays. Finally, requirements originating out of the problem
> statement
> had higher priority than other requirements. So, for example, the
> requirement of indepenence of paging area from subnet topology
> was identified in the problem statement and therefore had higher
> priority. These requirements are ones that we believe will give IP
> paging
> an advantage over current practice, and therefore are likely to serve as
> an
> incentive for implementation and deployment.

draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies indepenency of
paging area from subnet topology, but unfortunately the selection team
seems to misunderstand that the protocol does not satisfy this
requirement, which I also pointed out this both on the mike in the SLC
meeting and in my comments posted before the SLC meeting.  Actually,
we paid a special care on this point, for example we explitly
mentioned in the draft that:

   Paging Area

     (snip)

     An arbitrary mapping between subnets and paging areas is allowed in
     this protocol.

Additional comments:

Jim also mentioned in the SLC meeting that our protocol requires
extranous signaling (among separate agents), which is not desirable.
This is not exactly correct because our protocol allows elimination of
extranous signaling by implementing those agents in a single box (for
small size networks).  Extranous signaling is inevitable if
scalability matters.  For the same reason, extranous signaling is also
described in the selected protocol if PA is hierachically configured.
There is always tradeoff between scalability and centralized agent.

Jim also mentioned in the SLC meeting that our protocol does not
support time-slotted dormant mode at L3.  This is true, but
time-slotted dormant mode at L3 was not explicitly described in the
requirements document, and I don't think the basic issue of how to
synchronize at L3 can be solved by just definig a set of
synchronization timing parameters.  Additional consideration of
hardware-based IP-paging implementation and interference with other
traffic, etc. would be still necessary if we really want to archive
it.


Regards,
Yoshihiro Ohba


> 
> > And the second thing is that the comments that were posted by some of
> > the authors of the candidate protocols before the SLC meeting should
> > also be reflected to the assessment draft, if those comments are
> > relevant.
> >
> 
> The assessment is meant to be a record of the assessment team
> deliberations
> and not a complete transcript of the working group's dialog on the
> process.
> The comments posted by the authors are part of the mailing list archive.
> 
> However, I should probably remove the sentence in the abstract that says
> the assessment draft will make a recommendation, since it doesn't.
> 
> Thank you for posting this. It is very important that the decision
> making process
> be transparent, and I agree that the WG chairs have not done a very good
> job of explaining it. I hope this makes things clearer.
> 
> 
>                 jak
> 
> 
> 
> 

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


From seamoby-admin@ietf.org  Fri Dec 21 18:15:35 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03693
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:15:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA19090;
	Fri, 21 Dec 2001 18:03:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA19059
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 18:03:00 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03557
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 18:02:56 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBLN1x801363;
	Fri, 21 Dec 2001 15:01:59 -0800 (PST)
Message-ID: <033301c18a73$44673090$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <seamoby@ietf.org>, "Yoshihiro Ohba" <yohba@tari.toshiba.com>
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Date: Fri, 21 Dec 2001 15:00:21 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hi Yoshi,

> Additional comments are in-line.  Note that I'm not objecting the
> selection since it would be better to be constructive, but just to
> make things clearer and have a correct understanding of the result
> as much as possible.
>

I understand.

> As assessment team correctly evaluated,
> draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies independency
> from mobility protocol.
>

Yes.

> draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies indepenency of
> paging area from subnet topology, but unfortunately the selection team
> seems to misunderstand that the protocol does not satisfy this
> requirement, which I also pointed out this both on the mike in the SLC
> meeting and in my comments posted before the SLC meeting.  Actually,
> we paid a special care on this point, for example we explitly
> mentioned in the draft that:
>
>    Paging Area
>
>      (snip)
>
>      An arbitrary mapping between subnets and paging areas is allowed
in
>      this protocol.
>

But do you think it is realistic to expect the paging team to rate
the design based on this single sentence when the name of the protocol
implies a connection between the subnet and paging area, and the
rest of the design is described in terms of having a paging agent (which
controls the paging area) in the last hop subnet?

> Jim also mentioned in the SLC meeting that our protocol requires
> extranous signaling (among separate agents), which is not desirable.
> This is not exactly correct because our protocol allows elimination of
> extranous signaling by implementing those agents in a single box (for
> small size networks).  Extranous signaling is inevitable if
> scalability matters.  For the same reason, extranous signaling is also
> described in the selected protocol if PA is hierachically configured.
> There is always tradeoff between scalability and centralized agent.
>

Exactly what functional elements to group into a network element
is a design, not an implementation, choice. The draft-ohba design chose
a one to one mapping between functional elements and network
elements. While it is certainly possible to deploy by bundling
multiple network entities on a single host, the interface between
the entities, and thus the protocols on those interfaces, remain
as does the potential for extraneous signaling.

That said, I agree that it is certainly a challenge to come up with
a design that minimizes signaling, and I think that, going
forward, we need to keep this in mind.

> Jim also mentioned in the SLC meeting that our protocol does not
> support time-slotted dormant mode at L3.  This is true, but
> time-slotted dormant mode at L3 was not explicitly described in the
> requirements document, and I don't think the basic issue of how to
> synchronize at L3 can be solved by just definig a set of
> synchronization timing parameters.  Additional consideration of
> hardware-based IP-paging implementation and interference with other
> traffic, etc. would be still necessary if we really want to archive
> it.
>

The requirements do call out the need to support multiple dormant
modes, and that requires the ability to support time-slotted paging.
For example, draft-sarikaya has a good description of how
to support time-slotted paging. I recall having discussed this
in the requirements phase, but perhaps we should have been
clearer in the requirements document about what support for multiple
dormant modes means.


            jak


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


From seamoby-admin@ietf.org  Fri Dec 21 18:42:20 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04107
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:42:20 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA19613;
	Fri, 21 Dec 2001 18:30:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA19574
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 18:30:22 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03910
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 18:30:18 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA01987;
	Fri, 21 Dec 2001 15:29:15 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBLNTFQ06003;
	Fri, 21 Dec 2001 15:29:15 -0800
X-mProtect:  Fri, 21 Dec 2001 15:29:15 -0800 Nokia Silicon Valley Messaging Protection
Received: from jmalinen.iprg.nokia.com (205.226.2.98)
	by darkstar.iprg.nokia.com smtpdxAFsAE; Fri, 21 Dec 2001 15:29:13 PST
Received: from iprg.nokia.com (localhost [127.0.0.1]) by jmalinen.iprg.nokia.com (8.9.3/8.6.12) with ESMTP id PAA54347; Fri, 21 Dec 2001 15:29:13 -0800 (PST)
Message-ID: <3C23C5C9.5E41C971@iprg.nokia.com>
Date: Fri, 21 Dec 2001 15:29:13 -0800
From: "Jari T. Malinen" <jmalinen@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

Seems I have mail problems (James's mails get filtered due to
them having "MIME EXPLOIT - multiple CTE flds", local problem here..)
I do not know if paging-protocol-assessment has been to last call and
have this comment whenever that is the case.

I have to agree with Yoshihiro's remarks and suggest the following.
Seems the paging assessment team's draft does not map at all to the
actual selection criteria and no textual document on the actual
criteria have been published in a working group document format.
Hence the current assessment document does not represent the decision
and I can't see what is its usefulness as an RFC.

From the mails so far there seems to be no clarity on preference
of criteria and how the important one really map to current proposals.
I read from fragments of James's mails protocol independence and
topology independence are good but fail to see why this would make
draft-renker clearly above other than on hmip-paging on protocol
independence. Hence, I suggest a re-write of an assessment document
explaining the process and criteria by which draft-renker was selected.

BR,

-Jari

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


From seamoby-admin@ietf.org  Fri Dec 21 19:17:16 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05054
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 19:17:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20664;
	Fri, 21 Dec 2001 19:04:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20615
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 19:04:55 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04759
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 19:04:52 -0500 (EST)
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 fBM03nJZ019561;
	Fri, 21 Dec 2001 19:03:49 -0500 (EST)
Received: from localhost (ohba@tari-dhcp1.research.telcordia.com [207.3.232.115])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id TAA12095;
	Fri, 21 Dec 2001 19:03:43 -0500 (EST)
Date: Fri, 21 Dec 2001 18:02:44 -0500
To: James Kempf <kempf@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, seamoby@ietf.org
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Message-ID: <20011221230244.GA1194@catfish>
Mail-Followup-To: James Kempf <kempf@docomolabs-usa.com>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>, seamoby@ietf.org
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <033301c18a73$44673090$7e6015ac@T23KEMPF>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <033301c18a73$44673090$7e6015ac@T23KEMPF>
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 139
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

On Fri, Dec 21, 2001 at 03:00:21PM -0800, James Kempf wrote:
> Hi Yoshi,
> 
> > Additional comments are in-line.  Note that I'm not objecting the
> > selection since it would be better to be constructive, but just to
> > make things clearer and have a correct understanding of the result
> > as much as possible.
> >
> 
> I understand.
> 
> > As assessment team correctly evaluated,
> > draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies independency
> > from mobility protocol.
> >
> 
> Yes.
> 
> > draft-ohba-seamoby-last-hop-dmha-02.txt also satisfies indepenency of
> > paging area from subnet topology, but unfortunately the selection team
> > seems to misunderstand that the protocol does not satisfy this
> > requirement, which I also pointed out this both on the mike in the SLC
> > meeting and in my comments posted before the SLC meeting.  Actually,
> > we paid a special care on this point, for example we explitly
> > mentioned in the draft that:
> >
> >    Paging Area
> >
> >      (snip)
> >
> >      An arbitrary mapping between subnets and paging areas is allowed
> in
> >      this protocol.
> >
> 
> But do you think it is realistic to expect the paging team to rate
> the design based on this single sentence when the name of the protocol
> implies a connection between the subnet and paging area, and the
> rest of the design is described in terms of having a paging agent (which
> controls the paging area) in the last hop subnet?

We also have the following desription:

6.4.3.  Other States in Paging Agent

   The following additional information MAY be maintained.

   o A list of Access Routers through which Paging messages are carried
     on traffic channel.

   o Any L2 dependent information needed for performing L2 paging.  The
     L2 dependent information MAY include the list of Access Points that
     are not able to receive and process Paging messages at L3.  Note that
     how to page Hosts through those Access Points depends on L2 and out of
     the scope of this document.

     /* Authors' note: if an Access Point is able to receive and process
     Paging messages at L3, then it can be a separated Paging Agent and
     SHOULD NOT be included in the above list. */

I think this is enough to indicate independency between paging area
and subnets.

> 
> > Jim also mentioned in the SLC meeting that our protocol requires
> > extranous signaling (among separate agents), which is not desirable.
> > This is not exactly correct because our protocol allows elimination of
> > extranous signaling by implementing those agents in a single box (for
> > small size networks).  Extranous signaling is inevitable if
> > scalability matters.  For the same reason, extranous signaling is also
> > described in the selected protocol if PA is hierachically configured.
> > There is always tradeoff between scalability and centralized agent.
> >
> 
> Exactly what functional elements to group into a network element
> is a design, not an implementation, choice. The draft-ohba design chose
> a one to one mapping between functional elements and network
> elements. While it is certainly possible to deploy by bundling
> multiple network entities on a single host, the interface between
> the entities, and thus the protocols on those interfaces, remain
> as does the potential for extraneous signaling.

It would be more fair to say that draft-renker also remains as does the
potential for extraneous signaling since it defines hierarchical
paging, but the degree of extraneous signaling of draft-renker 
might be less than that of draft-ohba since DMA and TA is always 
together in draft-renker.

> 
> That said, I agree that it is certainly a challenge to come up with
> a design that minimizes signaling, and I think that, going
> forward, we need to keep this in mind.

Agreed.

> 
> > Jim also mentioned in the SLC meeting that our protocol does not
> > support time-slotted dormant mode at L3.  This is true, but
> > time-slotted dormant mode at L3 was not explicitly described in the
> > requirements document, and I don't think the basic issue of how to
> > synchronize at L3 can be solved by just definig a set of
> > synchronization timing parameters.  Additional consideration of
> > hardware-based IP-paging implementation and interference with other
> > traffic, etc. would be still necessary if we really want to archive
> > it.
> >
> 
> The requirements do call out the need to support multiple dormant
> modes, and that requires the ability to support time-slotted paging.
> For example, draft-sarikaya has a good description of how
> to support time-slotted paging. I recall having discussed this
> in the requirements phase, but perhaps we should have been
> clearer in the requirements document about what support for multiple
> dormant modes means.

I misunderstood the meaning of multiple dormant modes such that it
would mean multiple dormancy states, e.g., Active/Sniff/Hold/Park
modes in the case of Bluetooth.  Also, I had been thinking that
time-slotted paging at L3 only relates to the following requirement,
and that it is weaker than other requirements since it uses SHOULD NOT
instead of MUST NOT.

4.13.   Future L3 Paging Support
   
   Recognizing that future dormant mode and wireless link protocols may 
   be designed that more efficiently utilize IP, the IP paging protocol
   SHOULD NOT require L2 support for paging.

I guess this requirement seems to have been weighted higher during the 
judgement process.

Yoshihiro Ohba


> 
> 
>             jak
> 
> 

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


From seamoby-admin@ietf.org  Fri Dec 21 20:00:18 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05839
	for <seamoby-archive@odin.ietf.org>; Fri, 21 Dec 2001 20:00:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21637;
	Fri, 21 Dec 2001 19:48:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21604
	for <seamoby@ns.ietf.org>; Fri, 21 Dec 2001 19:48:03 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05644
	for <seamoby@ietf.org>; Fri, 21 Dec 2001 19:48:00 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA06461;
	Fri, 21 Dec 2001 16:47:01 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id fBM0l0i01916;
	Fri, 21 Dec 2001 16:47:00 -0800
X-mProtect:  Fri, 21 Dec 2001 16:47:00 -0800 Nokia Silicon Valley Messaging Protection
Received: from jmalinen.iprg.nokia.com (205.226.2.98)
	by darkstar.iprg.nokia.com smtpd5VnzVO; Fri, 21 Dec 2001 16:46:59 PST
Received: from iprg.nokia.com (localhost [127.0.0.1]) by jmalinen.iprg.nokia.com (8.9.3/8.6.12) with ESMTP id QAA54468; Fri, 21 Dec 2001 16:46:58 -0800 (PST)
Message-ID: <3C23D802.5E052D52@iprg.nokia.com>
Date: Fri, 21 Dec 2001 16:46:58 -0800
From: "Jari T. Malinen" <jmalinen@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: James Kempf <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: Re: [Seamoby] framework for DMHA protocol
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <033301c18a73$44673090$7e6015ac@T23KEMPF> <20011221230244.GA1194@catfish>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

Having a design team framework document is ok, currently the draft-renker
gives a multitude of choices to do a protocol. Ultimately we'll need something
simple and unambiguous. This would need strong modification to become a
real protocol from its current format which looks more like an architecture
with candidate modes for several functionalities.

I second that the requirement for protocol independence is important.
Hence, I suggest structuring the document in a way that decouples the protocol
from all other protocols (MIPv6 etc. included) so much that they do not need
ideally to be even refered to at all. If needed, there should be appendices
describing interaction but only in the case it is essential for the
working of the protocol in some mode etc. Interdependences should be
minimized.

Merry Christmas and a Happy New year all,

-Jari

On Fri, Dec 21, 2001 at 06:45:59PM +0100, Marco Liebsch wrote:
> Dear all,
> I will try to structure a draft framework, which is then for discussion
> on the list, taking first the protocol as it is now and moving the
> Mobile IPv6 options to be considered for MIP optimization purposes into
> the Annex (open). We have to think about extensions and address the
> parts the assessment draft refers to. Until first framework is
> available, please be referred to the current version of the base-line
> concept draft-renker-paging-ipv6-01.txt and also think of issues to be
> clarifed with respect to what is already written. So we can address
> these issues and have enhancements in the first draft version, which
> could be submitted end of January, if the WG agrees and we proceed. What
> do you think?
> 
> I wish you all a merry Christmas and a happy new year. I will be back in
> the office around Jan, 10th.
> 
> Marco
>

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


From seamoby-admin@ietf.org  Sat Dec 22 00:57:35 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10230
	for <seamoby-archive@odin.ietf.org>; Sat, 22 Dec 2001 00:57:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA27656;
	Sat, 22 Dec 2001 00:44:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA27627
	for <seamoby@optimus.ietf.org>; Sat, 22 Dec 2001 00:44:25 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10151
	for <seamoby@ietf.org>; Sat, 22 Dec 2001 00:44:23 -0500 (EST)
Received: from T23KEMPF (dhcp142.docomo-usa.com [172.21.96.142])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBM5hG808554;
	Fri, 21 Dec 2001 21:43:16 -0800 (PST)
Message-ID: <000f01c18aab$54a673c0$8e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jari T. Malinen" <jmalinen@iprg.nokia.com>,
        "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <seamoby@ietf.org>
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <3C23C5C9.5E41C971@iprg.nokia.com>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Date: Fri, 21 Dec 2001 21:41:38 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Jari,

Good points. I will add a section in the assessment document that
explains how the final decision was arrived at.

            jak

----- Original Message -----
From: "Jari T. Malinen" <jmalinen@iprg.nokia.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "James Kempf" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
Sent: Friday, December 21, 2001 3:29 PM
Subject: Re: [Seamoby] comments on the paging protocol assessment draft


> Hello,
>
> Seems I have mail problems (James's mails get filtered due to
> them having "MIME EXPLOIT - multiple CTE flds", local problem here..)
> I do not know if paging-protocol-assessment has been to last call and
> have this comment whenever that is the case.
>
> I have to agree with Yoshihiro's remarks and suggest the following.
> Seems the paging assessment team's draft does not map at all to the
> actual selection criteria and no textual document on the actual
> criteria have been published in a working group document format.
> Hence the current assessment document does not represent the decision
> and I can't see what is its usefulness as an RFC.
>
> >From the mails so far there seems to be no clarity on preference
> of criteria and how the important one really map to current proposals.
> I read from fragments of James's mails protocol independence and
> topology independence are good but fail to see why this would make
> draft-renker clearly above other than on hmip-paging on protocol
> independence. Hence, I suggest a re-write of an assessment document
> explaining the process and criteria by which draft-renker was
selected.
>
> BR,
>
> -Jari
>


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


From seamoby-admin@ietf.org  Sat Dec 22 01:16:34 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11242
	for <seamoby-archive@odin.ietf.org>; Sat, 22 Dec 2001 01:16:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29284;
	Sat, 22 Dec 2001 01:05:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29230
	for <seamoby@optimus.ietf.org>; Sat, 22 Dec 2001 01:05:49 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10340
	for <seamoby@ietf.org>; Sat, 22 Dec 2001 01:05:48 -0500 (EST)
Received: from T23KEMPF (dhcp142.docomo-usa.com [172.21.96.142])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBM64k808869;
	Fri, 21 Dec 2001 22:04:46 -0800 (PST)
Message-ID: <002f01c18aae$55984670$8e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <seamoby@ietf.org>
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <033301c18a73$44673090$7e6015ac@T23KEMPF> <20011221230244.GA1194@catfish>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Date: Fri, 21 Dec 2001 22:03:08 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Yoshi,

> > But do you think it is realistic to expect the paging team to rate
> > the design based on this single sentence when the name of the
protocol
> > implies a connection between the subnet and paging area, and the
> > rest of the design is described in terms of having a paging agent
(which
> > controls the paging area) in the last hop subnet?
>
> We also have the following desription:
>
> 6.4.3.  Other States in Paging Agent
>
>    The following additional information MAY be maintained.
>
>    o A list of Access Routers through which Paging messages are
carried
>      on traffic channel.
>
>    o Any L2 dependent information needed for performing L2 paging.
The
>      L2 dependent information MAY include the list of Access Points
that
>      are not able to receive and process Paging messages at L3.  Note
that
>      how to page Hosts through those Access Points depends on L2 and
out of
>      the scope of this document.
>
>      /* Authors' note: if an Access Point is able to receive and
process
>      Paging messages at L3, then it can be a separated Paging Agent
and
>      SHOULD NOT be included in the above list. */
>
> I think this is enough to indicate independency between paging area
> and subnets.
>

I agree that the first bullet implies that there may be multiple
subnets per paging agent, and thus per paging area,
but to me this looks like an afterthought
and not a fundamental feature of the design. I expect that was
also the case for the person who performed the requirements
comparison on the document. It was difficult enough for
the assessment team to wade through the details of
each protocol in the alloted time. I don't think one can expect that
they should infer that a requirement is satisfied based on
a few hints here and there. If a requirement is intended
to be satisfied, then it should be clearly stated how. At
best, this bullet and the previous statement would
rate as a rather deep underspecification on this
requirement.

> I misunderstood the meaning of multiple dormant modes such that it
> would mean multiple dormancy states, e.g., Active/Sniff/Hold/Park
> modes in the case of Bluetooth.  Also, I had been thinking that
> time-slotted paging at L3 only relates to the following requirement,
> and that it is weaker than other requirements since it uses SHOULD NOT
> instead of MUST NOT.
>
> 4.13.   Future L3 Paging Support
>
>    Recognizing that future dormant mode and wireless link protocols
may
>    be designed that more efficiently utilize IP, the IP paging
protocol
>    SHOULD NOT require L2 support for paging.
>
> I guess this requirement seems to have been weighted higher during the
> judgement process.
>

It was not a first priority requirement, but it was deemed important.
As I said in SLC, we went through a process of normalization
on our comparison criteria, and some proposals ranked higher
on certain requirements than others.

Would you find it satisfactory if, as Jari suggested, some text
is inserted into the assessment draft explaining how the final
decision was made?

            jak


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


From seamoby-admin@ietf.org  Sat Dec 22 12:14:38 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00987
	for <seamoby-archive@odin.ietf.org>; Sat, 22 Dec 2001 12:14:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20990;
	Sat, 22 Dec 2001 12:02:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20962
	for <seamoby@optimus.ietf.org>; Sat, 22 Dec 2001 12:02:31 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00838
	for <seamoby@ietf.org>; Sat, 22 Dec 2001 12:02:27 -0500 (EST)
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 fBMH1IUq004696;
	Sat, 22 Dec 2001 12:01:18 -0500 (EST)
Received: from localhost (tari.research.telcordia.com [207.3.232.66])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id MAA13407;
	Sat, 22 Dec 2001 12:01:11 -0500 (EST)
Date: Sat, 22 Dec 2001 11:00:10 -0500
To: James Kempf <kempf@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, seamoby@ietf.org
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Message-ID: <20011222160010.GA983@catfish>
Mail-Followup-To: James Kempf <kempf@docomolabs-usa.com>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>, seamoby@ietf.org
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <033301c18a73$44673090$7e6015ac@T23KEMPF> <20011221230244.GA1194@catfish> <002f01c18aae$55984670$8e6015ac@T23KEMPF>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <002f01c18aae$55984670$8e6015ac@T23KEMPF>
User-Agent: Mutt/1.3.24i
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20000414(IM141)
Lines: 54
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Jim,

I understand the reason of the ratings for draft-ohba on the
requirements that were said to be focused during the judgement phase.

But it is still not clear why draft-renker is selected even based on
the focused requirements, since the rating for draft-renker on each of 
those requirements are not the highest (see below).  


   |------------|------------|-------------|-------------|------------|
   |            | Ref. [3]   | Ref. [4]    |    Refs.    | Ref. [5]   |
   |            |            |             |-------------|            |
   |            |            |             | [6]     [7] |            |
   |------------|------------|-------------|-------------|------------|


   (snip)

   |    4.6     |            |             |             |            |
   | Multiple   |            |             |  4/2     1  |            |
   | Dormant    |    2       |     1       |             |     2      |
   |  Modes     |            |             |             |            | 
   |------------|------------|-------------|-------------|------------|

   (snip)

   |    4.7     |            |             |             |            |
   |Independence|            |             |  1       4  |            |
   | of Mobility|    4       |     3       |             |     4      |
   | Protocols  |            |             |             |            |
   |------------|------------|-------------|-------------|------------|

   (snip)

   |    4.12    |            |             |             |            |
   | Orthogonal-|            |             |  4       4  |            |
   | ity of PA  |     4      |     1       |             |     2      |
   | and subnets|            |             |             |            |
   |------------|------------|-------------|-------------|------------| 

   (snip)


> Would you find it satisfactory if, as Jari suggested, some text
> is inserted into the assessment draft explaining how the final
> decision was made?
> 
>             jak

Yes.

Thanks,
Yoshihiro Ohba

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


From seamoby-admin@ietf.org  Wed Dec 26 16:39:09 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20887
	for <seamoby-archive@odin.ietf.org>; Wed, 26 Dec 2001 16:39:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06399;
	Wed, 26 Dec 2001 16:18:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06368
	for <seamoby@optimus.ietf.org>; Wed, 26 Dec 2001 16:18:31 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20741
	for <seamoby@ietf.org>; Wed, 26 Dec 2001 16:18:29 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBQLHU820530;
	Wed, 26 Dec 2001 13:17:30 -0800 (PST)
Message-ID: <01e201c18e52$807c5960$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <seamoby@ietf.org>
References: <20011221000542.GE1492@catfish> <021401c18a56$97540110$7e6015ac@T23KEMPF> <20011221203645.GD709@catfish> <033301c18a73$44673090$7e6015ac@T23KEMPF> <20011221230244.GA1194@catfish> <002f01c18aae$55984670$8e6015ac@T23KEMPF> <20011222160010.GA983@catfish>
Subject: Re: [Seamoby] comments on the paging protocol assessment draft
Date: Wed, 26 Dec 2001 13:15:53 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Yoshi,

> But it is still not clear why draft-renker is selected even based on
> the focused requirements, since the rating for draft-renker on each of
> those requirements are not the highest (see below).
>
>
>
|------------|------------|-------------|-------------|------------|
>    |            | Ref. [3]   | Ref. [4]    |    Refs.    | Ref. [5]
|
>    |            |            |             |-------------|
|
>    |            |            |             | [6]     [7] |
|
>
|------------|------------|-------------|-------------|------------|
>
>
>    (snip)
>
>    |    4.6     |            |             |             |
|
>    | Multiple   |            |             |  4/2     1  |
|
>    | Dormant    |    2       |     1       |             |     2
|
>    |  Modes     |            |             |             |
|
>
|------------|------------|-------------|-------------|------------|
>
>    (snip)
>

As I mentioned, this was not a top priorty requirement and was
not discussed during the decision phase. However, if you
want an opinion, as the assessment draft stated, draft-ohba
tied support for multiple dormant modes to 802.11 power
management, a specific link layer type, in Appendix A.
Draft-renker had nothing on this requirement, as the assessment
indicated.
What the requirement was really getting at was support for
time-slotted paging, and perhaps the requirement wording should have
been
more clear in this respect. Draft-sarikaya did an excellent job of
discussing time-slotted paging, but, unfortunately, as I discussed in
my response to Behcet, the entire design was predicated
on a protocol that was not yet through reqirements phase in
another working group. Something like the time-slotted
paging support in draft-sarikaya is what is needed in
the final protocol.

As a metacomment, this requirement represents exactly the
difficulty that the assesement team and the decision
team had with regard to selecting one of these drafts
as the basis for further work. Each draft had particular
aspects of it that were well thought out and recommended
themselves for inclusion in the final result, but none of
the drafts exhibited the maturity of implementation
and design that immediately suggested it as
the only possible candidate for selection, and some drafts had
particular aspects that mitigated strongly against
selection.

>    |    4.7     |            |             |             |
|
>    |Independence|            |             |  1       4  |
|
>    | of Mobility|    4       |     3       |             |     4
|
>    | Protocols  |            |             |             |
|
>
|------------|------------|-------------|-------------|------------|
>
>    (snip)

In this case, draft-renker was viewed as having overspecified the
requirement.
Overspecification is not necessarily negative, since getting it to
match the requirements means that things only need to be taken out, and
that may often simplify doing a final design, because the choices and
their consequences are clear, whereas, if a single choice is presented,
the consequences of the rejected choices may not be so clear. Of course,
other things being equal, a design that exactly meets the requirements
and exhibits the kind of maturity of design and implementation
mentioned above is preferable.

>
>    |    4.12    |            |             |             |
|
>    | Orthogonal-|            |             |  4       4  |
|
>    | ity of PA  |     4      |     1       |             |     2
|
>    | and subnets|            |             |             |
|
>
|------------|------------|-------------|-------------|------------|
>
>    (snip)
>

The justification for the classification given to draft-renker
on Requirement 4.12, the orthogonality of PA subnets (pg. 8 of the
assessment draft)
indicated to me that the rating of 1 was unfair. The justification has
to
do with an obscure use of the TMSI for paging. Perhaps this was a typo
or
something the assessment team overlooked in the process
of performing the normalization. As the diagram on pg. 13 of
draft-renker
clearly shows, the protocol is designed to support mapping of
multiple subnets to a paging area, which is controlled by the paging
agent.
This is in contrast to draft-ohba, where support for multiple
subnets was only briefly mentioned, almost as an afterthought.
At worst, draft-renker rates a very strong 2 on this requirement.

>
> > Would you find it satisfactory if, as Jari suggested, some text
> > is inserted into the assessment draft explaining how the final
> > decision was made?
> >
> >             jak
>
> Yes.
>

I will attempt to come up with some text that describes
the decision phase.

            jak



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


From seamoby-admin@ietf.org  Fri Dec 28 11:57:40 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09537
	for <seamoby-archive@odin.ietf.org>; Fri, 28 Dec 2001 11:57:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27016;
	Fri, 28 Dec 2001 11:37:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26985
	for <seamoby@optimus.ietf.org>; Fri, 28 Dec 2001 11:37:25 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09416
	for <seamoby@ietf.org>; Fri, 28 Dec 2001 11:37:20 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126])
	by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id fBSGasS17086
	for <seamoby@ietf.org>; Fri, 28 Dec 2001 08:36:54 -0800 (PST)
Message-ID: <001401c18fbd$a2d56710$7e6015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <seamoby@ietf.org>
Date: Fri, 28 Dec 2001 08:35:18 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] CT Requirements Draft
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting  <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit



> Last call is just about to expire on the CT requirements
> draft, if it hasn't already. I have only three
> comments:
> 
> 1) Use of the term "microflow"
> This term generated comment from the IESG in
> the CT problem statement draft. I think it might
> be worthwhile substituting another term. I
> think just the term "flow" should be sufficient.
> 
> 2) Section 5.2
> I think this section should be removed since
> I believe there has been no comment
> from our AD on this. 
> 
> 3) What happens when CT fails?
> There are no requirements currently about
> what to do when CT fails. By "fails"
> I mean that the target AR is unable
> to interpret the transferred context.
> 
> There are some other minor points that
> I think could use work, but I don't
> think they are worthwhile holding
> up the draft.
> 
>             jak
> 
> 


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


