From mailman-admin@ietf.org  Sun Dec  1 11:18:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09359
	for <seamoby-archive@lists.ietf.org>; Sun, 1 Dec 2002 11:18:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB1GKbv22217
	for <seamoby-archive@lists.ietf.org>; Sun, 1 Dec 2002 11:20:37 -0500
Date: Sun, 01 Dec 2002 11:20:37 -0500
Message-ID: <20021201162037.8899.44928.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: seamoby-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, seamoby-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              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.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for seamoby-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
seamoby@ietf.org                         Zzch      
https://www1.ietf.org/mailman/options/seamoby/seamoby-archive%40lists.ietf.org


From seamoby-admin@ietf.org  Mon Dec  2 10:07:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18260
	for <seamoby-archive@lists.ietf.org>; Mon, 2 Dec 2002 10:07:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2F8ev04636;
	Mon, 2 Dec 2002 10:08:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2F7Cv04305
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 10:07:12 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18125
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 10:04:18 -0500 (EST)
From: Dirk.Trossen@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gB2F7BU20880
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 09:07:11 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5eeae86ee0ac12f255079@davir02nok.americas.nokia.com>;
 Mon, 2 Dec 2002 09:07:07 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Dec 2002 07:07:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29A14.79AFD424"
Subject: RE: [Seamoby] My opinion about CARD
Date: Mon, 2 Dec 2002 10:07:05 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB0124608772C5@bsebe001.americas.nokia.com>
Thread-Topic: [Seamoby] My opinion about CARD
Thread-Index: AcKYEQfrhefa63oWT8yJgS4uC0BnhgCArRYA
To: <xmwang@sait.samsung.co.kr>, <eunsoo@nec-labs.com>, <Seamoby@ietf.org>
X-OriginalArrivalTime: 02 Dec 2002 15:07:06.0393 (UTC) FILETIME=[7A6F4090:01C29A14]
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C29A14.79AFD424
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
We went through the phase of problem statement and requirement for quite =
a while. Re-iterating such "opinion" discussions
simply prevents us from going after the solutions. We had discussions on =
use cases, integration in mobility protocols, and so forth, but
I did not see your opinion at that time. As for now, we are in the phase =
of building a solution for something that had been identified as
indeed being necessary.=20
=20
Dirk
=20

-----Original Message-----
From: ext Xiaoming Wang [mailto:xmwang@sait.samsung.co.kr]
Sent: Friday, November 29, 2002 8:13 PM
To: Eunsoo Shim; Seamoby@ietf.org
Subject: Re: [Seamoby] My opinion about CARD


Thank you. I agree with you that there exist cases where we can use =
CARD. But is it enough for a protocol? Is it necessary to improve =
handoff performance?=20
I think we use a protocol to solve a common problem, not special cases.=20
=20
From draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot =
of different cases (MN types and TAR selection algrithm location) it =
should take into consideration. It is difficult for a protocol to =
include all the cases. So why not leaving it to implement consideration =
and solving it case by case?
=20
Above is my humble opinion. And I'm sorry for bringing noise into this =
community. But I want to clear my mind. And I think it can help me to =
know what we should do and why we should do it.
=20
Xiaoming Wang


----- Original Message -----=20
From: Eunsoo  <mailto:eunsoo@nec-labs.com> Shim=20
To: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  ; Seamoby@ietf.org =

Sent: Friday, November 29, 2002 5:07 AM
Subject: Re: [Seamoby] My opinion about CARD

Hi, Xiaoming,
=20
Depending on the cell structure/topology, there can be multiple CARs in =
handoffs. Also in wireless overlay networks, there are multiple CARs =
typically.
The CAR discovery issue draft describes some of the cases the CARD =
protocol is useful for. You can see that the CARD protocol is useful not =
only for FMIP. So the requirements draft says the CARD protocol should =
be independent of any mobility management protocol.
Regards,
=20
Eunsoo

----- Original Message -----=20
From: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr> =20
To: Seamoby@ietf.org=20
Sent: Wednesday, November 27, 2002 8:07 PM
Subject: [Seamoby] My opinion about CARD

Hi all,=20
=20
I only can see a few situations where CARD can be used. In most cases, =
handover only involves one CAR. So is CARD enough to be a protocol? IMHO =
it is better to integrate it in other mobility protocols such as FMIP =
since it is not common for all cases.=20
=20
=20
Xiaoming Wang
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea
=20
Phone: 82-31-280-9615
Fax:     82-31-280-9569
EMail:   stone_wang76@hotmail.com (preferred)
            xmwang@sait.samsung.co.kr
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D



------_=_NextPart_001_01C29A14.79AFD424
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

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


<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>We=20
went through the phase of problem statement and requirement for quite a =
while.=20
Re-iterating such "opinion" discussions</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>simply=20
prevents us from going after the solutions. We had discussions on use =
cases,=20
integration in mobility protocols, and so forth, but</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>I did=20
not see your opinion at that time. As for now, we are in the phase of =
building a=20
solution for something that had been identified as</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>indeed=20
being necessary. </FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2>Dirk</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002></SPAN><SPAN =
class=3D415470115-02122002><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> ext Xiaoming Wang=20
  [mailto:xmwang@sait.samsung.co.kr]<BR><B>Sent:</B> Friday, November =
29, 2002=20
  8:13 PM<BR><B>To:</B> Eunsoo Shim; Seamoby@ietf.org<BR><B>Subject:</B> =
Re:=20
  [Seamoby] My opinion about CARD<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Thank you. I agree with you that =
there exist=20
  cases where we can use CARD. But is it enough for a protocol? Is it =
necessary=20
  to improve handoff performance? </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>I think we use a protocol to solve a =
common=20
  problem, not special cases. </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>From =
draft-ietf-seamoby-card-protocol-00.txt, we=20
  can see there are a lot of different cases (MN types and TAR selection =

  algrithm location)&nbsp;it should take into consideration. It is =
difficult for=20
  a protocol to include all the cases. So why not leaving it to =
implement=20
  consideration and&nbsp;solving it case by case?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Above is my humble opinion. And I'm =
sorry for=20
  bringing noise into this community. But I want to clear my mind. And I =
think=20
  it can help me to know what we should do and why we should do =
it.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV>Xiaoming Wang<BR></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Deunsoo@nec-labs.com =
href=3D"mailto:eunsoo@nec-labs.com">Eunsoo=20
    Shim</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dxmwang@sait.samsung.co.kr=20
    href=3D"mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> ; <A=20
    title=3DSeamoby@ietf.org =
href=3D"mailto:Seamoby@ietf.org">Seamoby@ietf.org</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, November 29, =
2002 5:07=20
    AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Seamoby] My =
opinion about=20
    CARD</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=3DArial size=3D2>Hi, Xiaoming,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV>
    <DIV><FONT face=3DArial size=3D2>Depending on the cell =
structure/topology, there=20
    can be multiple CARs in handoffs. Also in wireless overlay networks, =
there=20
    are multiple CARs typically.</FONT></DIV></DIV>
    <DIV><FONT face=3DArial size=3D2>The CAR discovery issue draft =
describes some of=20
    the cases the CARD protocol is useful for. You can see that the CARD =

    protocol is useful not only for FMIP. So the requirements draft says =
the=20
    CARD protocol should be independent of any mobility management=20
    protocol.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Eunsoo</FONT></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>
      <DIV=20
      style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
      <A title=3Dxmwang@sait.samsung.co.kr=20
      href=3D"mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DSeamoby@ietf.org=20
      href=3D"mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, November =
27, 2002=20
      8:07 PM</DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Seamoby] My =
opinion about=20
      CARD</DIV>
      <DIV><BR></DIV>
      <DIV><FONT face=3DArial size=3D2>Hi all, </FONT></DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>I only can see a few situations =
where CARD=20
      can be used. In most cases, handover only involves one CAR. So is =
CARD=20
      enough to be a protocol? IMHO&nbsp;it is better to integrate it in =
other=20
      mobility protocols such as FMIP&nbsp;since it is not common for =
all cases.=20
      </FONT></DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>Xiaoming=20
      =
Wang<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Network=20
      Protocol Technical Group, i-Networking lab<BR>Samsung Advanced =
Institute=20
      of Technology, South Korea</FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>Phone:=20
      82-31-280-9615<BR>Fax:&nbsp;&nbsp;&nbsp;&nbsp;=20
      82-31-280-9569<BR>EMail:&nbsp;&nbsp; <A=20
      =
href=3D"mailto:stone_wang76@hotmail.com">stone_wang76@hotmail.com</A>=20
      =
(preferred)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
      <A=20
      =
href=3D"mailto:xmwang@sait.samsung.co.kr">xmwang@sait.samsung.co.kr</A><B=
R>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE></BODY></HTML>

------_=_NextPart_001_01C29A14.79AFD424--
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby


From mailnull@www1.ietf.org  Mon Dec  2 10:07:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18304
	for <seamoby-archive@odin.ietf.org>; Mon, 2 Dec 2002 10:07:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2F9xh04706
	for seamoby-archive@odin.ietf.org; Mon, 2 Dec 2002 10:09:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2F9xv04703
	for <seamoby-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 10:09:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18263
	for <seamoby-web-archive@ietf.org>; Mon, 2 Dec 2002 10:07:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2F8ev04636;
	Mon, 2 Dec 2002 10:08:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2F7Cv04305
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 10:07:12 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18125
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 10:04:18 -0500 (EST)
From: Dirk.Trossen@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gB2F7BU20880
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 09:07:11 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5eeae86ee0ac12f255079@davir02nok.americas.nokia.com>;
 Mon, 2 Dec 2002 09:07:07 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Dec 2002 07:07:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29A14.79AFD424"
Subject: RE: [Seamoby] My opinion about CARD
Date: Mon, 2 Dec 2002 10:07:05 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB0124608772C5@bsebe001.americas.nokia.com>
Thread-Topic: [Seamoby] My opinion about CARD
Thread-Index: AcKYEQfrhefa63oWT8yJgS4uC0BnhgCArRYA
To: <xmwang@sait.samsung.co.kr>, <eunsoo@nec-labs.com>, <Seamoby@ietf.org>
X-OriginalArrivalTime: 02 Dec 2002 15:07:06.0393 (UTC) FILETIME=[7A6F4090:01C29A14]
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C29A14.79AFD424
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
We went through the phase of problem statement and requirement for quite =
a while. Re-iterating such "opinion" discussions
simply prevents us from going after the solutions. We had discussions on =
use cases, integration in mobility protocols, and so forth, but
I did not see your opinion at that time. As for now, we are in the phase =
of building a solution for something that had been identified as
indeed being necessary.=20
=20
Dirk
=20

-----Original Message-----
From: ext Xiaoming Wang [mailto:xmwang@sait.samsung.co.kr]
Sent: Friday, November 29, 2002 8:13 PM
To: Eunsoo Shim; Seamoby@ietf.org
Subject: Re: [Seamoby] My opinion about CARD


Thank you. I agree with you that there exist cases where we can use =
CARD. But is it enough for a protocol? Is it necessary to improve =
handoff performance?=20
I think we use a protocol to solve a common problem, not special cases.=20
=20
From draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot =
of different cases (MN types and TAR selection algrithm location) it =
should take into consideration. It is difficult for a protocol to =
include all the cases. So why not leaving it to implement consideration =
and solving it case by case?
=20
Above is my humble opinion. And I'm sorry for bringing noise into this =
community. But I want to clear my mind. And I think it can help me to =
know what we should do and why we should do it.
=20
Xiaoming Wang


----- Original Message -----=20
From: Eunsoo  <mailto:eunsoo@nec-labs.com> Shim=20
To: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  ; Seamoby@ietf.org =

Sent: Friday, November 29, 2002 5:07 AM
Subject: Re: [Seamoby] My opinion about CARD

Hi, Xiaoming,
=20
Depending on the cell structure/topology, there can be multiple CARs in =
handoffs. Also in wireless overlay networks, there are multiple CARs =
typically.
The CAR discovery issue draft describes some of the cases the CARD =
protocol is useful for. You can see that the CARD protocol is useful not =
only for FMIP. So the requirements draft says the CARD protocol should =
be independent of any mobility management protocol.
Regards,
=20
Eunsoo

----- Original Message -----=20
From: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr> =20
To: Seamoby@ietf.org=20
Sent: Wednesday, November 27, 2002 8:07 PM
Subject: [Seamoby] My opinion about CARD

Hi all,=20
=20
I only can see a few situations where CARD can be used. In most cases, =
handover only involves one CAR. So is CARD enough to be a protocol? IMHO =
it is better to integrate it in other mobility protocols such as FMIP =
since it is not common for all cases.=20
=20
=20
Xiaoming Wang
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea
=20
Phone: 82-31-280-9615
Fax:     82-31-280-9569
EMail:   stone_wang76@hotmail.com (preferred)
            xmwang@sait.samsung.co.kr
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D



------_=_NextPart_001_01C29A14.79AFD424
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

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


<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>We=20
went through the phase of problem statement and requirement for quite a =
while.=20
Re-iterating such "opinion" discussions</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>simply=20
prevents us from going after the solutions. We had discussions on use =
cases,=20
integration in mobility protocols, and so forth, but</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>I did=20
not see your opinion at that time. As for now, we are in the phase of =
building a=20
solution for something that had been identified as</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =
size=3D2>indeed=20
being necessary. </FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D415470115-02122002><FONT face=3DArial color=3D#0000ff =

size=3D2>Dirk</FONT></SPAN></DIV>
<DIV><SPAN class=3D415470115-02122002></SPAN><SPAN =
class=3D415470115-02122002><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> ext Xiaoming Wang=20
  [mailto:xmwang@sait.samsung.co.kr]<BR><B>Sent:</B> Friday, November =
29, 2002=20
  8:13 PM<BR><B>To:</B> Eunsoo Shim; Seamoby@ietf.org<BR><B>Subject:</B> =
Re:=20
  [Seamoby] My opinion about CARD<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Thank you. I agree with you that =
there exist=20
  cases where we can use CARD. But is it enough for a protocol? Is it =
necessary=20
  to improve handoff performance? </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>I think we use a protocol to solve a =
common=20
  problem, not special cases. </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>From =
draft-ietf-seamoby-card-protocol-00.txt, we=20
  can see there are a lot of different cases (MN types and TAR selection =

  algrithm location)&nbsp;it should take into consideration. It is =
difficult for=20
  a protocol to include all the cases. So why not leaving it to =
implement=20
  consideration and&nbsp;solving it case by case?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Above is my humble opinion. And I'm =
sorry for=20
  bringing noise into this community. But I want to clear my mind. And I =
think=20
  it can help me to know what we should do and why we should do =
it.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV>Xiaoming Wang<BR></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Deunsoo@nec-labs.com =
href=3D"mailto:eunsoo@nec-labs.com">Eunsoo=20
    Shim</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dxmwang@sait.samsung.co.kr=20
    href=3D"mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> ; <A=20
    title=3DSeamoby@ietf.org =
href=3D"mailto:Seamoby@ietf.org">Seamoby@ietf.org</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, November 29, =
2002 5:07=20
    AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Seamoby] My =
opinion about=20
    CARD</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=3DArial size=3D2>Hi, Xiaoming,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV>
    <DIV><FONT face=3DArial size=3D2>Depending on the cell =
structure/topology, there=20
    can be multiple CARs in handoffs. Also in wireless overlay networks, =
there=20
    are multiple CARs typically.</FONT></DIV></DIV>
    <DIV><FONT face=3DArial size=3D2>The CAR discovery issue draft =
describes some of=20
    the cases the CARD protocol is useful for. You can see that the CARD =

    protocol is useful not only for FMIP. So the requirements draft says =
the=20
    CARD protocol should be independent of any mobility management=20
    protocol.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Eunsoo</FONT></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>
      <DIV=20
      style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
      <A title=3Dxmwang@sait.samsung.co.kr=20
      href=3D"mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DSeamoby@ietf.org=20
      href=3D"mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, November =
27, 2002=20
      8:07 PM</DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Seamoby] My =
opinion about=20
      CARD</DIV>
      <DIV><BR></DIV>
      <DIV><FONT face=3DArial size=3D2>Hi all, </FONT></DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>I only can see a few situations =
where CARD=20
      can be used. In most cases, handover only involves one CAR. So is =
CARD=20
      enough to be a protocol? IMHO&nbsp;it is better to integrate it in =
other=20
      mobility protocols such as FMIP&nbsp;since it is not common for =
all cases.=20
      </FONT></DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>Xiaoming=20
      =
Wang<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Network=20
      Protocol Technical Group, i-Networking lab<BR>Samsung Advanced =
Institute=20
      of Technology, South Korea</FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>Phone:=20
      82-31-280-9615<BR>Fax:&nbsp;&nbsp;&nbsp;&nbsp;=20
      82-31-280-9569<BR>EMail:&nbsp;&nbsp; <A=20
      =
href=3D"mailto:stone_wang76@hotmail.com">stone_wang76@hotmail.com</A>=20
      =
(preferred)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
      <A=20
      =
href=3D"mailto:xmwang@sait.samsung.co.kr">xmwang@sait.samsung.co.kr</A><B=
R>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE></BODY></HTML>

------_=_NextPart_001_01C29A14.79AFD424--
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby



From seamoby-admin@ietf.org  Mon Dec  2 14:17:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04881
	for <seamoby-archive@lists.ietf.org>; Mon, 2 Dec 2002 14:17:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2JIrv24696;
	Mon, 2 Dec 2002 14:18:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2JHmv24608
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 14:17:48 -0500
Received: from motgate.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04706
	for <seamoby@ietf.org>; Mon, 2 Dec 2002 14:14:54 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id gB2JHgQW011300
	for <seamoby@ietf.org>; Mon, 2 Dec 2002 12:17:42 -0700 (MST)
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA24338 for <seamoby@ietf.org>; Mon, 2 Dec 2002 12:17:42 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD8XK1HP>; Mon, 2 Dec 2002 13:17:42 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B08AD5B4C@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: seamoby@ietf.org
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Date: Mon, 2 Dec 2002 13:17:21 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] PPP context transfer
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hi all,

I just submitted a draft on PPP context transfer; hopefully
it will show up on the mailing list soon. Although
the context transfer protocol design is in a work in progress,
I felt that the PPP provides a good practical example for context
transfer which shows significant benefits for a low bandwidth 
environment. I tried to leave most of the details of the actual
transfer process out until CTP work is more complete.

Please find the title and abstract below.

Regards,

Madjid

Title:Enhanced PPP link re-establishment using context transfer

Abstract 

Many of today's networks use PPP as a means of providing access 
    links to remote users. In case a PPP user is mobile and performs a 
    subnet handover, it needs to tear down and re-establish of its PPP 
    link with the network. PPP link re-establishment is an elaborate 
    procedure involving multiple messages. This will lead in an extended
service 
    disruption as due to the round trip time involved in the messaging 
    as well extensive radio bandwidth usage. Of this reason, we 
    consider PPP to be a prime candidate for context transfer. 
    The proposal in this document can reduce the number of PPP 
    establishment messages by 50%-100. Furthermore, it will save 
    significant amount of time in PPP state machine transitions, due 
    to the multiphase nature of PPP. Reliability and timing issues of 
    PPP context transfer are also discussed. 
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby


From mailnull@www1.ietf.org  Mon Dec  2 14:17:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04902
	for <seamoby-archive@odin.ietf.org>; Mon, 2 Dec 2002 14:17:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2JKB124842
	for seamoby-archive@odin.ietf.org; Mon, 2 Dec 2002 14:20:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2JKBv24839
	for <seamoby-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 14:20:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04895
	for <seamoby-web-archive@ietf.org>; Mon, 2 Dec 2002 14:17:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2JIrv24696;
	Mon, 2 Dec 2002 14:18:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2JHmv24608
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 14:17:48 -0500
Received: from motgate.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04706
	for <seamoby@ietf.org>; Mon, 2 Dec 2002 14:14:54 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id gB2JHgQW011300
	for <seamoby@ietf.org>; Mon, 2 Dec 2002 12:17:42 -0700 (MST)
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA24338 for <seamoby@ietf.org>; Mon, 2 Dec 2002 12:17:42 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD8XK1HP>; Mon, 2 Dec 2002 13:17:42 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B08AD5B4C@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: seamoby@ietf.org
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Date: Mon, 2 Dec 2002 13:17:21 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] PPP context transfer
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hi all,

I just submitted a draft on PPP context transfer; hopefully
it will show up on the mailing list soon. Although
the context transfer protocol design is in a work in progress,
I felt that the PPP provides a good practical example for context
transfer which shows significant benefits for a low bandwidth 
environment. I tried to leave most of the details of the actual
transfer process out until CTP work is more complete.

Please find the title and abstract below.

Regards,

Madjid

Title:Enhanced PPP link re-establishment using context transfer

Abstract 

Many of today's networks use PPP as a means of providing access 
    links to remote users. In case a PPP user is mobile and performs a 
    subnet handover, it needs to tear down and re-establish of its PPP 
    link with the network. PPP link re-establishment is an elaborate 
    procedure involving multiple messages. This will lead in an extended
service 
    disruption as due to the round trip time involved in the messaging 
    as well extensive radio bandwidth usage. Of this reason, we 
    consider PPP to be a prime candidate for context transfer. 
    The proposal in this document can reduce the number of PPP 
    establishment messages by 50%-100. Furthermore, it will save 
    significant amount of time in PPP state machine transitions, due 
    to the multiphase nature of PPP. Reliability and timing issues of 
    PPP context transfer are also discussed. 
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby



From seamoby-admin@ietf.org  Mon Dec  2 15:27:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08299
	for <seamoby-archive@lists.ietf.org>; Mon, 2 Dec 2002 15:27:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2KTHv29765;
	Mon, 2 Dec 2002 15:29:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2KS7v29705
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 15:28:07 -0500
Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08179
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 15:25:11 -0500 (EST)
Received: from mothost.mot.com (mothost.mot.com [129.188.137.101])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id gB2KRiRN018819
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 13:27:44 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id NAA26247 for <Seamoby@ietf.org>; Mon, 2 Dec 2002 13:27:59 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6LR661>; Mon, 2 Dec 2002 14:27:59 -0600
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E07862600@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: "'Xiaoming Wang'" <xmwang@sait.samsung.co.kr>,
        Eunsoo Shim
	 <eunsoo@nec-labs.com>, Seamoby@ietf.org
Subject: RE: [Seamoby] My opinion about CARD
Date: Mon, 2 Dec 2002 14:27:56 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29A41.4C261BF2"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

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_01C29A41.4C261BF2
Content-Type: text/plain;
	charset="gb2312"

Hello Xiaoming Wang,
Please find my inline reply.
Regards,
Ajoy

-----Original Message-----
From: Xiaoming Wang [mailto:xmwang@sait.samsung.co.kr]
Sent: Friday, November 29, 2002 7:13 PM
To: Eunsoo Shim; Seamoby@ietf.org
Subject: Re: [Seamoby] My opinion about CARD


Thank you. I agree with you that there exist cases where we can use CARD. But is it enough for a protocol? Is it necessary to improve handoff performance? 
I think we use a protocol to solve a common problem, not special cases. 
 
From draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot of different cases (MN types and TAR selection algrithm location) it should take into consideration. 

AJOY-> In the proposed draft, we have identified various scenarios of CARD deployment. This does not mean 
that we will define multiple protocols for CARD.  
 
 It is difficult for a protocol to include all the cases. 

AJOY-> Why do you think it is difficult to solve all the proposed cases using 
single protocol. Could you please elaborate? 
 
 So why not leaving it to implement consideration and solving it case by case?
 
AJOY-> There will be changes between MN-AR as well as AR-AR interface. So,
I am not sure how can we leave this as implementation consideration?
 
Above is my humble opinion. And I'm sorry for bringing noise into this community. 

AJOY-> Your comments are appreciated. 
 
 But I want to clear my mind. And I think it can help me to know what we should do and why we should do it.
 
Xiaoming Wang


----- Original Message ----- 
From: Eunsoo  <mailto:eunsoo@nec-labs.com> Shim 
To: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  ; Seamoby@ietf.org <mailto:Seamoby@ietf.org>  
Sent: Friday, November 29, 2002 5:07 AM
Subject: Re: [Seamoby] My opinion about CARD


Hi, Xiaoming,
 
Depending on the cell structure/topology, there can be multiple CARs in handoffs. Also in wireless overlay networks, there are multiple CARs typically.
The CAR discovery issue draft describes some of the cases the CARD protocol is useful for. You can see that the CARD protocol is useful not only for FMIP. So the requirements draft says the CARD protocol should be independent of any mobility management protocol.
Regards,
 
Eunsoo

----- Original Message ----- 
From: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  
To: Seamoby@ietf.org <mailto:Seamoby@ietf.org>  
Sent: Wednesday, November 27, 2002 8:07 PM
Subject: [Seamoby] My opinion about CARD

Hi all, 
 
I only can see a few situations where CARD can be used. In most cases, handover only involves one CAR. So is CARD enough to be a protocol? IMHO it is better to integrate it in other mobility protocols such as FMIP since it is not common for all cases. 
 
 
Xiaoming Wang
=========================================================
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea
 
Phone: 82-31-280-9615
Fax:     82-31-280-9569
EMail:   stone_wang76@hotmail.com <mailto:stone_wang76@hotmail.com>  (preferred)
            xmwang@sait.samsung.co.kr <mailto:xmwang@sait.samsung.co.kr> 
=========================================================



------_=_NextPart_001_01C29A41.4C261BF2
Content-Type: text/html;
	charset="gb2312"

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


<META content="MSHTML 5.50.4728.2300" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=665231720-02122002><FONT face=Arial color=#0000ff size=2><FONT 
color=#000000 size=3>Hello Xiaoming Wang,</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT face=Arial>Please find my inline 
reply.</FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT 
face=Arial>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT face=Arial>Ajoy</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Xiaoming Wang 
  [mailto:xmwang@sait.samsung.co.kr]<BR><B>Sent:</B> Friday, November 29, 2002 
  7:13 PM<BR><B>To:</B> Eunsoo Shim; Seamoby@ietf.org<BR><B>Subject:</B> Re: 
  [Seamoby] My opinion about CARD<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>Thank you. I agree with you that there exist 
  cases where we can use CARD. But is it enough for a protocol? Is it necessary 
  to improve handoff performance? </FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2>I think we use a protocol to solve a common 
  problem, not special cases.&nbsp;<BR></FONT></FONT><FONT face=Arial><FONT 
  size=2><SPAN class=665231720-02122002>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2>From 
  draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot of 
  different cases (MN types and TAR selection algrithm location)&nbsp;it should 
  take into consideration.&nbsp;<BR><BR><SPAN class=665231720-02122002><FONT 
  color=#0000ff>AJOY-&gt; In the proposed draft, we have identified various 
  scenarios of CARD deployment. This does not 
  mean&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN class=665231720-02122002><FONT 
  color=#0000ff>that we will define multiple&nbsp;protocols&nbsp;for CARD. 
  </FONT>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=665231720-02122002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN>It is difficult for a protocol to 
  include all the cases.&nbsp;<BR><BR><SPAN class=665231720-02122002><FONT 
  color=#0000ff>AJOY-&gt;&nbsp;Why do you think it is difficult to&nbsp;solve 
  all the&nbsp;proposed cases using&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN class=665231720-02122002><FONT 
  color=#0000ff>single protocol.&nbsp;Could&nbsp;you please 
  elaborate?</FONT>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN>So why not leaving it to implement 
  consideration and&nbsp;solving it case by case?</FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=665231720-02122002><FONT face=Arial color=#000080 
  size=2>AJOY-&gt; There will be changes between MN-AR as well as AR-AR 
  interface. So,</FONT></SPAN></DIV>
  <DIV><SPAN class=665231720-02122002><FONT face=Arial color=#000080 size=2>I am 
  not sure how can we leave this as implementation 
  consideration?</FONT></SPAN></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2>Above is my humble opinion. And I'm sorry 
  for bringing noise into this community.&nbsp;<BR><BR><SPAN 
  class=665231720-02122002><FONT color=#0000ff>AJOY-&gt;&nbsp;Your comments are 
  appreciated. </FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=665231720-02122002>&nbsp;</SPAN>But I 
  want to clear my mind. And I think it can help me to know what we should do 
  and why we should do it.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV>Xiaoming Wang<BR></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=eunsoo@nec-labs.com href="mailto:eunsoo@nec-labs.com">Eunsoo 
    Shim</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=xmwang@sait.samsung.co.kr 
    href="mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> ; <A 
    title=Seamoby@ietf.org href="mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, November 29, 2002 5:07 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Seamoby] My opinion about 
    CARD</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial 
    color=#0000ff size=2></FONT><BR></DIV>
    <DIV><FONT face=Arial size=2>Hi, Xiaoming,</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV>
    <DIV><FONT face=Arial size=2>Depending on the cell structure/topology, there 
    can be multiple CARs in handoffs. Also in wireless overlay networks, there 
    are multiple CARs typically.</FONT></DIV></DIV>
    <DIV><FONT face=Arial size=2>The CAR discovery issue draft describes some of 
    the cases the CARD protocol is useful for. You can see that the CARD 
    protocol is useful not only for FMIP. So the requirements draft says the 
    CARD protocol should be independent of any mobility management 
    protocol.</FONT></DIV>
    <DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Eunsoo</FONT></DIV>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
      <DIV 
      style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
      <A title=xmwang@sait.samsung.co.kr 
      href="mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>To:</B> <A title=Seamoby@ietf.org 
      href="mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, November 27, 2002 
      8:07 PM</DIV>
      <DIV style="FONT: 10pt arial"><B>Subject:</B> [Seamoby] My opinion about 
      CARD</DIV>
      <DIV><BR></DIV>
      <DIV><FONT face=Arial size=2>Hi all, </FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>I only can see a few situations where CARD 
      can be used. In most cases, handover only involves one CAR. So is CARD 
      enough to be a protocol? IMHO&nbsp;it is better to integrate it in other 
      mobility protocols such as FMIP&nbsp;since it is not common for all cases. 
      </FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>Xiaoming 
      Wang<BR>=========================================================<BR>Network 
      Protocol Technical Group, i-Networking lab<BR>Samsung Advanced Institute 
      of Technology, South Korea</FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>Phone: 
      82-31-280-9615<BR>Fax:&nbsp;&nbsp;&nbsp;&nbsp; 
      82-31-280-9569<BR>EMail:&nbsp;&nbsp; <A 
      href="mailto:stone_wang76@hotmail.com">stone_wang76@hotmail.com</A> 
      (preferred)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      <A 
      href="mailto:xmwang@sait.samsung.co.kr">xmwang@sait.samsung.co.kr</A><BR>=========================================================<BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C29A41.4C261BF2--
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby


From mailnull@www1.ietf.org  Mon Dec  2 15:28:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08335
	for <seamoby-archive@odin.ietf.org>; Mon, 2 Dec 2002 15:27:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2KUO329847
	for seamoby-archive@odin.ietf.org; Mon, 2 Dec 2002 15:30:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2KUOv29844
	for <seamoby-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 15:30:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08313
	for <seamoby-web-archive@ietf.org>; Mon, 2 Dec 2002 15:27:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2KTHv29765;
	Mon, 2 Dec 2002 15:29:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2KS7v29705
	for <seamoby@optimus.ietf.org>; Mon, 2 Dec 2002 15:28:07 -0500
Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08179
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 15:25:11 -0500 (EST)
Received: from mothost.mot.com (mothost.mot.com [129.188.137.101])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id gB2KRiRN018819
	for <Seamoby@ietf.org>; Mon, 2 Dec 2002 13:27:44 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id NAA26247 for <Seamoby@ietf.org>; Mon, 2 Dec 2002 13:27:59 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6LR661>; Mon, 2 Dec 2002 14:27:59 -0600
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E07862600@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: "'Xiaoming Wang'" <xmwang@sait.samsung.co.kr>,
        Eunsoo Shim
	 <eunsoo@nec-labs.com>, Seamoby@ietf.org
Subject: RE: [Seamoby] My opinion about CARD
Date: Mon, 2 Dec 2002 14:27:56 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29A41.4C261BF2"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

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_01C29A41.4C261BF2
Content-Type: text/plain;
	charset="gb2312"

Hello Xiaoming Wang,
Please find my inline reply.
Regards,
Ajoy

-----Original Message-----
From: Xiaoming Wang [mailto:xmwang@sait.samsung.co.kr]
Sent: Friday, November 29, 2002 7:13 PM
To: Eunsoo Shim; Seamoby@ietf.org
Subject: Re: [Seamoby] My opinion about CARD


Thank you. I agree with you that there exist cases where we can use CARD. But is it enough for a protocol? Is it necessary to improve handoff performance? 
I think we use a protocol to solve a common problem, not special cases. 
 
From draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot of different cases (MN types and TAR selection algrithm location) it should take into consideration. 

AJOY-> In the proposed draft, we have identified various scenarios of CARD deployment. This does not mean 
that we will define multiple protocols for CARD.  
 
 It is difficult for a protocol to include all the cases. 

AJOY-> Why do you think it is difficult to solve all the proposed cases using 
single protocol. Could you please elaborate? 
 
 So why not leaving it to implement consideration and solving it case by case?
 
AJOY-> There will be changes between MN-AR as well as AR-AR interface. So,
I am not sure how can we leave this as implementation consideration?
 
Above is my humble opinion. And I'm sorry for bringing noise into this community. 

AJOY-> Your comments are appreciated. 
 
 But I want to clear my mind. And I think it can help me to know what we should do and why we should do it.
 
Xiaoming Wang


----- Original Message ----- 
From: Eunsoo  <mailto:eunsoo@nec-labs.com> Shim 
To: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  ; Seamoby@ietf.org <mailto:Seamoby@ietf.org>  
Sent: Friday, November 29, 2002 5:07 AM
Subject: Re: [Seamoby] My opinion about CARD


Hi, Xiaoming,
 
Depending on the cell structure/topology, there can be multiple CARs in handoffs. Also in wireless overlay networks, there are multiple CARs typically.
The CAR discovery issue draft describes some of the cases the CARD protocol is useful for. You can see that the CARD protocol is useful not only for FMIP. So the requirements draft says the CARD protocol should be independent of any mobility management protocol.
Regards,
 
Eunsoo

----- Original Message ----- 
From: Xiaoming Wang <mailto:xmwang@sait.samsung.co.kr>  
To: Seamoby@ietf.org <mailto:Seamoby@ietf.org>  
Sent: Wednesday, November 27, 2002 8:07 PM
Subject: [Seamoby] My opinion about CARD

Hi all, 
 
I only can see a few situations where CARD can be used. In most cases, handover only involves one CAR. So is CARD enough to be a protocol? IMHO it is better to integrate it in other mobility protocols such as FMIP since it is not common for all cases. 
 
 
Xiaoming Wang
=========================================================
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea
 
Phone: 82-31-280-9615
Fax:     82-31-280-9569
EMail:   stone_wang76@hotmail.com <mailto:stone_wang76@hotmail.com>  (preferred)
            xmwang@sait.samsung.co.kr <mailto:xmwang@sait.samsung.co.kr> 
=========================================================



------_=_NextPart_001_01C29A41.4C261BF2
Content-Type: text/html;
	charset="gb2312"

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


<META content="MSHTML 5.50.4728.2300" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=665231720-02122002><FONT face=Arial color=#0000ff size=2><FONT 
color=#000000 size=3>Hello Xiaoming Wang,</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT face=Arial>Please find my inline 
reply.</FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT 
face=Arial>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=665231720-02122002><FONT face=Arial>Ajoy</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Xiaoming Wang 
  [mailto:xmwang@sait.samsung.co.kr]<BR><B>Sent:</B> Friday, November 29, 2002 
  7:13 PM<BR><B>To:</B> Eunsoo Shim; Seamoby@ietf.org<BR><B>Subject:</B> Re: 
  [Seamoby] My opinion about CARD<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>Thank you. I agree with you that there exist 
  cases where we can use CARD. But is it enough for a protocol? Is it necessary 
  to improve handoff performance? </FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2>I think we use a protocol to solve a common 
  problem, not special cases.&nbsp;<BR></FONT></FONT><FONT face=Arial><FONT 
  size=2><SPAN class=665231720-02122002>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2>From 
  draft-ietf-seamoby-card-protocol-00.txt, we can see there are a lot of 
  different cases (MN types and TAR selection algrithm location)&nbsp;it should 
  take into consideration.&nbsp;<BR><BR><SPAN class=665231720-02122002><FONT 
  color=#0000ff>AJOY-&gt; In the proposed draft, we have identified various 
  scenarios of CARD deployment. This does not 
  mean&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN class=665231720-02122002><FONT 
  color=#0000ff>that we will define multiple&nbsp;protocols&nbsp;for CARD. 
  </FONT>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=665231720-02122002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN>It is difficult for a protocol to 
  include all the cases.&nbsp;<BR><BR><SPAN class=665231720-02122002><FONT 
  color=#0000ff>AJOY-&gt;&nbsp;Why do you think it is difficult to&nbsp;solve 
  all the&nbsp;proposed cases using&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN class=665231720-02122002><FONT 
  color=#0000ff>single protocol.&nbsp;Could&nbsp;you please 
  elaborate?</FONT>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN>So why not leaving it to implement 
  consideration and&nbsp;solving it case by case?</FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=665231720-02122002><FONT face=Arial color=#000080 
  size=2>AJOY-&gt; There will be changes between MN-AR as well as AR-AR 
  interface. So,</FONT></SPAN></DIV>
  <DIV><SPAN class=665231720-02122002><FONT face=Arial color=#000080 size=2>I am 
  not sure how can we leave this as implementation 
  consideration?</FONT></SPAN></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial><FONT size=2>Above is my humble opinion. And I'm sorry 
  for bringing noise into this community.&nbsp;<BR><BR><SPAN 
  class=665231720-02122002><FONT color=#0000ff>AJOY-&gt;&nbsp;Your comments are 
  appreciated. </FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial><FONT size=2><SPAN 
  class=665231720-02122002>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=665231720-02122002>&nbsp;</SPAN>But I 
  want to clear my mind. And I think it can help me to know what we should do 
  and why we should do it.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV>Xiaoming Wang<BR></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=eunsoo@nec-labs.com href="mailto:eunsoo@nec-labs.com">Eunsoo 
    Shim</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=xmwang@sait.samsung.co.kr 
    href="mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> ; <A 
    title=Seamoby@ietf.org href="mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, November 29, 2002 5:07 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Seamoby] My opinion about 
    CARD</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial 
    color=#0000ff size=2></FONT><BR></DIV>
    <DIV><FONT face=Arial size=2>Hi, Xiaoming,</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV>
    <DIV><FONT face=Arial size=2>Depending on the cell structure/topology, there 
    can be multiple CARs in handoffs. Also in wireless overlay networks, there 
    are multiple CARs typically.</FONT></DIV></DIV>
    <DIV><FONT face=Arial size=2>The CAR discovery issue draft describes some of 
    the cases the CARD protocol is useful for. You can see that the CARD 
    protocol is useful not only for FMIP. So the requirements draft says the 
    CARD protocol should be independent of any mobility management 
    protocol.</FONT></DIV>
    <DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Eunsoo</FONT></DIV>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
      <DIV 
      style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
      <A title=xmwang@sait.samsung.co.kr 
      href="mailto:xmwang@sait.samsung.co.kr">Xiaoming Wang</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>To:</B> <A title=Seamoby@ietf.org 
      href="mailto:Seamoby@ietf.org">Seamoby@ietf.org</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, November 27, 2002 
      8:07 PM</DIV>
      <DIV style="FONT: 10pt arial"><B>Subject:</B> [Seamoby] My opinion about 
      CARD</DIV>
      <DIV><BR></DIV>
      <DIV><FONT face=Arial size=2>Hi all, </FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>I only can see a few situations where CARD 
      can be used. In most cases, handover only involves one CAR. So is CARD 
      enough to be a protocol? IMHO&nbsp;it is better to integrate it in other 
      mobility protocols such as FMIP&nbsp;since it is not common for all cases. 
      </FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>Xiaoming 
      Wang<BR>=========================================================<BR>Network 
      Protocol Technical Group, i-Networking lab<BR>Samsung Advanced Institute 
      of Technology, South Korea</FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>Phone: 
      82-31-280-9615<BR>Fax:&nbsp;&nbsp;&nbsp;&nbsp; 
      82-31-280-9569<BR>EMail:&nbsp;&nbsp; <A 
      href="mailto:stone_wang76@hotmail.com">stone_wang76@hotmail.com</A> 
      (preferred)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      <A 
      href="mailto:xmwang@sait.samsung.co.kr">xmwang@sait.samsung.co.kr</A><BR>=========================================================<BR></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C29A41.4C261BF2--
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby



From seamoby-admin@ietf.org  Wed Dec  4 11:00:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18440
	for <seamoby-archive@lists.ietf.org>; Wed, 4 Dec 2002 11:00:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4Funv27854;
	Wed, 4 Dec 2002 10:56:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4Fs2v27692
	for <seamoby@optimus.ietf.org>; Wed, 4 Dec 2002 10:54:02 -0500
Received: from motgate.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17876
	for <seamoby@ietf.org>; Wed, 4 Dec 2002 10:51:08 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id gB4Frrhh023359
	for <seamoby@ietf.org>; Wed, 4 Dec 2002 08:53:53 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id IAA23991 for <seamoby@ietf.org>; Wed, 4 Dec 2002 08:53:53 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6LTRB3>; Wed, 4 Dec 2002 09:53:03 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B08AD5B5A@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Date: Wed, 4 Dec 2002 09:53:01 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] test: please ignore
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>


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


From mailnull@www1.ietf.org  Wed Dec  4 11:00:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18486
	for <seamoby-archive@odin.ietf.org>; Wed, 4 Dec 2002 11:00:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB4G33Y28235
	for seamoby-archive@odin.ietf.org; Wed, 4 Dec 2002 11:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4G33v28232
	for <seamoby-web-archive@optimus.ietf.org>; Wed, 4 Dec 2002 11:03:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18443
	for <seamoby-web-archive@ietf.org>; Wed, 4 Dec 2002 11:00:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4Funv27854;
	Wed, 4 Dec 2002 10:56:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4Fs2v27692
	for <seamoby@optimus.ietf.org>; Wed, 4 Dec 2002 10:54:02 -0500
Received: from motgate.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17876
	for <seamoby@ietf.org>; Wed, 4 Dec 2002 10:51:08 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id gB4Frrhh023359
	for <seamoby@ietf.org>; Wed, 4 Dec 2002 08:53:53 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id IAA23991 for <seamoby@ietf.org>; Wed, 4 Dec 2002 08:53:53 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6LTRB3>; Wed, 4 Dec 2002 09:53:03 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B08AD5B5A@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'seamoby@ietf.org'" <seamoby@ietf.org>
Date: Wed, 4 Dec 2002 09:53:01 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] test: please ignore
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>


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



From seamoby-admin@ietf.org  Tue Dec 10 09:04:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06510
	for <seamoby-archive@lists.ietf.org>; Tue, 10 Dec 2002 09:04:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAE0qv29926;
	Tue, 10 Dec 2002 09:00:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBADwwv29818
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 08:58:58 -0500
Received: from cnserver-com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06336
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 08:55:59 -0500 (EST)
Message-Id: <200212101355.IAA06336@ietf.org>
From: =?GB2312?B?1/bN+NW+v7S/tA==?= <firlink@chinaren.com>
To: seamoby@ietf.org
Content-Type: text/plain;
	charset="GB2312"
Date: Tue, 10 Dec 2002 21:58:47 +0800
X-Priority: 3
X-Mailer: jpfree Group Mail Express V1.0
Subject: [Seamoby] =?GB2312?B?0/LD+9b3u/rXqNK1zOG5qQ==?=
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

         ¾«Æ··þÎñÆ÷£¬°²È«¿É¿¿£¬±£ÖÊ±£Á¿£¬ÈÃÄúÓÃµÃ·ÅÐÄ£¬ÆóÒµÉÏÍøÀíÏëÑ¡Ôñ    


     ÖÐ¹ú·þÎñÈ«Çò×¨ÒµµÄÓòÃû×¢²áÌá¹©ÉÌ£¬ÏÖÍÆ³öÖ÷»ú¡¢ÓòÃû×¢²áÓÅ»Ý·þÎñ£º

       ¡°ÌØ»Ý1+1ÆóÒµÉÏÍøÌ×²Í¡±ÊÇÖÐ¹ú·þÎñÆ÷ÍøÂçÓÐÏÞ¹«Ë¾ÎªÄúÍÆ³öµÄ³¬Öµ·þÎñ£¬

       ¡°ÏÈ·þÎñ£¬ºóÊÕ·Ñ£¡¡±ÄÚÈÝ°üÀ¨£º

 ¡¡¡¡  100M asp cgi,php +ACCESS Êý¾Ý¿â Ö»Ðè 200Ôª/Äê (ËÍÎå¸öÓÊÏä)

       200M asp cgi,php +ACCESS Êý¾Ý¿â  ËÍ¹ú¼Ê¶¥¼¶ÓòÃûÒ»¸öÖ»Ðè 350Ôª/Äê(ËÍÁù¸öÓÊÏä)

       300N  asp cgi,php +ACCESS Êý¾Ý¿â,ËÍ¹ú¼Ê¶¥¼¶ÓòÃûÒ»¸ö,Ö»Ðè 500Ôª/Äê  

       ÌØ»Ý1+1ÉÏÍøÌ×²ÍÊÇÆóÒµÉÏÍø£¬ÆóÒµÉÌÎñ»¯µÄÀíÏëÑ¡Ôñ£¬ÏÖÕý»ð±¬Ñ¡¹ºÖÐ

       ¿ìËÙ¶ÈÉêÇë(Çëµã»÷£©£º http://www.linemail.net/host/index.asp
    
       =====================================================================
       °Ù¶È¾º¼Û¡¢ÐÂÀËÅÅÃû¡¢ËÑºüÅÅÃû¡¢ÍøÒ×ÅÅÃûµÈ·þÎñ£¬Ê¹ÄúµÄÍøÕ¾ÖªÃû¶È´ó´óÌá

       ¸ß¡£ÏµÁÐ³¬ÖµÔùËÍ·þÎñ£¬²»¿É²»¿´£¡
       
       ÂíÉÏÉêÇë: http://www.linemail.net/special/index.asp

       ====================================================================== 
       »¶Ó­·ÃÎÊÎÒË¾ÍøÕ¾½øÒ»²½ÁË½â£º

       http://www.linemail.net

       ÁªÏµµç»°:0592-2180338  QQ:93767793
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby


From mailnull@www1.ietf.org  Tue Dec 10 09:05:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06535
	for <seamoby-archive@odin.ietf.org>; Tue, 10 Dec 2002 09:05:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAE7iA30748
	for seamoby-archive@odin.ietf.org; Tue, 10 Dec 2002 09:07:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAE7hv30745
	for <seamoby-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 09:07:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06513
	for <seamoby-web-archive@ietf.org>; Tue, 10 Dec 2002 09:04:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAE0qv29926;
	Tue, 10 Dec 2002 09:00:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBADwwv29818
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 08:58:58 -0500
Received: from cnserver-com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06336
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 08:55:59 -0500 (EST)
Message-Id: <200212101355.IAA06336@ietf.org>
From: =?GB2312?B?1/bN+NW+v7S/tA==?= <firlink@chinaren.com>
To: seamoby@ietf.org
Content-Type: text/plain;
	charset="GB2312"
Date: Tue, 10 Dec 2002 21:58:47 +0800
X-Priority: 3
X-Mailer: jpfree Group Mail Express V1.0
Subject: [Seamoby] =?GB2312?B?0/LD+9b3u/rXqNK1zOG5qQ==?=
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

         ¾«Æ··þÎñÆ÷£¬°²È«¿É¿¿£¬±£ÖÊ±£Á¿£¬ÈÃÄúÓÃµÃ·ÅÐÄ£¬ÆóÒµÉÏÍøÀíÏëÑ¡Ôñ    


     ÖÐ¹ú·þÎñÈ«Çò×¨ÒµµÄÓòÃû×¢²áÌá¹©ÉÌ£¬ÏÖÍÆ³öÖ÷»ú¡¢ÓòÃû×¢²áÓÅ»Ý·þÎñ£º

       ¡°ÌØ»Ý1+1ÆóÒµÉÏÍøÌ×²Í¡±ÊÇÖÐ¹ú·þÎñÆ÷ÍøÂçÓÐÏÞ¹«Ë¾ÎªÄúÍÆ³öµÄ³¬Öµ·þÎñ£¬

       ¡°ÏÈ·þÎñ£¬ºóÊÕ·Ñ£¡¡±ÄÚÈÝ°üÀ¨£º

 ¡¡¡¡  100M asp cgi,php +ACCESS Êý¾Ý¿â Ö»Ðè 200Ôª/Äê (ËÍÎå¸öÓÊÏä)

       200M asp cgi,php +ACCESS Êý¾Ý¿â  ËÍ¹ú¼Ê¶¥¼¶ÓòÃûÒ»¸öÖ»Ðè 350Ôª/Äê(ËÍÁù¸öÓÊÏä)

       300N  asp cgi,php +ACCESS Êý¾Ý¿â,ËÍ¹ú¼Ê¶¥¼¶ÓòÃûÒ»¸ö,Ö»Ðè 500Ôª/Äê  

       ÌØ»Ý1+1ÉÏÍøÌ×²ÍÊÇÆóÒµÉÏÍø£¬ÆóÒµÉÌÎñ»¯µÄÀíÏëÑ¡Ôñ£¬ÏÖÕý»ð±¬Ñ¡¹ºÖÐ

       ¿ìËÙ¶ÈÉêÇë(Çëµã»÷£©£º http://www.linemail.net/host/index.asp
    
       =====================================================================
       °Ù¶È¾º¼Û¡¢ÐÂÀËÅÅÃû¡¢ËÑºüÅÅÃû¡¢ÍøÒ×ÅÅÃûµÈ·þÎñ£¬Ê¹ÄúµÄÍøÕ¾ÖªÃû¶È´ó´óÌá

       ¸ß¡£ÏµÁÐ³¬ÖµÔùËÍ·þÎñ£¬²»¿É²»¿´£¡
       
       ÂíÉÏÉêÇë: http://www.linemail.net/special/index.asp

       ====================================================================== 
       »¶Ó­·ÃÎÊÎÒË¾ÍøÕ¾½øÒ»²½ÁË½â£º

       http://www.linemail.net

       ÁªÏµµç»°:0592-2180338  QQ:93767793
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby



From seamoby-admin@ietf.org  Tue Dec 10 10:01:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09198
	for <seamoby-archive@lists.ietf.org>; Tue, 10 Dec 2002 10:01:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF3Iv03539;
	Tue, 10 Dec 2002 10:03:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF2rv03447
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 10:02:53 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09063
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:59:54 -0500 (EST)
Received: from latinmail.com.com (unknown [216.167.63.38])
	by smtp.latinmail.com (Postfix) with SMTP id D127D180B8
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:02:46 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 10:02:49 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210150246.D127D180B8@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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


From seamoby-admin@ietf.org  Tue Dec 10 10:01:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09221
	for <seamoby-archive@lists.ietf.org>; Tue, 10 Dec 2002 10:01:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAEfIv00488;
	Tue, 10 Dec 2002 09:41:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAEdSv32678
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 09:39:28 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07489
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:36:30 -0500 (EST)
Received: from latinmail.com.com (unknown [216.167.63.40])
	by smtp.latinmail.com (Postfix) with SMTP id 88FF518B7F
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:39:22 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 09:39:25 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210143922.88FF518B7F@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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


From mailnull@www1.ietf.org  Tue Dec 10 10:02:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09277
	for <seamoby-archive@odin.ietf.org>; Tue, 10 Dec 2002 10:02:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAF4jQ03660
	for seamoby-archive@odin.ietf.org; Tue, 10 Dec 2002 10:04:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF4jv03657
	for <seamoby-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 10:04:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09201
	for <seamoby-web-archive@ietf.org>; Tue, 10 Dec 2002 10:01:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF3Iv03539;
	Tue, 10 Dec 2002 10:03:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF2rv03447
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 10:02:53 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09063
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:59:54 -0500 (EST)
Received: from latinmail.com.com (unknown [216.167.63.38])
	by smtp.latinmail.com (Postfix) with SMTP id D127D180B8
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:02:46 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 10:02:49 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210150246.D127D180B8@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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



From mailnull@www1.ietf.org  Tue Dec 10 10:02:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09303
	for <seamoby-archive@odin.ietf.org>; Tue, 10 Dec 2002 10:02:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAF4pd03688
	for seamoby-archive@odin.ietf.org; Tue, 10 Dec 2002 10:04:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAF4pv03685
	for <seamoby-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 10:04:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09225
	for <seamoby-web-archive@ietf.org>; Tue, 10 Dec 2002 10:01:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAEfIv00488;
	Tue, 10 Dec 2002 09:41:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAEdSv32678
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 09:39:28 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07489
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:36:30 -0500 (EST)
Received: from latinmail.com.com (unknown [216.167.63.40])
	by smtp.latinmail.com (Postfix) with SMTP id 88FF518B7F
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 09:39:22 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 09:39:25 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210143922.88FF518B7F@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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



From seamoby-admin@ietf.org  Tue Dec 10 10:24:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10358
	for <seamoby-archive@lists.ietf.org>; Tue, 10 Dec 2002 10:24:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAFJ7v05441;
	Tue, 10 Dec 2002 10:19:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAFI2v05360
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 10:18:02 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09955
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:15:03 -0500 (EST)
Received: from latinmail.com.com (unknown [209.207.185.29])
	by smtp.latinmail.com (LatinMail) with SMTP id 720553BF1F
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:17:55 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 10:17:47 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210151755.720553BF1F@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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


From mailnull@www1.ietf.org  Tue Dec 10 10:25:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10382
	for <seamoby-archive@odin.ietf.org>; Tue, 10 Dec 2002 10:25:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAFRbV05979
	for seamoby-archive@odin.ietf.org; Tue, 10 Dec 2002 10:27:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAFRbv05976
	for <seamoby-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 10:27:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10372
	for <seamoby-web-archive@ietf.org>; Tue, 10 Dec 2002 10:24:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAFJ7v05441;
	Tue, 10 Dec 2002 10:19:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAFI2v05360
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 10:18:02 -0500
Received: from smtp.latinmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09955
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:15:03 -0500 (EST)
Received: from latinmail.com.com (unknown [209.207.185.29])
	by smtp.latinmail.com (LatinMail) with SMTP id 720553BF1F
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 10:17:55 -0500 (EST)
To: seamoby@ietf.org
From: Victor Peters <vicpeters@latinmail.com>
Date: Tue, 10 Dec 2002 10:17:47 -0500
X-Mailer: LatinMail v3.0 -- http://www.latinmail.com.com
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
Message-Id: <20021210151755.720553BF1F@smtp.latinmail.com>
Subject: [Seamoby] Hello (From Dr. Victor Peters)
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

From: Dr. Victor Peters 
Chief Financial Director 
Independent National Electoral Commission (INEC) 
Lagos - Nigeria 
Date: 10th December, 2002 

Dear Sir, 

RE: INVESTMENT & CONFIDENTIAL BUSINESS PROPOSAL 

It is my warmest pleasure writing you this confidential business offer irrespective of the fact that we have not met or done anything that will re-impose absolute confidence but nevertheless. I am very determined to communicate you with much conviction that you will give my proposal a consideration. As earlier stated I am Dr. Victor Peters, a Financial Director working with INEC. My Agency is in charge of conducting all elections in my country Nigeria and by the virtue of my unique position in office as the Chief Financial Director. I was elevated by the commission to become the chairman of foreign contract tender board committee whose responsibility is to award and supervise foreign contract to ensure it is executed promptly. 

Consequently, I the chairman of the tender board committee in collaboration with two other top committee members over-invoiced certain contract for the supply of electoral equipments needed for the forth-coming elections in April 2003. The initial cost of the contract was pegged at US$50 million, but after the feasibility study was done, while submitting my report to the office of the presidency for final approval, we deliberately inflated the cost to an excess amount of US$ 30 million making the cost to be US$ 80 million. 

Right now, the gist of contacting you is we are constrained to claim the fund due to certain laws enacted by the government guiding civil service code of conduct Bureau which prohibits top civil servants working under Government establishment from operating offshore or foreign Account and this situation has kept us in a fix to openly come forward to claim the outstanding balance of US$ 30 million, hence after series of private meetings we decided to make contact in order to get a reliable foreign partner whom we will forward his or her credentials to claim the fund based on mutual trust and agreement. 

In a nutshell, we need your assistance and support to claim this fund so that at the later time convenient for us, we will come over to your country after the funds have been transferred, we will meet you and collect our own percentage while you will keep the rest as yours. For your support and total dedication to realize the objectives of this operation, you shall be entitled to 30% of the sum total while 70% of the fund belongs to the three officials involved in the deal. 

Note, you are vividly assured that you will not be subjected to any kind of risk for your support and involvement in this venture hence we have piloted a good strategy to ensure the operations goes smoothly of which we have targeted two weeks duration to accomplished our Aim. 

Kindly treat this matter Absolutely confidential because the officials involved are still in service and some of us intend to resign our appointment immediately after the transaction is finalized. I look forward to hearing positively from you while further details will be given as soon as I get your response. 

Best Regards 

Dr. Victor Peters


_________________________________________________________
http://www.latinmail.com.  Gratuito, latino y en español.

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



From seamoby-admin@ietf.org  Tue Dec 10 12:17:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14275
	for <seamoby-archive@lists.ietf.org>; Tue, 10 Dec 2002 12:17:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAHGPv13265;
	Tue, 10 Dec 2002 12:16:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAHDPv12924
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 12:13:25 -0500
Received: from forthnet.gr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13946
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 12:10:24 -0500 (EST)
From: alice@mail.com
Received: from 193.92.150.24 (ppp2-139.ath.forthnet.gr [213.16.149.139])
	by forthnet.gr (8.12.2/8.12.2) with SMTP id gBAHCmJl007414
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 19:12:49 +0200
Message-Id: <200212101712.gBAHCmJl007414@forthnet.gr>
To: seamoby@ietf.org
Date: 11 Dec 02 07:26:33
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_008E_01C27CE9.A3756840"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Subject: [Seamoby] Blondes Forever!!
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Blondes.exe is of type executable and is removed.

Please contact your network administrator for further information.

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

------=_NextPart_000_008E_01C27CE9.A3756840
Content-Type: text/html; charset="us-ascii"

<HTML><BODY>Hey, whatz up :)) Where are you? Don't you chat any more?<BR>
I haven't seen you so long. Read this :))<BR>
<BR>
 - What do blondes wear behind their ears to attract men? Their ankles!!<BR>
 - Why did god invent the female orgasm? So blondes know when to stop screwing!!<BR>
 - What is a blond with hair black colored? Artificial intelligence!<BR>
<BR>
Blondes forever!! :) Time off, i must go now, but i'll be very<BR>
happy if you write to me soon :) Bye bye :))</BODY></HTML>

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


------------------  Virus Warning Message (on ietf-mx)

Blondes.exe is removed from here because it is of type executable

---------------------------------------------------------
------=_NextPart_000_008E_01C27CE9.A3756840--

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


From mailnull@www1.ietf.org  Tue Dec 10 12:17:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14311
	for <seamoby-archive@odin.ietf.org>; Tue, 10 Dec 2002 12:17:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAHKNj13616
	for seamoby-archive@odin.ietf.org; Tue, 10 Dec 2002 12:20:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAHKNv13613
	for <seamoby-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 12:20:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14278
	for <seamoby-web-archive@ietf.org>; Tue, 10 Dec 2002 12:17:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAHGPv13265;
	Tue, 10 Dec 2002 12:16:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAHDPv12924
	for <seamoby@optimus.ietf.org>; Tue, 10 Dec 2002 12:13:25 -0500
Received: from forthnet.gr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13946
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 12:10:24 -0500 (EST)
From: alice@mail.com
Received: from 193.92.150.24 (ppp2-139.ath.forthnet.gr [213.16.149.139])
	by forthnet.gr (8.12.2/8.12.2) with SMTP id gBAHCmJl007414
	for <seamoby@ietf.org>; Tue, 10 Dec 2002 19:12:49 +0200
Message-Id: <200212101712.gBAHCmJl007414@forthnet.gr>
To: seamoby@ietf.org
Date: 11 Dec 02 07:26:33
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_008E_01C27CE9.A3756840"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Subject: [Seamoby] Blondes Forever!!
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Blondes.exe is of type executable and is removed.

Please contact your network administrator for further information.

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

------=_NextPart_000_008E_01C27CE9.A3756840
Content-Type: text/html; charset="us-ascii"

<HTML><BODY>Hey, whatz up :)) Where are you? Don't you chat any more?<BR>
I haven't seen you so long. Read this :))<BR>
<BR>
 - What do blondes wear behind their ears to attract men? Their ankles!!<BR>
 - Why did god invent the female orgasm? So blondes know when to stop screwing!!<BR>
 - What is a blond with hair black colored? Artificial intelligence!<BR>
<BR>
Blondes forever!! :) Time off, i must go now, but i'll be very<BR>
happy if you write to me soon :) Bye bye :))</BODY></HTML>

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


------------------  Virus Warning Message (on ietf-mx)

Blondes.exe is removed from here because it is of type executable

---------------------------------------------------------
------=_NextPart_000_008E_01C27CE9.A3756840--

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



From seamoby-admin@ietf.org  Wed Dec 11 11:34:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11418
	for <seamoby-archive@lists.ietf.org>; Wed, 11 Dec 2002 11:34:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGUiv05567;
	Wed, 11 Dec 2002 11:30:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGS0v05374
	for <seamoby@optimus.ietf.org>; Wed, 11 Dec 2002 11:28:00 -0500
Received: from 10.30.58.06 ([61.235.68.66])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10975
	for <seamoby@ietf.org>; Wed, 11 Dec 2002 11:24:57 -0500 (EST)
Message-Id: <200212111624.LAA10975@ietf.org>
From: hello <notthisemail@dd.com>
To: seamoby@ietf.org
Reply-To: notthisemail@dd.com
Date: Sat, 06 Nov 1999 00:31:03 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="09adcc2a-93d7-11d3-a98a-5254aba02fb7"
Subject: [Seamoby] =?gb2312?q?30=CD=F2=D3=CA=CF=E4100=D4=AA------300000emailaddress_only_usd$10_----300000?=
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>


This is a multi-part message in MIME format
--09adcc2a-93d7-11d3-a98a-5254aba02fb7
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable

=C4=E3=C8=E7=B9=FB=D0=E8=D2=AA=D7=F6=B9=E3=B8=E6=A3=AC=C7=EB=C4=E3=BD=AB=C4=E3=
=CB=F9=D2=AA=D0=FB=B4=AB=B5=C4=B2=FA=C6=B7=BA=CD=B6=D4=CF=F3=B8=E6=CB=DF=CE=D2=
=A3=AC=CE=D2=BB=E1=CE=AA=C4=E3=B6=A8=D6=C6=C4=E3=CB=F9=D2=AA=B5=C4=D3=CA=D6=B7=
=A3=AC=BC=DB=B8=F1=A3=BA30=CD=F2=D3=CA=D6=B7100=D4=AA=A3=AC=CB=CD=C8=ED=BC=FE=
=D2=BB=CC=D7=A3=AC=D2=BB=C8=D5=C4=DA=BD=BB=BB=F5=A3=AC=CE=D2=B5=C4=D3=CA=CF=E4=
=D3=C3=BB=A7=C3=FB=CA=C7usa123888=BB=F2usa123268=BB=F2usa123368   =D3=CA=CF=E4=
=CA=C7=CA=F4=D3=DAyaoweb.com=B5=C4 
=C7=EB=C1=F4=C4=E3=B5=C4=D3=CA=CF=E4=B5=D8=D6=B7=D2=D4=B1=E3=C1=AA=CF=B5=A3=AC=
=C8=E7=B9=FB=C4=E3=B2=BB=D0=E8=D2=AA=CE=D2=BF=B4=B5=BD=CE=D2=B5=C4=B9=E3=B8=E6=
=A3=AC=C7=EB=B7=A2=D3=CA=BC=FE=B5=BD=D3=C3=BB=A7=C3=FBusa123468 =B5=C4=
yaoweb.com=D6=D0=D2=AA=C7=F3=B3=B7=B3=FD=C4=E3=B5=C4=D3=CA=CF=E4=B5=D8=D6=B7=
=A1=A3 =D4=DA=D6=F7=CC=E2=D6=D0=CC=EE=D0=B4=C4=E3=B5=C4=D3=CA=CF=E4
do you have products to sell in net ,please contact with me .i can find 
300000 emailaddress for you only 10$ ,and i will sent it with a =
emailsendersoft to you,if you need please sent a mail to me ,my email:   =
username=A3=BAusa123888 or username:usa123268 or username:usa123368   they =
are yaoweb.com 
if you want to remove your emailaddress pleses sent email to =
username:usa123468    its  yaoweb.com    and full in your emaiaddress on =
subject.then i will delete it                              
=C4=E3=C8=E7=B9=FB=D0=E8=D2=AA=D7=F6=8FV=B8=E6=A3=AC=D5=88=C4=E3=8C=A2=C4=E3=
=CB=F9=D0=FB=82=F7=B5=C4=AEa=C6=B7=BA=CD =C4=E3 =CB=F9=D2=AA=B5=C4=BF=CD=91=F4=
=B8=E6=D4V=CE=D2=A3=AC=CE=D2=95=FE=B8=F9=93=FE=C4=E3=B5=C4=D0=E8=D2=AA=A3=AC=
=9E=E9=C4=E3=B6=A8=D6=C630=C8f=E0]=BC=FE=B5=D8=D6=B7=A3=AC=83r=B8=F1=A3=BA=C8=
=CB=C3=F1=8E=C5100=D4=AA=BB=F2=C3=C0=BD=F010=D4=AA=A3=AC=81K=CB=CD=C4=E3=D2=BB=
=CC=D7=F3=8C=E0]=BC=FE=B5=C4=DC=9B=BC=FE=A3=AC=CA=D7=8C=92=E1=E1=D2=BB=C8=D5=
=C4=DA=BD=BB=D8=9B=A3=AC=CE=D2=95=FE=8C=A2=E0]=BC=FE=BA=CD=DC=9B=BC=FE=B0l=B5=
=BD=C4=E3=B5=C4=E0]=CF=E4=A3=AC=D4=94=C7=E9=C7=E5=C2=93=82Susa123888      @   =
         yaoweb.com
=BB=F2=D3=C3=91=F4=C3=FB=A3=BAusa123168    usa123268   usa123368    =B5=C4=
yaoweb.com
=C8=E7=B9=FB=C4=E3=B2=BB=D0=E8=D2=AA=DF@=8FV=B8=E6=A3=AC=D5=88=B0l=E0]=BC=FE=
=B5=BD usa123468=B5=C4yaoweb.com=D2=AA=C7=F3=B3=B7=B3=FD=A1=A3=D4=DA=98=CB=EE=
}=D6=D0=8C=91=C9=CF=C4=E3=B5=C4=E0]=CF=E4=B5=D8=D6=B7=A1=A3                   =
                     
--09adcc2a-93d7-11d3-a98a-5254aba02fb7--

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


From mailnull@www1.ietf.org  Wed Dec 11 11:35:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11438
	for <seamoby-archive@odin.ietf.org>; Wed, 11 Dec 2002 11:35:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBBGbiB06622
	for seamoby-archive@odin.ietf.org; Wed, 11 Dec 2002 11:37:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGbiv06619
	for <seamoby-web-archive@optimus.ietf.org>; Wed, 11 Dec 2002 11:37:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11432
	for <seamoby-web-archive@ietf.org>; Wed, 11 Dec 2002 11:34:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGUiv05567;
	Wed, 11 Dec 2002 11:30:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGS0v05374
	for <seamoby@optimus.ietf.org>; Wed, 11 Dec 2002 11:28:00 -0500
Received: from 10.30.58.06 ([61.235.68.66])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10975
	for <seamoby@ietf.org>; Wed, 11 Dec 2002 11:24:57 -0500 (EST)
Message-Id: <200212111624.LAA10975@ietf.org>
From: hello <notthisemail@dd.com>
To: seamoby@ietf.org
Reply-To: notthisemail@dd.com
Date: Sat, 06 Nov 1999 00:31:03 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="09adcc2a-93d7-11d3-a98a-5254aba02fb7"
Subject: [Seamoby] =?gb2312?q?30=CD=F2=D3=CA=CF=E4100=D4=AA------300000emailaddress_only_usd$10_----300000?=
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>


This is a multi-part message in MIME format
--09adcc2a-93d7-11d3-a98a-5254aba02fb7
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable

=C4=E3=C8=E7=B9=FB=D0=E8=D2=AA=D7=F6=B9=E3=B8=E6=A3=AC=C7=EB=C4=E3=BD=AB=C4=E3=
=CB=F9=D2=AA=D0=FB=B4=AB=B5=C4=B2=FA=C6=B7=BA=CD=B6=D4=CF=F3=B8=E6=CB=DF=CE=D2=
=A3=AC=CE=D2=BB=E1=CE=AA=C4=E3=B6=A8=D6=C6=C4=E3=CB=F9=D2=AA=B5=C4=D3=CA=D6=B7=
=A3=AC=BC=DB=B8=F1=A3=BA30=CD=F2=D3=CA=D6=B7100=D4=AA=A3=AC=CB=CD=C8=ED=BC=FE=
=D2=BB=CC=D7=A3=AC=D2=BB=C8=D5=C4=DA=BD=BB=BB=F5=A3=AC=CE=D2=B5=C4=D3=CA=CF=E4=
=D3=C3=BB=A7=C3=FB=CA=C7usa123888=BB=F2usa123268=BB=F2usa123368   =D3=CA=CF=E4=
=CA=C7=CA=F4=D3=DAyaoweb.com=B5=C4 
=C7=EB=C1=F4=C4=E3=B5=C4=D3=CA=CF=E4=B5=D8=D6=B7=D2=D4=B1=E3=C1=AA=CF=B5=A3=AC=
=C8=E7=B9=FB=C4=E3=B2=BB=D0=E8=D2=AA=CE=D2=BF=B4=B5=BD=CE=D2=B5=C4=B9=E3=B8=E6=
=A3=AC=C7=EB=B7=A2=D3=CA=BC=FE=B5=BD=D3=C3=BB=A7=C3=FBusa123468 =B5=C4=
yaoweb.com=D6=D0=D2=AA=C7=F3=B3=B7=B3=FD=C4=E3=B5=C4=D3=CA=CF=E4=B5=D8=D6=B7=
=A1=A3 =D4=DA=D6=F7=CC=E2=D6=D0=CC=EE=D0=B4=C4=E3=B5=C4=D3=CA=CF=E4
do you have products to sell in net ,please contact with me .i can find 
300000 emailaddress for you only 10$ ,and i will sent it with a =
emailsendersoft to you,if you need please sent a mail to me ,my email:   =
username=A3=BAusa123888 or username:usa123268 or username:usa123368   they =
are yaoweb.com 
if you want to remove your emailaddress pleses sent email to =
username:usa123468    its  yaoweb.com    and full in your emaiaddress on =
subject.then i will delete it                              
=C4=E3=C8=E7=B9=FB=D0=E8=D2=AA=D7=F6=8FV=B8=E6=A3=AC=D5=88=C4=E3=8C=A2=C4=E3=
=CB=F9=D0=FB=82=F7=B5=C4=AEa=C6=B7=BA=CD =C4=E3 =CB=F9=D2=AA=B5=C4=BF=CD=91=F4=
=B8=E6=D4V=CE=D2=A3=AC=CE=D2=95=FE=B8=F9=93=FE=C4=E3=B5=C4=D0=E8=D2=AA=A3=AC=
=9E=E9=C4=E3=B6=A8=D6=C630=C8f=E0]=BC=FE=B5=D8=D6=B7=A3=AC=83r=B8=F1=A3=BA=C8=
=CB=C3=F1=8E=C5100=D4=AA=BB=F2=C3=C0=BD=F010=D4=AA=A3=AC=81K=CB=CD=C4=E3=D2=BB=
=CC=D7=F3=8C=E0]=BC=FE=B5=C4=DC=9B=BC=FE=A3=AC=CA=D7=8C=92=E1=E1=D2=BB=C8=D5=
=C4=DA=BD=BB=D8=9B=A3=AC=CE=D2=95=FE=8C=A2=E0]=BC=FE=BA=CD=DC=9B=BC=FE=B0l=B5=
=BD=C4=E3=B5=C4=E0]=CF=E4=A3=AC=D4=94=C7=E9=C7=E5=C2=93=82Susa123888      @   =
         yaoweb.com
=BB=F2=D3=C3=91=F4=C3=FB=A3=BAusa123168    usa123268   usa123368    =B5=C4=
yaoweb.com
=C8=E7=B9=FB=C4=E3=B2=BB=D0=E8=D2=AA=DF@=8FV=B8=E6=A3=AC=D5=88=B0l=E0]=BC=FE=
=B5=BD usa123468=B5=C4yaoweb.com=D2=AA=C7=F3=B3=B7=B3=FD=A1=A3=D4=DA=98=CB=EE=
}=D6=D0=8C=91=C9=CF=C4=E3=B5=C4=E0]=CF=E4=B5=D8=D6=B7=A1=A3                   =
                     
--09adcc2a-93d7-11d3-a98a-5254aba02fb7--

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



From seamoby-admin@ietf.org  Thu Dec 12 05:18:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18691
	for <seamoby-archive@lists.ietf.org>; Thu, 12 Dec 2002 05:18:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBC9mOv06950;
	Thu, 12 Dec 2002 04:48:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBC9lMv06931
	for <seamoby@optimus.ietf.org>; Thu, 12 Dec 2002 04:47:22 -0500
Received: from directvinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18101
	for <seamoby@ietf.org>; Thu, 12 Dec 2002 04:44:12 -0500 (EST)
Message-ID: <41125-220021241294658223@directvinternet.com>
From: "Charly Calder Faux Furs" <ccalder@directvinternet.com>
To: seamoby@ietf.org
Date: Thu, 12 Dec 2002 01:46:58 -0800
MIME-Version: 1.0
Content-Type: multipart/related; 
	boundary="----=_NextPart_94915C5ABAF209EF376268C8"
Subject: [Seamoby] Christmas Greetings!
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: multipart/alternative; 
	boundary="----=_NextPart_84815C5ABAF209EF376268C8"

------=_NextPart_84815C5ABAF209EF376268C8
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

=09 =09=09 =09=20

=20



Faux Chinchilla

Faux Fox=20

Manhattan Mink=09=09=09=09=09 =09=09=09=09 =09=09=09=09 =20
=09=09=09=09 =20

Midnight Mink Faux Fur Throw:=20

Faux Fur Throws are ideal choice to make your living space more cozy, eleg=
ant or plain cool=2E Charly Calder throws come in a variety of best qualit=
y TISSAVEL Faux Furs (Black & Brown Mink, Sable, Red & Purple Fox, Wolf an=
d more)=20
Our exclusive offer only available at: www=2Echarlycalder=2Ecom=20


Forward this e-mail to a friend, and  automatically  enter to WIN!=20

Happy Holidays!=20

=20




If you wish no longer to receive e-mail offers from us, send e-mail to cca=
lder@directvinternet=2Ecom, with subject line Remove=2E We apologize for t=
he inconvenience=2E=20
------=_NextPart_84815C5ABAF209EF376268C8
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html>



=09<head>

=09=09<title>Charly Calder Holiday Gift Ideas </title>

=09</head>



<BODY BGCOLOR=3D"GHOSTWHITE" text=3D"9999CC" link=3D"white" vlink=3D"white=
" alink=3D"white">
<center>
<table width=3D"560" bgcolor=3D"333333" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"0" align=3D"center">

<tr>
</a></td>
</tr>
<tr valign=3D"top">
<td width=3D"159">
<table width=3D"25" bgcolor=3D"330000" border=3D"0" cellspacing=3D"0" cell=
padding=3D"4">
<tr>
</tr>


</tr><p align=3D"CENTER">

<br>
<center>
<a href=3D"http://www=2Echarlycalder=2Ecom/cavalli2=2Ehtm"><IMG SRC=3D"htt=
p://www=2Echarlycalder=2Ecom/cavallimini=2Ejpg" WIDTH=3D"120" HEIGHT=3D"16=
0" alt=3D"Click for more Information!"><br>
Faux Chinchilla<br>
<a href=3D"http://www=2Echarlycalder=2Ecom/lotus22=2Ehtm"><img src=3D"http=
://www=2Echarlycalder=2Ecom/reklotus=2Ejpg" width=3D"120" height=3D"163" a=
lt=3D"Click for more Information!"><br>
Faux Fox <br>
<a href=3D"http://www=2Echarlycalder=2Ecom/manhattanii=2Ehtm"><img src=3D"=
http://www=2Echarlycalder=2Ecom/manhattanrek=2Ejpg" width=3D"120" height=3D=
"167" alt=3D"Click for more Information!"><br>
Manhattan Mink=09=09=09=09=09



</tr>

</table>

</td>

=09=09=09=09
=09=09=09=09
<td width=3D"600" bgcolor=3D"333333"><BR>
<center>=09=09=09=09
<td width=3D"420" bgcolor=3D"333333"><BR>
<center>
<img src=3D"cid:1856115-2200212412934188611163@directvinternet=2Ecom" widt=
h=3D"421" height=3D"72" usemap=3D"#title1" border=3D"0">
<img src=3D"cid:2064716-2200212412934188611164@directvinternet=2Ecom" widt=
h=3D"354" height=3D"128" usemap=3D"#title1" border=3D"0">


 =20
<br><img src=3D"http://www=2Echarlycalder=2Ecom/199=2Egif" height=3D"41 wi=
dth=3D"368">
<a href=3D"http://www=2Echarlycalder=2Ecom/midnightthrow=2Ehtm"><font colo=
r=3D"9999CC"><FONT SIZE=3D"4">Midnight Mink Faux Fur Throw:</a></FONT>
<br>
<font size=3D4">

<a href=3D"http://www=2Echarlycalder=2Ecom/throws=2Ehtm">
<img src=3D"HTTP://WWW=2ECHARLY=2ECC/midnightreklama=2Ejpg" height=3D"300"=
 width=3D"400"></a><br>

Faux Fur Throws are ideal choice to make your living space more cozy, eleg=
ant or plain cool=2E Charly Calder throws come in a variety of best qualit=
y TISSAVEL Faux Furs <font color=3D"white">(Black & Brown Mink, Sable, Red=
 & Purple Fox, Wolf and more)



<img src=3D"http://www=2Echarlycalder=2Ecom/moreinfo=2Egif" height=3D"41" =
width=3D"368">

<br>
Our exclusive offer only available at: <A HREF=3D"HTTP://WWW=2ECHARLYCALDE=
R=2ECOM">www=2Echarlycalder=2Ecom
<BR><BR><img src=3D"http://www=2Echarlycalder=2Ecom/rfox=2Egif"></a><br>
Forward this e-mail to a friend, and  automatically  enter to WIN!
<BR><BR>
Happy Holidays!
<table width=3D"150" border=3D"0" cellspacing=3D"0" cellpadding=3D"5" alig=
n=3D"right"><br>

<tr>

<td>
<center>



</td>
</tr>
</table><BR><bR><p ALIGN=3D"JUSTIFY"><font face=3D"Verdana,Arial,Helvetica=
,sans-serif" size=3D"2">







<br></a><br>
If you wish no longer to receive e-mail offers from us, send e-mail to cca=
lder@directvinternet=2Ecom, with subject line Remove=2E
We apologize for the inconvenience=2E=20















<map name=3D"title1">
<area shape=3D"rect" coords=3D"2,1,424,42" href=3D"http://www=2Echarlycald=
er=2Ecom" title=3D"">
<area shape=3D"rect" coords=3D"158,47,223,67" href=3D"http://www=2Echarlyc=
alder=2Ecom" title=3D"">
<area shape=3D"rect" coords=3D"225,48,422,67" href=3D"http://www=2Echarlyc=
alder=2Ecom" title=3D"">
<area shape=3D"default" nohref>
</map>

------=_NextPart_84815C5ABAF209EF376268C8--

------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: image/gif; name="rektop.gif"
Content-Transfer-Encoding: base64
Content-Description: rektop.gif
Content-Id: <1856115-2200212412934188611163@directvinternet.com>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhpQFHANUAAHR1cF1niB0dHWp3oVRde2l2niwsLCkpKXB+qzc4OigoKIKTykpSaXyMvzxB
UiQkJCIiIiYmJkdMW2Nuk3aFtCAgIEVMYxkZGSotNRUVFTk+TH+QxIaY0VdgfTI1QXF/rTU6SU5W
cCQlKjM4RVFac0BGWjs9RS4xOyEiJhscIB4gIygpL42h4PLz58LDumBgXYea1pGRi+fn3EFEUHiH
uJ2el0dIRoWFgFRUUqmqotrb0c7Pxba2ri4uLo2g3C8vLyH5BAAAAAAALAAAAAClAUcAAAb/wJ9w
+Ov1DEjD4aBQRB7Q6ANCpUqjkeYyaTQSv+CweEwuf41JJbP5vE6r7kdWsUV6zfgufg9GJ5drTnFQ
VVZuc3QHaXd8jXxdaUtNgoNvhodailyMjp2eZn5qbFFUFaanqKmXmYt6n2NdsZyOoUqjhBCpuqir
dJthsrF9wbOvQrWSClKFu80VcFBzmgauxq+hyW24uc67l9LTxdbje9hNuKYCAiIaJQTv8PEaHuqm
EFCsrT3kRbW/neaUvUmnToOGeAgJzKv3DF+4YUfSULsDSeJEfgFJcaugToDBEAnjhVjI0JCWf/we
RZTUphRBAR7ahZSnQUTJe3J82dmXsies/5VMCKU7+IGDj6NIkyr1QSNACRENH2SaRg1jRIsXG/mR
JJQj0Q1LwyKlMcGCgoY6eQ7xJzEWVpTGtgrkVjBEgKJi8/rYMCAEPXsOufjMs1IQXQEY3H0Aqzcs
hw8ESggALLWOuMFWkTB5kktAiQGNQx+dgCEquJ3jtkoChLpcYc6mSkwwKlrvgBH3fHG6mqzOxD+r
H6bWrKyzBwIfatfeMMED4LRqMQMjzhmxhQK0lTceYAHqvQiWpQ+WK7QD47w0PqhXjyB72BLPcEpN
O9yWIGl2XFOfUoHBebHprfdBe3oxAAF9axHnRARZUKUggydldc0RQR1onl4IrBfPXerR0P/YBhag
pUl04hFR2BQMIKDXBusFEM8A6zXGQQAYfDdiiT2dOIUG/x3Fl0L0dCTABUNeYOQFKowwAgMEqOjD
B5NV4MAEJ+R0Y1zEPRCABNHoRqIYrz1QwQgeKvUjSUIWeWQGSjLp5AYQgJffMdT1MAEIgf0hiAQT
MNDgnNdkOYJ7PlAwAQEjnHAkkWk26pE7BfToAwcGVlYVjmcgocwKySW1AQIkWACCCkc62mhMBEzQ
qVIB5HYlpnGtxFkHSXFQFgYdNdPRohn0msEFKzzWEa0+4IngJydCcBQNrgL6k2acMVArd7gypMuu
a/qK5AbMynlpEdA+4MBRrVoqirhHdSD/x6vIZskYAoj6+mup1uqaJgoOEFDmpBWY+6V4aARFbFMO
iCAvvVE60+gFGjAwQHYGevsvrFplCUEASE0gWcKXLPPSmkaC4OHGAhBw1ADNTtwPMbLYsiNS5XpZ
RrLSjrbxKR1rxJE6vF4gsg/qSlxRhcT6UIKVXF2cbsosNy0MuC4nF4ADKhxsZK7xFcLMKR2lcKQK
FhylQW47OQ2M09WYSKEyJDBlwQpWXx2l1lqjIuSiICTXAdNnoO23yu1WWMKkHdhkj3yITNLSzjyD
EIKHHIQgpMlP9iux2my9pcQTFWiA1AeWj9h0P7Y8MS7QuB6OxSSKC3W342Xuba5EFVZQ/7TsrPPX
Ke4Oav6WWy6v0MG+CCDg4jsdaODACvJptDXji6pwlAXN+l52y9ZP5MpWTzg8FgKHIl+CA7jFUTfX
PBuZgYqgr3t9Rdn7nrYxFnNbrWmTAKL/OSBI0IGq5/lACGwyuaNAqXrYAw5raGcYj3xOANXDCvAq
9AEaBAl/U9mfMk7gPwB+LgSlcRVVWCKmkiGFAA3JAhQ4MoGjhMByOgEOVvTXFt4UhyMxkQkBGKA8
B1SCbnZTUwZO90KkqYGG8Uui9shTQgwYRAMh6MBIHLC8QQARfUXqlVEOOLsk6u+LvZMQ/Tb3gBJs
gIBRmcoMFaCBGVDRAU8kYJQK6AMCTP/GSm9JBuv2OAoIqOMED4RgZcJokQM8YVBoxEmDfBMJBXjA
jVSMY65wksE1rFAdYTuKHftFCnVQTgNoSUQg+EhK36hmLhuJDxYYpI0q2CuLGSiTBgSZuFIuUDNf
tKUpJ4hKXkCDlctIZRCFSLkA3HGQkQDjKEnJultephGamkIHOjBJfCQij5tBh70uQDk73vFPjaRE
JVw3pAzAjEihFOUt//CEDhizHpS85gyzORBVKJJ1rdyZz5DigMm4kmefPCYwx3mFRZYNl7co6B5b
chhTqS8DGDsKCgRJ0C5lAp/aKOhplqgncUqhlgLhz0sWpj5AalId8UwERjNa0S4JZ4z/xfnABKo5
n3UilBKu3AVAp8coTqrzHPX0ZU551qsTXi0qcoBQhKgDgQ5ACZ7WtKkocOoSnDVPZ/q8AJuQAgJG
3e0CbSuWP3FS1axtzSThwIYem7m/H0yAAgKKa1wJNb2xllWoP6RbIaIQIeDddI+5VEAH4CrXwu4r
KQWA51WDeUVnoLU1r4gmBJJjAZomToPizKlOh0S5EVzNOd+5RWegCA+SIYZnGojUBganyV85EbRw
gIAHehDDJbTTB+/0J1/zB4jWbUMX0BgIYtzxju5s9ShdJdIFMJAvAjjASSCoV0EI0IHudEQEBBTB
BDw0AH/5FZdIPKIT/KOdpCDAqx05/wg8oquOEjDgLMxYQRSDxI4QgDBXIAABeG4EPwUykiUzWFV5
fbCCeljAQHUTXgeqddr2FmW1HcEASEJQvmN9Ilw1G8D9VFlQN5RVSKcQQWW5eZQRZEAFBfDBBDjM
HxEQgK4IWAEIjsIBC2TyKKz1AQNOnDGsYcwB4HRZzT4wy7ktlqVBZRzHSrCCoQiYxgzwAFJOMK+I
LqWrQgIBaDyFAhSUqQAY2NcHwKmW72oumxBggIAf8wEXhSC/KhBBUrCsDhEEAMZgo3GQOtLCOl7A
y0kJwAVCsIENjMBfa+nvmYMirtkkJT0DeIcDQEDlfRGAURGlgRzVUaZLh8BH7pizz/+chBQ4ScVZ
nrDYqj5g3YSZ9XlKFpIHQgCaEVOuV5Z29ToOyxzs1HEFNZsUUjhgzhL3ysoWuFomfVjb4vSZKfd1
tV5TaapZg2bFnqwV+MDCASkfxVc3XgoJjoSCTtGABCNIcbFU8DNhI4UBiO6b0/QEmxPUxFHqe/Z5
eYaB/xjKSQyYMY1RoNwVGDVfzy115L7JrkQ3raNCQVPX1DeCYaugI59e1pCGlONLnyDj7qFBBiww
IxMPMQDUsxTg8qCpJ6zg2ctC+Z5NlaYVQPEuSWHATn2QAZj7YOYCULcPCoCCXmHAKCZ/tgVG4Nxi
+8DkKmDMBrR6AdpowH3snIKVY27/AaDTXB0o0IAFkJOdDgxl2CXwVYoR4G2e94oCNvNAsAPwq54f
pQApKIGTEFB3g98diriDrH72s42hGsnvyGXUBVY1gaJnAAPGtvJ5jWTlCcgrlvwkkgdW8ICGE0ZB
zhtqkUg9AfSuStBGEjoB6v4mKhKgqwgoAAkKAHe39Us31tBR5yTlI/UcDx4CoqsBR8A4ykmLApTb
y0SVS+O0P97RPrBAr07nA6oX1di9uvGOqT+2zjeSMxp4cql9j5Dgi2UDoEwH5RCQggzkvQFHoUDb
fXUUEvTKA7Xfi6/6TBsOFED683IBjMFeCOQJapVQHjMkpLZvHUFjDmB0VmZiKmBp/79yHnznKxOI
FAXAMKamAKj2eTeFZPwxJBl3FKlzCkeHFMkmPTDTKxdQM5N3JCJGAgRAAhOAABvAAbenCCsHCjqS
CyUgfgNmQKDkEia0LKTybDSwAoPmdxxQPISyehdgUjSwKBcwZYviJJSSHYLkIGjWOVs2hErxAQyQ
NRxBOTSAAPmHFBU3Ke3ndGJRACBgAWHFAR1wAimwJBOAeosnNt/kgR84eOC1TLBRgtFXD+rgI8Wz
FFJoUsjFADSQSRxAKhlwAjkodEaxN5cDEGq1VoZRASk4GrpVCjnGAScQAH3iI6SyT0+iXNnSKyIQ
AjiYMqkRJtwgYYelHBzQFyEkH/9AqGdHkosbsAKSsgE1c2lGYkBp0imPoShTmBR9RgMQJDT7cYuP
I4YC1IukUAGGCDNOogK08SkXIHRHgQCnCI2ItxSCNiQR5Rx58kwgOE/nAAHnIY32YAp0ZYwudCQ3
xgE0QCq0sYEg4I9MqIScZ2G0kDkIpXVJURpXkAvP5o8ogHjI6HcDkCaSwgElECeeZ4CFMRfpIALu
ACPn9wGR1nVWFQ0MQggkAGFCEoRPMkAwUSYb8H9GwgEbwGCgYXaooAB9NgE2YSQOkInFFgDP4CWn
hA7rcBAwInwscpLOoTpJFQUVYGVtxoQmc2krADmXxiNMMTVGggJbNGJmNC1FZgr/nsMBlCQ65GBm
uHRInYIbvuiVe2GTV5iTQpJJjcdxRiE5AwCU6UUDIRBagueRCsloESU78/GJGMMBdkQkYcMBRSYA
yUEC8WEKDJAdbYYB75gZoNcVsWYqKZkTKpVZjYVFaSJUOfMGuIE+WkVlxeaOuEc6D6JNX4c1HIYI
liRSt8lgNJcKosliq8OWPhEMb4kLq6SUIHY4sNYNWuNSgRgrvIQJ+6NNwLVXHkYQz0GcbXkVU8VY
VUU3qyNPfzVQefWchwBSLNUZKAAC9HdAm7gywAFUhbcR4mlRC5QMoTdt/HmewZVUrJQP8JgSQLEg
SpUN9dlSCmpEYjQeH3mgI0Sf/wSlVLlDCtAZnbGSTIEggh+lm4ykoYG1UKw0oiClTiEKkiZjKy0E
SipHIsigRxy6SrxFSBtKojZ6oyXKBiupkjMaXgNKoEDBBEjUWwZKoaLETEg6o3CBGZ0oVeKVpJVE
pAuSDw0KpN55RJ4YpTWkaPOkTF5KSLRDQhBgiEaJdROjaCfaox+aQFj6pW76psokPz2YI1e6aF5a
SHAKpj/anXL6ol9qPWDUCjjilkqkPZhTp4WaqOH0AC9HOD7Fg4BDqEr0NPKpqJYaP/MDK5kjqZfa
p3NqFXWqB5zaqYWJKWwqQbJABn+zqqw6n8iJR9/ig1y6pZnqcKx6q/3lNxRzNv+42quruqvylqrB
6qtmA6xgwjLGyon09gQGVaUqQQzJGq3SOq3UWq3Weq2qyhtrsEvY2q3e+q3gGq7iOqiIuqTjeq7o
mq7quq7UyqW1KgQJIAEmAAYmIAH2Ggb2Kq/0KgEJMATxyq9DIAEzMAQzMLD/CrBCUK/2Oq8Ji7A/
cK9CMAMIq7D+mq/9GrESAAb56rA/ILEbO68bOwb/erEEa68ky7BEgLLsurIsa63ISgYmwAIIIAT6
+gPwhwAskLE/0AE0ywIDwAIN0LBCgLMDu7MwwAJIiwD9ygIUMAQU0LQSgLQsEABDEABSC7QM8ANW
q7M2m7M/kAAwAAMmkAA4K7X/PBu1SEu1QkABLAAGV8u0Rcu2V0u1VwsDBUCyQtABR5u0/ToDDSC1
MEACa8u1P1AAatuyiJu46fq38xp7HSuzM8ACBfADMTuvBZCzlzuwb/W1QJu3STsBRzu5TOu0TWsC
AbAALLAAVSu5AVAAYau1XhuxqVu4LMCzOGu3ZcsApou6MOC0bfsFqYuKRyu2P8C2AXC8W/IDwRsA
fyu4Q9ABnxu6YJu6b4W0WUsBMFC0EzC1itu93vutJFC7MQsDCbC9Gfu35Su5YKu6UXu3R2sC0Ou8
R5u1lMuzytu0a4u/48sC9Lu1QrC9DOC/Q7C9OBu0kUu+NEu/CcACR+u8bOu2//jrVpJbvL9LBKPL
uRH8A/ObsDwLvREcvqrLttkbvtz7vSZ8wtG6vlZbuwuguj8QvnrLwNBrvwsQuEg7AQ2AwJHrwhb8
thdsteGLv/7rtyxgurELr6jLAgNrtZMLBlbrwWtbwUNwwZTLtHIrtTo7ugkAvU38uDzsu84rBEdL
wWGbuiWMwmicxiVyuTBAAUlsvwt8wwyMwDuLtAuAAKGbsLP7BSL8tNiLvzCgujhrxG87AbCrsyRA
tQwwwXXcxUTQwrQ7sA8sBAEguFQcs4ZytH48sD68AEVbxV8cxWGswW3LtjMAAw2wyIerxqzcyuMQ
ufwLvSxAsperuqjbxXHcAf+LXMRD0MBD4LxU/LQv/LYFIAFsWwDb68IC/MBRq7awfLEmkLUkLLWT
O8n3e81CcLnVLMWwuwDMywKjTMphLLjQG7SeG8JtO7bN7Mrs3M6e0ACqu8COHLU8a7Wf/AN43K8L
0LQdMLAkTAHfLLoRLMyoi7w1nAD+i7OGzMTHi7oPe8Zla7gN/LcGTb7Ge7yjG7yuy8DzetHHm7Gj
e8D92s/DzLQBnQC8W738S8EBe8bu/NIwHQaJnM2E+wML0K8mYM5DwABNPAGWPLMvvLfqi83FSwHt
u7qJ7LXTKwErfLUPfbjpK7UkELVADbuD9bZNi9Vx+7Z0i78ErLxATQJCfbf/lHvFgRvFLb3KMb3W
MJ0A0AwGJIu38DrXHYu3EJus9XrPwDoDdl3THXvXbB3Ygj3YhF3Yhn3YiJ3Yir3YjN3Yjv3YkB3Z
kj3ZlF3Zln3ZmJ3Zmr3ZnN3Znv3ZoB3aoj3apF3apn3aqJ3aqr3arI3GCXADLvAC7GoDMeACONDa
uN3KCdACvC3b6ooDvN0Ccp3bxO29ANACNWADQvACMRADN3CxNvACNnADt00Er30DNmACAPDcRIAD
za3cQhDdNrDd4O0INdACAHCxANDcADAEOPACCRAD5f0Cvu3e8P0D0/3dREDb6Y0DN9DeRLDe6W3f
0w3gxX3gZBADLeDbORDc/y0gA7et4DKA3t094S2gAzsQ3L593sHtAv0q4cF9A53gAi0AryQe3Dug
3CQ+4eXNAxReA/064QkAABbO2yL+AzcQ3Dxg4TIArxnO2zJQA0Kw4kBe3Qh+5EMAADrQAjtQA8cd
5ABA4jrwAwruAgYuBOddAwreAjmg4DnwA08OAC9A4i5A5Q9+A+c95Y1QAxPuAlp+4TEAABle5iTO
A1d+3Dmw2wCA5yYw4XaeAxMu20sO2zZO4u3d4LFN4xRO4jtwAy4u5Ege6UrO5DVA4jf+A4Gu4Fc+
5CWO6cL9AzrQ4y7uAs3d4MKt4Dfu4kaOB2zeAm6+5ABuA7xtAyRe30MgA/8yoOA60OB7zuRD0OA5
ANxl/gKu/gPEzgM/wNtdXtvFTuLKvds9HumRruCyTeJG7uLMveBgQOKc3u0n7uALTu1CIO6NwO3J
/ulCkOFjru1fwOETLgNTruCQDuauTuzDXuz2fu7gTued/gPmLu1HLu6PDq+87d3sTgTmnvAlDuzw
CuDkTu58YO4ZDuDALdy1DgYVfwMTLuTHreY/8Oj5HvLFHuhC8N7dfvIAj+DiTuyu3uplDvFDoPDd
zvI50Opf/vAHvwfmnuMtwAOAjtz+nvNDsAPx3gK3bQJLrgM1kOEyEN34/vQvf+E1YOrt/e//nvLF
Te6Kztsebua2fvIyD+Z4Nf7lXj/uQm8G/77lvM0D/XrxYHADMYDfO+DeP/7g7S3y917mP8Dhdo/y
V4/1uQ3xCUDfq/4Kg3/fKXH1h1/eZODWdG3fX28G0R35gC/tMJ+uf1/5mm+tzM346bremx/6oj/6
pF/6pn/6qJ/6qr/6rN/6rv/66xoEADs=
------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: image/gif; name="holidaygift.gif"
Content-Transfer-Encoding: base64
Content-Description: holidaygift.gif
Content-Id: <2064716-2200212412934188611164@directvinternet.com>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhYgGAANUAADExMS4QEC0tLSUlJTEaGrNKaSkpKSEgIDIrKxoZGSskJDAVFSoODmkzQh0d
HY+DsyMbGxoWFjEiIisbG1UnMiUQEM4zVo1slB0WFo59q42f3SISEno6TY2d2h0ZGY5xm42g35CR
xo+JuyAUFDAoKI2Z1Y52oY56po1liicgIBgXFyYWFh4TE4+Gt5lGYJCOw4yX0tUtUcE/YEAcIY+M
v+IhSNsnTJCXz4xfgY+UzBsUFOgcQ42h4I2b2I+Ar4pAVyH5BAAAAAAALAAAAABiAYAAAAb/QAAA
MUQYjyQEabmUkCTQqJQgoRKu2Kx2y+16v+CwmFutjs/otHrN9patbbK1LK07nUzlcT/sC/+AgYJE
e3tMTU92UHNYb3GPkG6Mb5RZlZdwkZqba5iYlpOhnqFXdFSKUE+HeoWEQkSCsYGErUmHd6iLjpy8
vWBmvsHCwru8wJSoqqutfbCyz7SFtky4doxxC1fZBNvd2t/c4N7h5NvD51vj6uLs5e3r7uTo842l
p8l4S6yFfs7Ps0UMKaGWSFGmg1zgKXzHMN5Ch/TOPFSXbUHFi9wwWswIsePEdhEhXVKkLA8zV/9i
RUMysAkqUl68aZzJcaNNmjdr4tToEZyw/4k7dQrNSTRo0aE8P8o7Zw4NHZL59vHxl3KWtJaqciHU
IjOjxa9gw4odS7as2bBIhfZc283o2bdw48o1m5ZoQ6V4f02yU1LfST9V/7TSc8tgMa7h5ipezFhs
XbePvTaeTLny2MhHM0Me9+Up36hJ+KEM/OrqrYJ1wty0zLp1WcwzXcuePRu2TrlqJXlOlc/vX9Kl
pVEzvPXbRdrIkytfzrw57cRbzOyOUlKqEcDAhRMknjCx8+/gWQewOH5B+fPk05tXj369+/blw4df
Gv0eddB/qabUjsjaYeNwwcfegO8RKGCBCLYn31wHNmjggwlC6CCCC1IGXRf45BHaEc0AF/+QEadx
191bE5Yo4YkRphifcyYWGMB4L5oH44wy1hjjjTTiaGOOKE5Y4Vv0iVLHIRuK5qEhIab2n3dknZfj
kztGqeOUUFIpZYtY9shelVxe6aWVYHYZ5npZqqglhWcF2QhU+hR5nX77IbGdf10cFxZ6VL6o5558
9unnn4Dy+SWUZhYq4Jg4Bqrooow2quegURp6ZouvNWXPdMpY9+aRcg6n5FZmOSmjo6SWaiqkiIrJ
pamstuqqn6iqGquU7pGl5hyfmTTVK6Qh2Z8iEyQ0lqivFmssoLOmOuqxzDZbbLKyCqpjrWhZWg9J
y3A4WlWd/hpFcZLdSaaz5JZr7rnopqv/7qMwVqrFdLxlqy2nWGU1hQTBptPkAg1w4O8Mf/rrb7EC
N7DnDC4UQIGjMwi88LqmzvBDARRTbDCgFBTgwp8ZV/zDixS4wEGjAo/saL8cXAwxqQs07LBjcgzZ
m5vbxllvNUuG+1W7Fuzgs8l9+uxzsUJbsGcBPhtNstAFrOwoBTIILfUONmzspw0+F8AAn1FLbXQM
WTcqNak976C0045yIHUBK6D1rn33EflbYN2i9i2++ooLY9k7AM3n2K8WvSffaTONtqIMID314hYA
vGcDPtdw9ouKSz2y4YwC3mjZkx+uqNpCc1BtzFL0RTN2Nid5txYT2LkzmXz7vafmrQqu/6cLSRce
tud/dr344jE4rmfZH+tJgdQ1xBDDi5gvSvuinPPOKOShO2ZthrrykV29dkcRbL6t69zui7H/+byp
thuvMqOg79C09HsmPrUFIvsrQw1e98nBwy/Kn7TwAWieos4XqOjBb4DVgxkZ+CKvedGNSPbyXha+
57r0DC905hOan6AGNp/ZQAayY17ublcxP/3AAvjbQQ1kQIH2vW9PHCzaxxKmMeNVjH964kAJFXW8
tW3tYB2MwcK2trWKcYCIAajcEAOQsKJRbIlIRCIBoYa1pH3MgHzigAyqaDar/WkGBejgDmLQNB1S
jE8z2KLQyIjDACbQbViYALz6MhjUQf8Dgt2T4/ey0Da9XfBnGRxaFCvHuBlEUXBEJBwSZ8A35FXu
hQHw3+JkgMX2hbByi/Jd3yLJSSLOIAYyiGIkDUdETCbyd0fspCoZILUoSnJqBcDiixj5O6qtL4cp
nJoMfPe4XOpSeFKbgfVIV7oGOnA/EMSZHCdIgPDpbVTl81MrGUBNBmjydzYwZDWLVk0G8K2bn6wl
LLt5zVpaoJqW7CY1K6fOds7Ah+3sZiTbyTQkspOTjQydKA8pNHWW83fnrGY4xVmDBqgTd+LUHAV8
uTitidBn1LJI+OKIqd7UEU4qSaYEFOC9Kuyxda1r2wrG07YcckCMBShZyaa5TqnZoGL/jYxBN7lZ
zW/W1GsUu984qfkDl8qAYmJMGjr1qU52xrOaPRWaNtGpUpVuM2vUTBjfbkhJodnAAhYw6FGpyVIG
JNWDPw3j/LrJtxqkVIe5rMFSFyq0FeZ0cUT0nQVGpkOfhVJPYlzRV7iRr2vFzZib4haRNloHPXq0
mQtoHVhGSqaEirOaPbSrOn+QSxc81Wxk7WdUpWZZagZgoFBlwAxyKYOlvjKgDEhnUTW71cqh9rK1
vKzWvFnLI7IytFuFrUBJa1pCohahYzQtaENJTb4JsZsc8OVNVWhI45V2cEKLaNuaeYV8sSl7x0Qm
ExRAAo5yFArL/GhiFyBS8oz0oY6d/1o1K0fcya7xsq+1KQNQ6k4uzha4Mm2na4f6M/2y9qiPpGdC
ZVvc2nIVt7m9rc+qCdzXrpem8yVqNyO7A0NGVq3tbN8OllvQVfKpbDXQa0XiWN3d0PGiD1QdePEm
3pBahLEBGGl6f7fcHVDgqGLUJoRpu+ADU+2owJ2t734Qz9EKlZqq7aZRWyu09sKWxj6ebT6JWs8E
+3jD1PSdbdVpZMxeuWJgLgAXjxjgeMpXkxaQgQsM9sM/WsA85Z0u+JpZUcDaURbJ7C4UOKrHPRJg
BX/+CmNLmkQxNznMFWNpCm3A5P4qOL6abZ+TJ1xl+baTc/ztm3973GgvKznMmiTwg/85LWors9TS
6sQ0A6g3Y/dJcsur5TRbF7fC9XFuLCClLnXxVbqZualDVcmzdyWQAhZPgIIu7uNIKwBdRwuY0zuO
taYfndkeu3Crlf5vqo+cWgmPGstb1fCNc1s5RkdZydpW8GxNzVpUVzugGk6v1ioHa3STugFTxiDl
chdniSZW11SQYzHltiuMBgKCChh2R6l7bMSSl7wxHg+zmR27o7JUjFv1nVZ3bFNWTzrTUlYqjrmd
5G8n+J1Nzm2Xd9DeKreU1Oe2soLBzTfTdrODAUU51RCNaDILjcjtrIDv2pkxGQSVapxU3Jtf/JVc
f4/XAt+zr41kcEBghbuE5Wixj83/9WZOYAVgfziMX0Rxb8+Utb7rLJdzCd9qgzuX4/ZnlX23buRC
uH1qr+bQE6zJvMtdaHF3uSSf7WBso13wmUZtCmsgc69Gm5orV7kL4L5v98WY6YD+9/eWKQWOQvA3
VX9FErjb3WHzGV9cP/Z4xU7eCiw7ABWoeDxZCtyCttN37a15jfW+RpsD19UVYPUOtCpQMaJW5w6m
sJVnjWDIa9LJgl9yNRdtc4trtgLtsz04jc/75os2BhaI+8r9bs2uusDvQscgs9n18Bd/lM5RJ2x3
7Rx6wRwC697dOupTH9Kvg33QsAd7sVMBs/dfYlQDascBjRR3vnNcPAZuFBYDtgVG/zv1gGalTT/A
RZ4WYXalTSfVVVv1ezvnLz+gU71HgDH3cuDWfcHFbqRWVgUwAwSYgV4DWbxVTQ2AUihISCxEgPim
XpvFcksVebOUMDMAdpfXNiD1UbwmdU5Aer6xK4FBJNyVcN9FbCnAf1zHehA3UitQdj9DgCjIAAQo
NSgYfAylgVlzhsyHgA9ITQRISB70O+vGfHPION30VXcIhFYmggRFfCk4eOqkYW54VGUoNGfYAGkI
UHDIACKIVUGlfRUAWpHDUD2mh2NUVU0WgF1jAeUldgzHdU0ofzODYlN4f6WXcCmwdVr4df4nUmDn
esy2AgNIho04c7ZIhoqYUAVQAf9iGFW51DTfdIb/5DP0hYK7+Ds1UEUOVoxc1HiOaIlTEzxjGIjS
x2CcBXu3eIatlIjSqELMmIsV4IdSEwMN4ItwSInT2E+TKIfTKIMxJjVxBnZ/5nXBwmvF5l2m0woC
UDN4tl2p+F1bl4VaGGj/h4ReGHv69Iti2I1iWAFQ8zsSiI4UCZE9w2gKuWAVSYNTIzJM85AWCTy0
ZDYM+UpZw04lmZJkCDXSWDVn2IhVFofsuI0/KFMvKY4zx5AhOT8jeU4VqYC01ou++JCi5Y420AAo
iWT59lwMMFKdGGPlFT6tGAWm93miIQAptgQJV3opoADFRpBaGHZiGYtfKItDOXH/Z5mWaumLElMx
a7aWaekvcHmWZGhGGjNuRFmRDBAyFXOOKvmLfHmX6aeRZJiXhlmXYOYCFKCXjEmUlXOYvpgyjVmY
lFmRZxmYBeCXczmUmPkDm0mAbUkxngmXtoiZiomWMTaOLnCE5BV2rsh/o5h1VnkE/XhnsXAIBhCQ
hJWFYJl6K/B1rdmFXhiAaPmZxlmYxpmcyrmcFGmLYsgBluWNSQOZ1FmZQ2md2EmRj0mdhsmc3vmd
4JmcsDecB6mE5GWPXJeFxGaFGwWFUYgAtQmfp7hdVqiKA9mKr1ieX/iFG2CW4fmfABqgZ5lGdsUB
vjh5QuMCAhqe27mgDvqgy0mc/6kpiwgpdoAGaFrIa97lee65If3oCvUHAFRYn1pHbBPQm8d2ofp5
kLLYnxD6ojA6lO44jTGqnA1aozgKo2W5n66nn/2Hn6u4oVVoTPEJAFiZEqhIol25iifaimCXnyzK
o2bpojlapcs5khIpg1YKlze6pV76nTtKoSuaWL+pheqZj+05f9nzof0QbEuQmwG5pFiIoikKnPq5
ASuAp67Xn3xaAX36pcZJpQ+6AQXAUBcIqGppl4i6qGvpovzpizyKkLBIXq9ppnKUj/U5m/C5qUY6
hXBqACRqn7zZpBMAAa74mysKdni6Aayqp37qp60qqIxqpdBJMRwwA7I6q8qZq/+6+p99+qsUKqb6
2ZqVmnpnup6Z6p5G8KG1iZX1RwK5mZtK6pVY2KSmWqqnmqqrSpatCqux+q2x2qtqyavfSa7iGp7g
mq7qGq6Duq7f+qp8qqd5Oq+pWqzpealCOqRMIAAeyqlHiqTROn9KuopMSpDXCgGomqqqmqfu2rAO
+7AQ+67nOrFzGbEWe7EYu677ua0Ka6/HdqaYaoV41I8kSwQC8K8pEbAKAKoDW7CkaqqmugIIq7Dz
uqoZe7M4m7ELmrPs6qA8+7NA67AMy6r0Wq+oyn+8uYrImqkaUrIka5uCAK3QWoX1uaQEy5swW6oy
u7UKu61eG7Rg+7DeGrZkW7b/Znu2F1uzRduxv3mt96q0XRmqUrsETtusJxsYKsuyVmi1V2utEPC3
Wzuz+jkCC0u4GzACaJu4iru4jNu4Oau2eEqz//d1B/uxTXq1JKqm+7qpJOusKPsMAcuyeuuVV0uw
f4utf4uwqruihNu6eIq4K4C4jju7tFu7tpuxsJu7r0uvhKuwM5u1x2aqBDsB1Cq3cPqm8Nm5Jtup
ADu1o+uVpHu1EJCFMJu6gMu1sZu9rRu7I9C93vu94Hu74ju+5Au04Hu+3pun29u7vaufq4u6YFm6
0EuiAUsC/Jq8nHu3nxsLobuy01q602u91iuzgvt/64u+CJzACny4CtzADrwB/ywAwRIcwRQ8wRFb
wRhswRmcwePrwB78wSD8wdqbvSv6uwSctcKbtEsqt1JrAAjgwieLv526v1FrADbsv6FauqsYwAI8
wBgAAR6wAhgwwq0bwkZ8xEj8vSywxEyswU68wU6cxAgMxRksxVZ8xVhMxCT8u6qLuieawvKbrHOb
m/h7svrLvP9gw2qccKPLt6abAj2cugS8AkE8xHY8AhhAuHn8vXuMxX7cvUwcyII8yIRcyIZ8yIgs
yH+8yIzMyFpcwKtrvaV6ujq8wvUJqi2cBPxqxmY8w2jMv9F6wwk3AAn3Ai9AAzQgAiLQAi3wAA8A
x3Gsuqr7wxhQy3SMx7jcx//eewEXkMS8/MvADMKJnMg4UMzGbMzDnMwosMzLnMzDPAI4gAKK3MgO
zMvoC8zY3MvW3MBDjMexa8dCTMfiHMk9TL2VPL+XnMmbnLyc7MlpvMY3TMoKMACmfMqpvMqtzMOx
DMQIG8QQMAIekMcCncu4PALbbMQYkM2/XMsMzdDO/NAoEM0SHdHS/NCFzMwY3cyHDMLLTM1GfNDf
q9C/bNC9DL4DLdC2nNLg3M+Au88BXMlxm842LLWbzMmdjJU0DAhqfMMsS8qknAIDkAKofAA7TNQu
zc/+XMfh3NBMjQEf8AFNHdVR/dRS7dAWbdEafdWI/MuBzNVaPcgXUNGIXNX/ZF3WDU3VZI3WeOzU
UG3WDC3E4BzE/izL5VyqcCy/lozDoWu/9mvTN10VOw2qoOrT8wzUKXDKq3gA+JzPf+sDPpABGZC6
HgABJ2ACHmACmG3ZdlzLmW0CGGACbf3ZoV3LH+DZU20CLFDVpU3VpZ3abM3UT80CH3ABH8DEXi3I
Ya0DhIwCFyDIvL3E2EzIvAzWuA3MYM3Vww3cxs0C2IwBgnzWTw3VaO3UqL3ao03aoC3dpq3a243d
1D3d313aAC3ame3PmJ26JpC6kJ26PuDKD9ACYUy/K0vTfe3XZ5yyO+2/hB3UQR0CL5ACRH3PLXAA
EODeD+DYj/23HgDZJ9Dg/w7e0CZQ2Z293ZjN1BUe1ReO4ROe4RmuAzrw1B4e3TqQ0B/g4SZu4rx8
4iee4it+AR4OzCoe4iW+xE3NxE9N27Nd27Y927R92zlO27Id3dEd1Syw4Rxu5BCO5GSd4Zyt5J+d
2bV82Z1d2fzc4H97An+73nDs3qzcAiKwikEdqoLdwvxqAPbdyYAd2Po9z/ydAiEQAgAu1DRA4CnQ
5dZ74AoO2RngAXzO4Hz+4LUM6BjQ4ExN6E3t4Ih+Agwt6A2+3ZVt4RRuAh8u6TH+4T3+4yhe2yc+
2xjw4SVe6ZMO6ia+2qMO4p7+6ae+6ahe2h7+5Bru6BG+6IY+6IbO6LMu1f+3TuuKHui1fgJ8/ucN
/usODsTrDQGRDQGO/bcp8N5xrspBGtNs7L+hW9N+HaIAoOYG4NM+bdg5AOdEjdgErsqL3cqu3Ng+
MNnoDtl9vud8XsuQzdDv3tDxztR6Xu8ZAO/3Lu/3rgMR0OAq7u8mntmiLuRCXuoqbuqgfeKQXtZM
7uoOz9ClneQMDeVknesZsOsYMO/unu8an/H5XtUdH/Icf++/ru6TTezHnuyO/QAFzvLTy8oiQNTy
K8/RDq0zbcMCYOZnntOBgO37PQD8nQM5EOf+fQAEjsriPu5/68roDsSOzedP39COzdBTL/U+INVV
39RZv/ER4OGQreIX3/X/Hu7goq4DmA3qCX/iZ2/2lF7pAC/qbz/2pv3oEr/o3Z3oGK/v9P7xGXD1
Vl/LW48Bga/1fk/1hQ/45+4BT8/nxn7u/IzsPpC67l3grAwBdJ4CqozKNPDfPz3PVijYN8/XZ768
ac7T2c7mbA7UN5ADRH0Ab07gB4DKlh/LlY/uHsD0t/8Av87nuJ/7TO3KUg38US38hm/4Jx4BX2/i
el72EY72be/hza8DcR/jyX/iGaD812/i/X4CY8/9J/722w/qyz/ixf/3tUz85/8A6f/76k/W6I8B
vc/7up/7u4/nTV/uf2vnXW7UrQ8EKeHrFUopBgqkwmBgNqFNwZRaBVyx/9lstJkcfL+p7+2WOqRy
ocM6RIQcIA4aLQ4RiSAevafV0vf9/vowCAEJMQwPFQcVDx8eI3R0Hh8kJx8tH30sfTYzMixDJTNO
RC1PUE9JR0FNLTN8MiIlO2V1YFtvP1lzP3N1X30OO4UbKR0fkRsZExFbHhqjkxWT9zwe9bDzIB76
IPIAvyH68Ozwzg7mzFJC2gfElpieoEgE6quoEAAEtPqxuLogAROGzLocOdawaUNkDh0HEGjg0ZPn
zp47gABZw4gxWqEWhyKEFLkRkMgIGzFJSvmgkytgLn3FlBQBlstMlHBWUkmMWCiePEX19JFTZ6iQ
JBk5W/bRI8mOGPb0sf/GJ1DUQFI1Yrwj7ts5iG/QEWnXLsc7L0ucAJSCzwo/f1rUDpRLBh3dhG/G
hnhTZ46HPH77WrwjwkNFa4NFYLjz9I5JxxEQQxbheOPIPiIpzfK5yebPUClnPo6UU7NKnKZOg870
uaToo4Mli2xscjYhxIoTP7VN+DBvwXoM+wWOuA7fvTTgoDNDNocYeGfTRrlngO2Ufdff/uMywIBc
MM7RJRRfB85D83nMT1W/noa1hlNdx5c/n/5jm/Xx59e/nz/99f8BDHCPv+o4j7xvxFtHOSHAWIK7
eaIQgLrqrnMruysA4s47sw4YIDzx7iqvwDj8ckDA9YhIMcU9+mtRNJv/RHFRxhlprFGkE3FUL70R
HyovuQQXNOsLgZBoAkIpJmSrwgu1i0JDucR4p0MzQAxRxPTSy3GqvELQI4EvbQyzNBgtEdPMM2XU
EseHPDjPzb1+BNI5IYl8UC0Jq6MCOyYz7G5DMc7wsMofeXTA0EPbTFTNPb5s1NFG0YxU0klrfNTS
SxtddD0Td3wzThAVNCvKBrmLLsIkleTHwuz63PCLKQcd7wA3DY2D00RNVBNTRyl9TIWQYuxV2GEj
2BVTTfW49dBlC1wDrCoVHFWu7o48NU9VmcRwO1fB6DBWEB2YdVZbDcVVU2PRBTMCFdht18Z2VdAh
3vp+JdZe19LNN1M1/5Vt0zxPPwXSQyGnLfVOVPFZks8MuX1V0G/FDXfZicvtN1f19N0V3o057rje
+eQN+eN7h+0445PRBdBicylu9tlBzRhY2oHUivBahS+Mq2FvH45V4lkpnpjl/1B+1OOjkebYsXiZ
DpnGpDsWE2qoiy5aZZaDPjRiiNcANMqZNawZ4VT3ZLXVDTsUtOcqf8562aHXqzqBqemum12R6bVb
7735rlvulP+z2O22uUZnYG7FvlZPbBfezk/v0l5j7W/bztrcuKvuu+51RRYZXnnX1Vz00Uk/+u9L
A8fa7a25dhhxg61VHGezowABhMcH0ED3wyUvPCGJB0fU4tMv5Tv0X/9hgEHedmHIofmm2+0c+uNL
r97j5E0mPuMSuC/B0aGD5p7ircNdg/tBB+6gg4YTVxzbVd8CyPYnQdjdYW99Jz/4is3V3tHSsce8
5ClvY8s7mvQ8Z73Scc9j/ktXDyDYg0etjGIQHF/5QARBEKltAOp73cHcN7v4cQEEPNCQ7UCANvxx
rXL7G54Dq8dAASYtgQq04dFkaDoHXgqCqBPcxCy4LNaJR33iUVuHPOgqsY2NbPDzh/xSaAAUekd3
ulvhGqqoAfE4QH1cVF8HBtfFRCVAfY76YhkbhcY0dmBuZ+wAu9y4sQj2YGM5VIEdOTbAALarezns
Y/fYhUc8wquPdyz/AR8PWcg6lgCCKmjk0dz4qEia8YtfOqMk2UjJL97KjV7cpKHOeIAirqGIoRzY
AeonlyzWDE8hZFzOSGjCKQ4EhSi0ooeymMU1OCCXuuti0MTIKTW6cZiZXGMbvwhHYipzmex6pDMP
6bE/+nGazpwjHa0pR2xy7JoRbFc3n+nIa6oPksRc4yQtScxLHvOcZ/TXGUEJT0+6MSG9rOLA7Jc7
DdTSdgBppexeSbsm8ICgPJgfLQ/6hX16yHZarKdDD1BFoPFSd0GraMU6oIEvVbFRHE2A7h4FUhXo
Dl4kVaYKktkucp7Umt7U5ja96VJxbpOlKH0jvFa6sZTaFKbPTOlO/3eq05xy1KMfBalRO3pUpBqV
qBVtU0Y1YKiLHmqqVSyfRLFoRcndU59fmGJ3pHg7LvzzZgEdIRQKmlaE8tN2PEAlW1GY1d9JNaoU
mypdHfBRECQgrxvV6FKTOjeTsquKG8tlHG2q0jNyk6Y4valiHRtZyQqVsjVlaU4tW1INbCywjjqq
UpVq1Lxmca93pShel3XRiEJUrlgEgeQGdlDZwrWfsXNltgAAEIJ2p6BgMChtc0fb1751iw6wXdCO
m1qNUpSvzf3sXzs7WMLmcqT2NKkGHpvYjmF2spbNbnUNu1mOcTen5L0pd6WrWc76NaR/BS10kZrX
+jW3fhO7qGkr2v/ahNhuv6/lnUG9msIBCFesUCBrnkT4RC7slrcm/AJB0TZg/8aKv1tM7sQubKjj
JmDDfbXdlz7sqBDb7mi2FK/HpJteyG73u4NN74tPrF4Zg1fGMEYxCOAl4r3qGMQ75rCPOcwD+oIg
r8Yl8rKSm2Ej9xdEJWSy62brVROClZVMTJhZz4pWHnShtwPo8oNNeICC4q/Cbx3uGpR8KBSqOckf
zutve+xjFPYYXiRmF1vrfOIUx1izehZvYaf7Zz5X18+DJnS7AE1jRAvazzjuGArZ9eM4N2rOku6x
owzaXIOy+chGPrKSyxxXNFc4uClM2ywP2lstj9XKbSlbdiQUBQb/N9jBaVVrh2w95jXkesxZoy2n
a6ljflLa0XfGswpoW+f6Tfdo1g10Fhe9TzsjG64eM3GibWzsYz8arnEO9qVBLGT6Clm+nfZ0Ldks
RDOPmq3e4jWEfQvhd7Pafe/DbaxX3QUDfFmt3ZIyQUEE8LQWl2JpdQBBl2Xr5jZK4QwXN7wKWmxt
S7xddp52x6hb0lpWfNvUJvHFN7bxaYP84iKneI7bStBHNfxLKm85ufmqckMhPOEGPxTNAy6egQPc
QxAuIbzlAmFab5ne9U6wP/Bdsyc1zN9HTAjAITYxHtR86hNrbpFRZj2Q37Diyj451xu4w6uPfeZV
d6Gh8pcQDqaN/+lghZ0/W724V8N6iW7H3c5etUKos/DgvHYb2bNOuq1zPdlg16HYAV/km5t9f2nv
XeSYTrO3w73e9r43deq+9Mjzzt1uzV/ZCxo8wAdec4MHu60Nv17ENwrrrZc641fn+CO6ru1hW+KB
KYRluic9Lm7fPOQf7/izL2v0pE/98fu2+ny1/urDn5jj1Q5btm+eyrePu9ydCGs8Zd73v7/fFT/v
fOb3tWjIN3+OlV+18Tdf/GiH/uwPR33bJ+761tG99rfPfc0zHfjg9137i6/8zk+B0k971k/x2g/6
og/y4q/2qq/KcK+JcAsLpgDzeK/39o//vm9yCgcAme90BtBuCv9Q7A6Qr9rP/WSvd3hn877A7urO
Ao3u/vAv//Tv7iKv/ziQ75wv8bTH/EbwB3nQ9U5QAfFnBVmwBeeP/iJQAifwCqrAAl/Q7o7QdYqQ
CD1w7IAwC7Vw+YKQ/YZQAeFv+uTvAa2v8iyvCfcBHzAvCqVwCoHP6dLu9RaPYjQN5sjPWFyuaPIw
Dy+FD7dQbkoQAcWP5jAo7cJwCsHABetu+ypvSbLvQtgCCtkwbBBxBYMvDstuDoMmAWQOC3fFDzNm
D8UNU0DxD3clEBPvBMsODFWQAadQEV9wCXNv7u6tOtZwEtvwCN/wEjuQEAkxa7rQUkoxX4axD0cx
C1ExGb1QFRf/LwV5xgiPEBYXEQZj8OiY5FokERcz0PtOyf++xdb6ru9+cRzTavRUrhxXDh1fzuHS
8RyPkRMLCh7ZEdOmDvAUDuvKkfnKsRPF8Rf7kfEQzuaezvNapxVp7xWTMAplcRYfMVsUJxujkBJt
8AbvBw5jBRzfTRP/kR/rMNfokeVE8SNZDh498s3sUB71sSTf7eoyEvRsbiPN7t10jiBj5RArUSLZ
EEkW8sqs0SHdByIjsvsQEQe5Zu9CD/QyMSnD8VA6siNNEuZCDyWlMh6fsimr0iTHjiOx0iTFseYW
LyZ9ESyRcixDb9eMkiaNyCAbkAWlMCcNrP54siFr8SdpMCcl/7ISd9Ebz3KXkjIsYa/g6rHIZI4j
BxMqDTMrDxMfE1Mjqe71WtIf/RIw5bDvAo4g924BobESpVEhqdEMHRENtcAMGdEtoYASb5IoK3Mg
K1MpNzJoILPqXlMpw3Iyl1IjY9M1MfLdYBP2yNHmXtMsUxM4MdMVEXIzY7EzRbMnJ1A0K7Au7TIX
dbEig1PM0BLq/PErJdMra7MvxZI1a/M2tzM8cfMoswY8HTMcZ1I4VRM4bfImjfM4dxLBzhA0KZA5
R/MCX/Au8XIDqXM91xPqvvM6b5M8j3I2x7IrD5RAIzM7W9M2FzRA3UrXqNPzLrM/h/MgoxEnSZMR
7RP76PMtOv+0OW+RNPVzKL9vzCrUOi0z13CTNv0OO3sTHL9SRl3yJanON1+0Ro9yQgfOLG3NP9mT
OjMzQ8kwJ++zQz/zQ/tBVUL0PkmzNIWSBRkQlXquOinUSi9TOxmTRufwNQOSN0PPS6fuOmfUMRlv
IAUOS9WUJveuSiUHwsSQLTV0Q5GTOZNUSZc0DZt0NJ9U30zTDaXTG4kQXJixUMtTayR0UBX1/dQy
TuX0PaeRQ5v0TvE0NCtkT520T6EzOk/JIhf1U0G1SmQyVEm1SpyOCt1zTuk0PqtRBvHU3jBVRJ3z
Of+UUyOnCks1Vwf1R3V1UU/1GYmTSBPSSKEwVmG1UmHtM43/NVM1tVZtlT8FtVeldVqJ8Fd5Zkpv
EgkhNVLrdFLnE1lB1BGXVVY11U+jVEpRFVdzkFrZVVetdfawdS0RsS379EiNVVnB1SHxdVyLtVw3
FVCNUF0fb13blRUF9mDfdWDjNVizlV6f1F7v9VjztQmPdVypAChJ9F9NNGChNWERVmE/NmQ9dmQX
FlU5Nls3xGFXtVu9FV8nFjQrVk+XtV+ftERRVi5K9mQXVmB11mRz9md9Nmjl9WZTVlWJVVIj1mVf
Vklj1mLJFT/zU2OJdiCAtmettmqxFkOndmvvslwhNlb3lRaXFg2bVmZnlk9rVmq5dm3Ztm3dtmBU
dmVZ1U5jyXZsl7ZpnZZZM9Zm37Zv/fZv2adrvbZYLTZs5dJuK7Vs85Zm+7RrAfdxIZdr23JYH5Zl
MTVsETdz87RiF3dW09ZxIzd0RVdbHddfrcVyQ9RwNXd1kc5wLZZxy7V0nXV0aTfyJvd2KVdTv/Zy
y5Z1fRcS97VzR9R0cbd4a7c4Zdd4lXfyiPctkRZse/d3pfcaXfdsMbZ5lzd7k3d7tbd7uTd3sfd0
59Yz63Z6zXc5q9dYYTd8xeZ7vfd9k5d95ZfyUNc+Vfd8KzUIAAA7
------=_NextPart_94915C5ABAF209EF376268C8--

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


From mailnull@www1.ietf.org  Thu Dec 12 05:19:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18716
	for <seamoby-archive@odin.ietf.org>; Thu, 12 Dec 2002 05:19:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCALmN08682
	for seamoby-archive@odin.ietf.org; Thu, 12 Dec 2002 05:21:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCALmv08679
	for <seamoby-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 05:21:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18694
	for <seamoby-web-archive@ietf.org>; Thu, 12 Dec 2002 05:18:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBC9mOv06950;
	Thu, 12 Dec 2002 04:48:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBC9lMv06931
	for <seamoby@optimus.ietf.org>; Thu, 12 Dec 2002 04:47:22 -0500
Received: from directvinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18101
	for <seamoby@ietf.org>; Thu, 12 Dec 2002 04:44:12 -0500 (EST)
Message-ID: <41125-220021241294658223@directvinternet.com>
From: "Charly Calder Faux Furs" <ccalder@directvinternet.com>
To: seamoby@ietf.org
Date: Thu, 12 Dec 2002 01:46:58 -0800
MIME-Version: 1.0
Content-Type: multipart/related; 
	boundary="----=_NextPart_94915C5ABAF209EF376268C8"
Subject: [Seamoby] Christmas Greetings!
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: multipart/alternative; 
	boundary="----=_NextPart_84815C5ABAF209EF376268C8"

------=_NextPart_84815C5ABAF209EF376268C8
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

=09 =09=09 =09=20

=20



Faux Chinchilla

Faux Fox=20

Manhattan Mink=09=09=09=09=09 =09=09=09=09 =09=09=09=09 =20
=09=09=09=09 =20

Midnight Mink Faux Fur Throw:=20

Faux Fur Throws are ideal choice to make your living space more cozy, eleg=
ant or plain cool=2E Charly Calder throws come in a variety of best qualit=
y TISSAVEL Faux Furs (Black & Brown Mink, Sable, Red & Purple Fox, Wolf an=
d more)=20
Our exclusive offer only available at: www=2Echarlycalder=2Ecom=20


Forward this e-mail to a friend, and  automatically  enter to WIN!=20

Happy Holidays!=20

=20




If you wish no longer to receive e-mail offers from us, send e-mail to cca=
lder@directvinternet=2Ecom, with subject line Remove=2E We apologize for t=
he inconvenience=2E=20
------=_NextPart_84815C5ABAF209EF376268C8
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html>



=09<head>

=09=09<title>Charly Calder Holiday Gift Ideas </title>

=09</head>



<BODY BGCOLOR=3D"GHOSTWHITE" text=3D"9999CC" link=3D"white" vlink=3D"white=
" alink=3D"white">
<center>
<table width=3D"560" bgcolor=3D"333333" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"0" align=3D"center">

<tr>
</a></td>
</tr>
<tr valign=3D"top">
<td width=3D"159">
<table width=3D"25" bgcolor=3D"330000" border=3D"0" cellspacing=3D"0" cell=
padding=3D"4">
<tr>
</tr>


</tr><p align=3D"CENTER">

<br>
<center>
<a href=3D"http://www=2Echarlycalder=2Ecom/cavalli2=2Ehtm"><IMG SRC=3D"htt=
p://www=2Echarlycalder=2Ecom/cavallimini=2Ejpg" WIDTH=3D"120" HEIGHT=3D"16=
0" alt=3D"Click for more Information!"><br>
Faux Chinchilla<br>
<a href=3D"http://www=2Echarlycalder=2Ecom/lotus22=2Ehtm"><img src=3D"http=
://www=2Echarlycalder=2Ecom/reklotus=2Ejpg" width=3D"120" height=3D"163" a=
lt=3D"Click for more Information!"><br>
Faux Fox <br>
<a href=3D"http://www=2Echarlycalder=2Ecom/manhattanii=2Ehtm"><img src=3D"=
http://www=2Echarlycalder=2Ecom/manhattanrek=2Ejpg" width=3D"120" height=3D=
"167" alt=3D"Click for more Information!"><br>
Manhattan Mink=09=09=09=09=09



</tr>

</table>

</td>

=09=09=09=09
=09=09=09=09
<td width=3D"600" bgcolor=3D"333333"><BR>
<center>=09=09=09=09
<td width=3D"420" bgcolor=3D"333333"><BR>
<center>
<img src=3D"cid:1856115-2200212412934188611163@directvinternet=2Ecom" widt=
h=3D"421" height=3D"72" usemap=3D"#title1" border=3D"0">
<img src=3D"cid:2064716-2200212412934188611164@directvinternet=2Ecom" widt=
h=3D"354" height=3D"128" usemap=3D"#title1" border=3D"0">


 =20
<br><img src=3D"http://www=2Echarlycalder=2Ecom/199=2Egif" height=3D"41 wi=
dth=3D"368">
<a href=3D"http://www=2Echarlycalder=2Ecom/midnightthrow=2Ehtm"><font colo=
r=3D"9999CC"><FONT SIZE=3D"4">Midnight Mink Faux Fur Throw:</a></FONT>
<br>
<font size=3D4">

<a href=3D"http://www=2Echarlycalder=2Ecom/throws=2Ehtm">
<img src=3D"HTTP://WWW=2ECHARLY=2ECC/midnightreklama=2Ejpg" height=3D"300"=
 width=3D"400"></a><br>

Faux Fur Throws are ideal choice to make your living space more cozy, eleg=
ant or plain cool=2E Charly Calder throws come in a variety of best qualit=
y TISSAVEL Faux Furs <font color=3D"white">(Black & Brown Mink, Sable, Red=
 & Purple Fox, Wolf and more)



<img src=3D"http://www=2Echarlycalder=2Ecom/moreinfo=2Egif" height=3D"41" =
width=3D"368">

<br>
Our exclusive offer only available at: <A HREF=3D"HTTP://WWW=2ECHARLYCALDE=
R=2ECOM">www=2Echarlycalder=2Ecom
<BR><BR><img src=3D"http://www=2Echarlycalder=2Ecom/rfox=2Egif"></a><br>
Forward this e-mail to a friend, and  automatically  enter to WIN!
<BR><BR>
Happy Holidays!
<table width=3D"150" border=3D"0" cellspacing=3D"0" cellpadding=3D"5" alig=
n=3D"right"><br>

<tr>

<td>
<center>



</td>
</tr>
</table><BR><bR><p ALIGN=3D"JUSTIFY"><font face=3D"Verdana,Arial,Helvetica=
,sans-serif" size=3D"2">







<br></a><br>
If you wish no longer to receive e-mail offers from us, send e-mail to cca=
lder@directvinternet=2Ecom, with subject line Remove=2E
We apologize for the inconvenience=2E=20















<map name=3D"title1">
<area shape=3D"rect" coords=3D"2,1,424,42" href=3D"http://www=2Echarlycald=
er=2Ecom" title=3D"">
<area shape=3D"rect" coords=3D"158,47,223,67" href=3D"http://www=2Echarlyc=
alder=2Ecom" title=3D"">
<area shape=3D"rect" coords=3D"225,48,422,67" href=3D"http://www=2Echarlyc=
alder=2Ecom" title=3D"">
<area shape=3D"default" nohref>
</map>

------=_NextPart_84815C5ABAF209EF376268C8--

------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: image/gif; name="rektop.gif"
Content-Transfer-Encoding: base64
Content-Description: rektop.gif
Content-Id: <1856115-2200212412934188611163@directvinternet.com>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhpQFHANUAAHR1cF1niB0dHWp3oVRde2l2niwsLCkpKXB+qzc4OigoKIKTykpSaXyMvzxB
UiQkJCIiIiYmJkdMW2Nuk3aFtCAgIEVMYxkZGSotNRUVFTk+TH+QxIaY0VdgfTI1QXF/rTU6SU5W
cCQlKjM4RVFac0BGWjs9RS4xOyEiJhscIB4gIygpL42h4PLz58LDumBgXYea1pGRi+fn3EFEUHiH
uJ2el0dIRoWFgFRUUqmqotrb0c7Pxba2ri4uLo2g3C8vLyH5BAAAAAAALAAAAAClAUcAAAb/wJ9w
+Ov1DEjD4aBQRB7Q6ANCpUqjkeYyaTQSv+CweEwuf41JJbP5vE6r7kdWsUV6zfgufg9GJ5drTnFQ
VVZuc3QHaXd8jXxdaUtNgoNvhodailyMjp2eZn5qbFFUFaanqKmXmYt6n2NdsZyOoUqjhBCpuqir
dJthsrF9wbOvQrWSClKFu80VcFBzmgauxq+hyW24uc67l9LTxdbje9hNuKYCAiIaJQTv8PEaHuqm
EFCsrT3kRbW/neaUvUmnToOGeAgJzKv3DF+4YUfSULsDSeJEfgFJcaugToDBEAnjhVjI0JCWf/we
RZTUphRBAR7ahZSnQUTJe3J82dmXsies/5VMCKU7+IGDj6NIkyr1QSNACRENH2SaRg1jRIsXG/mR
JJQj0Q1LwyKlMcGCgoY6eQ7xJzEWVpTGtgrkVjBEgKJi8/rYMCAEPXsOufjMs1IQXQEY3H0Aqzcs
hw8ESggALLWOuMFWkTB5kktAiQGNQx+dgCEquJ3jtkoChLpcYc6mSkwwKlrvgBH3fHG6mqzOxD+r
H6bWrKyzBwIfatfeMMED4LRqMQMjzhmxhQK0lTceYAHqvQiWpQ+WK7QD47w0PqhXjyB72BLPcEpN
O9yWIGl2XFOfUoHBebHprfdBe3oxAAF9axHnRARZUKUggydldc0RQR1onl4IrBfPXerR0P/YBhag
pUl04hFR2BQMIKDXBusFEM8A6zXGQQAYfDdiiT2dOIUG/x3Fl0L0dCTABUNeYOQFKowwAgMEqOjD
B5NV4MAEJ+R0Y1zEPRCABNHoRqIYrz1QwQgeKvUjSUIWeWQGSjLp5AYQgJffMdT1MAEIgf0hiAQT
MNDgnNdkOYJ7PlAwAQEjnHAkkWk26pE7BfToAwcGVlYVjmcgocwKySW1AQIkWACCCkc62mhMBEzQ
qVIB5HYlpnGtxFkHSXFQFgYdNdPRohn0msEFKzzWEa0+4IngJydCcBQNrgL6k2acMVArd7gypMuu
a/qK5AbMynlpEdA+4MBRrVoqirhHdSD/x6vIZskYAoj6+mup1uqaJgoOEFDmpBWY+6V4aARFbFMO
iCAvvVE60+gFGjAwQHYGevsvrFplCUEASE0gWcKXLPPSmkaC4OHGAhBw1ADNTtwPMbLYsiNS5XpZ
RrLSjrbxKR1rxJE6vF4gsg/qSlxRhcT6UIKVXF2cbsosNy0MuC4nF4ADKhxsZK7xFcLMKR2lcKQK
FhylQW47OQ2M09WYSKEyJDBlwQpWXx2l1lqjIuSiICTXAdNnoO23yu1WWMKkHdhkj3yITNLSzjyD
EIKHHIQgpMlP9iux2my9pcQTFWiA1AeWj9h0P7Y8MS7QuB6OxSSKC3W342Xuba5EFVZQ/7TsrPPX
Ke4Oav6WWy6v0MG+CCDg4jsdaODACvJptDXji6pwlAXN+l52y9ZP5MpWTzg8FgKHIl+CA7jFUTfX
PBuZgYqgr3t9Rdn7nrYxFnNbrWmTAKL/OSBI0IGq5/lACGwyuaNAqXrYAw5raGcYj3xOANXDCvAq
9AEaBAl/U9mfMk7gPwB+LgSlcRVVWCKmkiGFAA3JAhQ4MoGjhMByOgEOVvTXFt4UhyMxkQkBGKA8
B1SCbnZTUwZO90KkqYGG8Uui9shTQgwYRAMh6MBIHLC8QQARfUXqlVEOOLsk6u+LvZMQ/Tb3gBJs
gIBRmcoMFaCBGVDRAU8kYJQK6AMCTP/GSm9JBuv2OAoIqOMED4RgZcJokQM8YVBoxEmDfBMJBXjA
jVSMY65wksE1rFAdYTuKHftFCnVQTgNoSUQg+EhK36hmLhuJDxYYpI0q2CuLGSiTBgSZuFIuUDNf
tKUpJ4hKXkCDlctIZRCFSLkA3HGQkQDjKEnJultephGamkIHOjBJfCQij5tBh70uQDk73vFPjaRE
JVw3pAzAjEihFOUt//CEDhizHpS85gyzORBVKJJ1rdyZz5DigMm4kmefPCYwx3mFRZYNl7co6B5b
chhTqS8DGDsKCgRJ0C5lAp/aKOhplqgncUqhlgLhz0sWpj5AalId8UwERjNa0S4JZ4z/xfnABKo5
n3UilBKu3AVAp8coTqrzHPX0ZU551qsTXi0qcoBQhKgDgQ5ACZ7WtKkocOoSnDVPZ/q8AJuQAgJG
3e0CbSuWP3FS1axtzSThwIYem7m/H0yAAgKKa1wJNb2xllWoP6RbIaIQIeDddI+5VEAH4CrXwu4r
KQWA51WDeUVnoLU1r4gmBJJjAZomToPizKlOh0S5EVzNOd+5RWegCA+SIYZnGojUBganyV85EbRw
gIAHehDDJbTTB+/0J1/zB4jWbUMX0BgIYtzxju5s9ShdJdIFMJAvAjjASSCoV0EI0IHudEQEBBTB
BDw0AH/5FZdIPKIT/KOdpCDAqx05/wg8oquOEjDgLMxYQRSDxI4QgDBXIAABeG4EPwUykiUzWFV5
fbCCeljAQHUTXgeqddr2FmW1HcEASEJQvmN9Ilw1G8D9VFlQN5RVSKcQQWW5eZQRZEAFBfDBBDjM
HxEQgK4IWAEIjsIBC2TyKKz1AQNOnDGsYcwB4HRZzT4wy7ktlqVBZRzHSrCCoQiYxgzwAFJOMK+I
LqWrQgIBaDyFAhSUqQAY2NcHwKmW72oumxBggIAf8wEXhSC/KhBBUrCsDhEEAMZgo3GQOtLCOl7A
y0kJwAVCsIENjMBfa+nvmYMirtkkJT0DeIcDQEDlfRGAURGlgRzVUaZLh8BH7pizz/+chBQ4ScVZ
nrDYqj5g3YSZ9XlKFpIHQgCaEVOuV5Z29ToOyxzs1HEFNZsUUjhgzhL3ysoWuFomfVjb4vSZKfd1
tV5TaapZg2bFnqwV+MDCASkfxVc3XgoJjoSCTtGABCNIcbFU8DNhI4UBiO6b0/QEmxPUxFHqe/Z5
eYaB/xjKSQyYMY1RoNwVGDVfzy115L7JrkQ3raNCQVPX1DeCYaugI59e1pCGlONLnyDj7qFBBiww
IxMPMQDUsxTg8qCpJ6zg2ctC+Z5NlaYVQPEuSWHATn2QAZj7YOYCULcPCoCCXmHAKCZ/tgVG4Nxi
+8DkKmDMBrR6AdpowH3snIKVY27/AaDTXB0o0IAFkJOdDgxl2CXwVYoR4G2e94oCNvNAsAPwq54f
pQApKIGTEFB3g98diriDrH72s42hGsnvyGXUBVY1gaJnAAPGtvJ5jWTlCcgrlvwkkgdW8ICGE0ZB
zhtqkUg9AfSuStBGEjoB6v4mKhKgqwgoAAkKAHe39Us31tBR5yTlI/UcDx4CoqsBR8A4ykmLApTb
y0SVS+O0P97RPrBAr07nA6oX1di9uvGOqT+2zjeSMxp4cql9j5Dgi2UDoEwH5RCQggzkvQFHoUDb
fXUUEvTKA7Xfi6/6TBsOFED683IBjMFeCOQJapVQHjMkpLZvHUFjDmB0VmZiKmBp/79yHnznKxOI
FAXAMKamAKj2eTeFZPwxJBl3FKlzCkeHFMkmPTDTKxdQM5N3JCJGAgRAAhOAABvAAbenCCsHCjqS
CyUgfgNmQKDkEia0LKTybDSwAoPmdxxQPISyehdgUjSwKBcwZYviJJSSHYLkIGjWOVs2hErxAQyQ
NRxBOTSAAPmHFBU3Ke3ndGJRACBgAWHFAR1wAimwJBOAeosnNt/kgR84eOC1TLBRgtFXD+rgI8Wz
FFJoUsjFADSQSRxAKhlwAjkodEaxN5cDEGq1VoZRASk4GrpVCjnGAScQAH3iI6SyT0+iXNnSKyIQ
AjiYMqkRJtwgYYelHBzQFyEkH/9AqGdHkosbsAKSsgE1c2lGYkBp0imPoShTmBR9RgMQJDT7cYuP
I4YC1IukUAGGCDNOogK08SkXIHRHgQCnCI2ItxSCNiQR5Rx58kwgOE/nAAHnIY32YAp0ZYwudCQ3
xgE0QCq0sYEg4I9MqIScZ2G0kDkIpXVJURpXkAvP5o8ogHjI6HcDkCaSwgElECeeZ4CFMRfpIALu
ACPn9wGR1nVWFQ0MQggkAGFCEoRPMkAwUSYb8H9GwgEbwGCgYXaooAB9NgE2YSQOkInFFgDP4CWn
hA7rcBAwInwscpLOoTpJFQUVYGVtxoQmc2krADmXxiNMMTVGggJbNGJmNC1FZgr/nsMBlCQ65GBm
uHRInYIbvuiVe2GTV5iTQpJJjcdxRiE5AwCU6UUDIRBagueRCsloESU78/GJGMMBdkQkYcMBRSYA
yUEC8WEKDJAdbYYB75gZoNcVsWYqKZkTKpVZjYVFaSJUOfMGuIE+WkVlxeaOuEc6D6JNX4c1HIYI
liRSt8lgNJcKosliq8OWPhEMb4kLq6SUIHY4sNYNWuNSgRgrvIQJ+6NNwLVXHkYQz0GcbXkVU8VY
VUU3qyNPfzVQefWchwBSLNUZKAAC9HdAm7gywAFUhbcR4mlRC5QMoTdt/HmewZVUrJQP8JgSQLEg
SpUN9dlSCmpEYjQeH3mgI0Sf/wSlVLlDCtAZnbGSTIEggh+lm4ykoYG1UKw0oiClTiEKkiZjKy0E
SipHIsigRxy6SrxFSBtKojZ6oyXKBiupkjMaXgNKoEDBBEjUWwZKoaLETEg6o3CBGZ0oVeKVpJVE
pAuSDw0KpN55RJ4YpTWkaPOkTF5KSLRDQhBgiEaJdROjaCfaox+aQFj6pW76psokPz2YI1e6aF5a
SHAKpj/anXL6ol9qPWDUCjjilkqkPZhTp4WaqOH0AC9HOD7Fg4BDqEr0NPKpqJYaP/MDK5kjqZfa
p3NqFXWqB5zaqYWJKWwqQbJABn+zqqw6n8iJR9/ig1y6pZnqcKx6q/3lNxRzNv+42quruqvylqrB
6qtmA6xgwjLGyon09gQGVaUqQQzJGq3SOq3UWq3Weq2qyhtrsEvY2q3e+q3gGq7iOqiIuqTjeq7o
mq7quq7UyqW1KgQJIAEmAAYmIAH2Ggb2Kq/0KgEJMATxyq9DIAEzMAQzMLD/CrBCUK/2Oq8Ji7A/
cK9CMAMIq7D+mq/9GrESAAb56rA/ILEbO68bOwb/erEEa68ky7BEgLLsurIsa63ISgYmwAIIIAT6
+gPwhwAskLE/0AE0ywIDwAIN0LBCgLMDu7MwwAJIiwD9ygIUMAQU0LQSgLQsEABDEABSC7QM8ANW
q7M2m7M/kAAwAAMmkAA4K7X/PBu1SEu1QkABLAAGV8u0Rcu2V0u1VwsDBUCyQtABR5u0/ToDDSC1
MEACa8u1P1AAatuyiJu46fq38xp7HSuzM8ACBfADMTuvBZCzlzuwb/W1QJu3STsBRzu5TOu0TWsC
AbAALLAAVSu5AVAAYau1XhuxqVu4LMCzOGu3ZcsApou6MOC0bfsFqYuKRyu2P8C2AXC8W/IDwRsA
fyu4Q9ABnxu6YJu6b4W0WUsBMFC0EzC1itu93vutJFC7MQsDCbC9Gfu35Su5YKu6UXu3R2sC0Ou8
R5u1lMuzytu0a4u/48sC9Lu1QrC9DOC/Q7C9OBu0kUu+NEu/CcACR+u8bOu2//jrVpJbvL9LBKPL
uRH8A/ObsDwLvREcvqrLttkbvtz7vSZ8wtG6vlZbuwuguj8QvnrLwNBrvwsQuEg7AQ2AwJHrwhb8
thdsteGLv/7rtyxgurELr6jLAgNrtZMLBlbrwWtbwUNwwZTLtHIrtTo7ugkAvU38uDzsu84rBEdL
wWGbuiWMwmicxiVyuTBAAUlsvwt8wwyMwDuLtAuAAKGbsLP7BSL8tNiLvzCgujhrxG87AbCrsyRA
tQwwwXXcxUTQwrQ7sA8sBAEguFQcs4ZytH48sD68AEVbxV8cxWGswW3LtjMAAw2wyIerxqzcyuMQ
ufwLvSxAsperuqjbxXHcAf+LXMRD0MBD4LxU/LQv/LYFIAFsWwDb68IC/MBRq7awfLEmkLUkLLWT
O8n3e81CcLnVLMWwuwDMywKjTMphLLjQG7SeG8JtO7bN7Mrs3M6e0ACqu8COHLU8a7Wf/AN43K8L
0LQdMLAkTAHfLLoRLMyoi7w1nAD+i7OGzMTHi7oPe8Zla7gN/LcGTb7Ge7yjG7yuy8DzetHHm7Gj
e8D92s/DzLQBnQC8W738S8EBe8bu/NIwHQaJnM2E+wML0K8mYM5DwABNPAGWPLMvvLfqi83FSwHt
u7qJ7LXTKwErfLUPfbjpK7UkELVADbuD9bZNi9Vx+7Z0i78ErLxATQJCfbf/lHvFgRvFLb3KMb3W
MJ0A0AwGJIu38DrXHYu3EJus9XrPwDoDdl3THXvXbB3Ygj3YhF3Yhn3YiJ3Yir3YjN3Yjv3YkB3Z
kj3ZlF3Zln3ZmJ3Zmr3ZnN3Znv3ZoB3aoj3apF3apn3aqJ3aqr3arI3GCXADLvAC7GoDMeACONDa
uN3KCdACvC3b6ooDvN0Ccp3bxO29ANACNWADQvACMRADN3CxNvACNnADt00Er30DNmACAPDcRIAD
za3cQhDdNrDd4O0INdACAHCxANDcADAEOPACCRAD5f0Cvu3e8P0D0/3dREDb6Y0DN9DeRLDe6W3f
0w3gxX3gZBADLeDbORDc/y0gA7et4DKA3t094S2gAzsQ3L593sHtAv0q4cF9A53gAi0AryQe3Dug
3CQ+4eXNAxReA/064QkAABbO2yL+AzcQ3Dxg4TIArxnO2zJQA0Kw4kBe3Qh+5EMAADrQAjtQA8cd
5ABA4jrwAwruAgYuBOddAwreAjmg4DnwA08OAC9A4i5A5Q9+A+c95Y1QAxPuAlp+4TEAABle5iTO
A1d+3Dmw2wCA5yYw4XaeAxMu20sO2zZO4u3d4LFN4xRO4jtwAy4u5Ege6UrO5DVA4jf+A4Gu4Fc+
5CWO6cL9AzrQ4y7uAs3d4MKt4Dfu4kaOB2zeAm6+5ABuA7xtAyRe30MgA/8yoOA60OB7zuRD0OA5
ANxl/gKu/gPEzgM/wNtdXtvFTuLKvds9HumRruCyTeJG7uLMveBgQOKc3u0n7uALTu1CIO6NwO3J
/ulCkOFjru1fwOETLgNTruCQDuauTuzDXuz2fu7gTued/gPmLu1HLu6PDq+87d3sTgTmnvAlDuzw
CuDkTu58YO4ZDuDALdy1DgYVfwMTLuTHreY/8Oj5HvLFHuhC8N7dfvIAj+DiTuyu3uplDvFDoPDd
zvI50Opf/vAHvwfmnuMtwAOAjtz+nvNDsAPx3gK3bQJLrgM1kOEyEN34/vQvf+E1YOrt/e//nvLF
Te6Kztsebua2fvIyD+Z4Nf7lXj/uQm8G/77lvM0D/XrxYHADMYDfO+DeP/7g7S3y917mP8Dhdo/y
V4/1uQ3xCUDfq/4Kg3/fKXH1h1/eZODWdG3fX28G0R35gC/tMJ+uf1/5mm+tzM346bremx/6oj/6
pF/6pn/6qJ/6qr/6rN/6rv/66xoEADs=
------=_NextPart_94915C5ABAF209EF376268C8
Content-Type: image/gif; name="holidaygift.gif"
Content-Transfer-Encoding: base64
Content-Description: holidaygift.gif
Content-Id: <2064716-2200212412934188611164@directvinternet.com>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhYgGAANUAADExMS4QEC0tLSUlJTEaGrNKaSkpKSEgIDIrKxoZGSskJDAVFSoODmkzQh0d
HY+DsyMbGxoWFjEiIisbG1UnMiUQEM4zVo1slB0WFo59q42f3SISEno6TY2d2h0ZGY5xm42g35CR
xo+JuyAUFDAoKI2Z1Y52oY56po1liicgIBgXFyYWFh4TE4+Gt5lGYJCOw4yX0tUtUcE/YEAcIY+M
v+IhSNsnTJCXz4xfgY+UzBsUFOgcQ42h4I2b2I+Ar4pAVyH5BAAAAAAALAAAAABiAYAAAAb/QAAA
MUQYjyQEabmUkCTQqJQgoRKu2Kx2y+16v+CwmFutjs/otHrN9patbbK1LK07nUzlcT/sC/+AgYJE
e3tMTU92UHNYb3GPkG6Mb5RZlZdwkZqba5iYlpOhnqFXdFSKUE+HeoWEQkSCsYGErUmHd6iLjpy8
vWBmvsHCwru8wJSoqqutfbCyz7SFtky4doxxC1fZBNvd2t/c4N7h5NvD51vj6uLs5e3r7uTo842l
p8l4S6yFfs7Ps0UMKaGWSFGmg1zgKXzHMN5Ch/TOPFSXbUHFi9wwWswIsePEdhEhXVKkLA8zV/9i
RUMysAkqUl68aZzJcaNNmjdr4tToEZyw/4k7dQrNSTRo0aE8P8o7Zw4NHZL59vHxl3KWtJaqciHU
IjOjxa9gw4odS7as2bBIhfZc283o2bdw48o1m5ZoQ6V4f02yU1LfST9V/7TSc8tgMa7h5ipezFhs
XbePvTaeTLny2MhHM0Me9+Up36hJ+KEM/OrqrYJ1wty0zLp1WcwzXcuePRu2TrlqJXlOlc/vX9Kl
pVEzvPXbRdrIkytfzrw57cRbzOyOUlKqEcDAhRMknjCx8+/gWQewOH5B+fPk05tXj369+/blw4df
Gv0eddB/qabUjsjaYeNwwcfegO8RKGCBCLYn31wHNmjggwlC6CCCC1IGXRf45BHaEc0AF/+QEadx
191bE5Yo4YkRphifcyYWGMB4L5oH44wy1hjjjTTiaGOOKE5Y4Vv0iVLHIRuK5qEhIab2n3dknZfj
kztGqeOUUFIpZYtY9shelVxe6aWVYHYZ5npZqqglhWcF2QhU+hR5nX77IbGdf10cFxZ6VL6o5558
9unnn4Dy+SWUZhYq4Jg4Bqrooow2quegURp6ZouvNWXPdMpY9+aRcg6n5FZmOSmjo6SWaiqkiIrJ
pamstuqqn6iqGquU7pGl5hyfmTTVK6Qh2Z8iEyQ0lqivFmssoLOmOuqxzDZbbLKyCqpjrWhZWg9J
y3A4WlWd/hpFcZLdSaaz5JZr7rnopqv/7qMwVqrFdLxlqy2nWGU1hQTBptPkAg1w4O8Mf/rrb7EC
N7DnDC4UQIGjMwi88LqmzvBDARRTbDCgFBTgwp8ZV/zDixS4wEGjAo/saL8cXAwxqQs07LBjcgzZ
m5vbxllvNUuG+1W7Fuzgs8l9+uxzsUJbsGcBPhtNstAFrOwoBTIILfUONmzspw0+F8AAn1FLbXQM
WTcqNak976C0045yIHUBK6D1rn33EflbYN2i9i2++ooLY9k7AM3n2K8WvSffaTONtqIMID314hYA
vGcDPtdw9ouKSz2y4YwC3mjZkx+uqNpCc1BtzFL0RTN2Nid5txYT2LkzmXz7vafmrQqu/6cLSRce
tud/dr344jE4rmfZH+tJgdQ1xBDDi5gvSvuinPPOKOShO2ZthrrykV29dkcRbL6t69zui7H/+byp
thuvMqOg79C09HsmPrUFIvsrQw1e98nBwy/Kn7TwAWieos4XqOjBb4DVgxkZ+CKvedGNSPbyXha+
57r0DC905hOan6AGNp/ZQAayY17ublcxP/3AAvjbQQ1kQIH2vW9PHCzaxxKmMeNVjH964kAJFXW8
tW3tYB2MwcK2trWKcYCIAajcEAOQsKJRbIlIRCIBoYa1pH3MgHzigAyqaDar/WkGBejgDmLQNB1S
jE8z2KLQyIjDACbQbViYALz6MhjUQf8Dgt2T4/ey0Da9XfBnGRxaFCvHuBlEUXBEJBwSZ8A35FXu
hQHw3+JkgMX2hbByi/Jd3yLJSSLOIAYyiGIkDUdETCbyd0fspCoZILUoSnJqBcDiixj5O6qtL4cp
nJoMfPe4XOpSeFKbgfVIV7oGOnA/EMSZHCdIgPDpbVTl81MrGUBNBmjydzYwZDWLVk0G8K2bn6wl
LLt5zVpaoJqW7CY1K6fOds7Ah+3sZiTbyTQkspOTjQydKA8pNHWW83fnrGY4xVmDBqgTd+LUHAV8
uTitidBn1LJI+OKIqd7UEU4qSaYEFOC9Kuyxda1r2wrG07YcckCMBShZyaa5TqnZoGL/jYxBN7lZ
zW/W1GsUu984qfkDl8qAYmJMGjr1qU52xrOaPRWaNtGpUpVuM2vUTBjfbkhJodnAAhYw6FGpyVIG
JNWDPw3j/LrJtxqkVIe5rMFSFyq0FeZ0cUT0nQVGpkOfhVJPYlzRV7iRr2vFzZib4haRNloHPXq0
mQtoHVhGSqaEirOaPbSrOn+QSxc81Wxk7WdUpWZZagZgoFBlwAxyKYOlvjKgDEhnUTW71cqh9rK1
vKzWvFnLI7IytFuFrUBJa1pCohahYzQtaENJTb4JsZsc8OVNVWhI45V2cEKLaNuaeYV8sSl7x0Qm
ExRAAo5yFArL/GhiFyBS8oz0oY6d/1o1K0fcya7xsq+1KQNQ6k4uzha4Mm2na4f6M/2y9qiPpGdC
ZVvc2nIVt7m9rc+qCdzXrpem8yVqNyO7A0NGVq3tbN8OllvQVfKpbDXQa0XiWN3d0PGiD1QdePEm
3pBahLEBGGl6f7fcHVDgqGLUJoRpu+ADU+2owJ2t734Qz9EKlZqq7aZRWyu09sKWxj6ebT6JWs8E
+3jD1PSdbdVpZMxeuWJgLgAXjxjgeMpXkxaQgQsM9sM/WsA85Z0u+JpZUcDaURbJ7C4UOKrHPRJg
BX/+CmNLmkQxNznMFWNpCm3A5P4qOL6abZ+TJ1xl+baTc/ztm3973GgvKznMmiTwg/85LWors9TS
6sQ0A6g3Y/dJcsur5TRbF7fC9XFuLCClLnXxVbqZualDVcmzdyWQAhZPgIIu7uNIKwBdRwuY0zuO
taYfndkeu3Crlf5vqo+cWgmPGstb1fCNc1s5RkdZydpW8GxNzVpUVzugGk6v1ioHa3STugFTxiDl
chdniSZW11SQYzHltiuMBgKCChh2R6l7bMSSl7wxHg+zmR27o7JUjFv1nVZ3bFNWTzrTUlYqjrmd
5G8n+J1Nzm2Xd9DeKreU1Oe2soLBzTfTdrODAUU51RCNaDILjcjtrIDv2pkxGQSVapxU3Jtf/JVc
f4/XAt+zr41kcEBghbuE5Wixj83/9WZOYAVgfziMX0Rxb8+Utb7rLJdzCd9qgzuX4/ZnlX23buRC
uH1qr+bQE6zJvMtdaHF3uSSf7WBso13wmUZtCmsgc69Gm5orV7kL4L5v98WY6YD+9/eWKQWOQvA3
VX9FErjb3WHzGV9cP/Z4xU7eCiw7ABWoeDxZCtyCttN37a15jfW+RpsD19UVYPUOtCpQMaJW5w6m
sJVnjWDIa9LJgl9yNRdtc4trtgLtsz04jc/75os2BhaI+8r9bs2uusDvQscgs9n18Bd/lM5RJ2x3
7Rx6wRwC697dOupTH9Kvg33QsAd7sVMBs/dfYlQDascBjRR3vnNcPAZuFBYDtgVG/zv1gGalTT/A
RZ4WYXalTSfVVVv1ezvnLz+gU71HgDH3cuDWfcHFbqRWVgUwAwSYgV4DWbxVTQ2AUihISCxEgPim
XpvFcksVebOUMDMAdpfXNiD1UbwmdU5Aer6xK4FBJNyVcN9FbCnAf1zHehA3UitQdj9DgCjIAAQo
NSgYfAylgVlzhsyHgA9ITQRISB70O+vGfHPION30VXcIhFYmggRFfCk4eOqkYW54VGUoNGfYAGkI
UHDIACKIVUGlfRUAWpHDUD2mh2NUVU0WgF1jAeUldgzHdU0ofzODYlN4f6WXcCmwdVr4df4nUmDn
esy2AgNIho04c7ZIhoqYUAVQAf9iGFW51DTfdIb/5DP0hYK7+Ds1UEUOVoxc1HiOaIlTEzxjGIjS
x2CcBXu3eIatlIjSqELMmIsV4IdSEwMN4ItwSInT2E+TKIfTKIMxJjVxBnZ/5nXBwmvF5l2m0woC
UDN4tl2p+F1bl4VaGGj/h4ReGHv69Iti2I1iWAFQ8zsSiI4UCZE9w2gKuWAVSYNTIzJM85AWCTy0
ZDYM+UpZw04lmZJkCDXSWDVn2IhVFofsuI0/KFMvKY4zx5AhOT8jeU4VqYC01ou++JCi5Y420AAo
iWT59lwMMFKdGGPlFT6tGAWm93miIQAptgQJV3opoADFRpBaGHZiGYtfKItDOXH/Z5mWaumLElMx
a7aWaekvcHmWZGhGGjNuRFmRDBAyFXOOKvmLfHmX6aeRZJiXhlmXYOYCFKCXjEmUlXOYvpgyjVmY
lFmRZxmYBeCXczmUmPkDm0mAbUkxngmXtoiZiomWMTaOLnCE5BV2rsh/o5h1VnkE/XhnsXAIBhCQ
hJWFYJl6K/B1rdmFXhiAaPmZxlmYxpmcyrmcFGmLYsgBluWNSQOZ1FmZQ2md2EmRj0mdhsmc3vmd
4JmcsDecB6mE5GWPXJeFxGaFGwWFUYgAtQmfp7hdVqiKA9mKr1ieX/iFG2CW4fmfABqgZ5lGdsUB
vjh5QuMCAhqe27mgDvqgy0mc/6kpiwgpdoAGaFrIa97lee65If3oCvUHAFRYn1pHbBPQm8d2ofp5
kLLYnxD6ojA6lO44jTGqnA1aozgKo2W5n66nn/2Hn6u4oVVoTPEJAFiZEqhIol25iifaimCXnyzK
o2bpojlapcs5khIpg1YKlze6pV76nTtKoSuaWL+pheqZj+05f9nzof0QbEuQmwG5pFiIoikKnPq5
ASuAp67Xn3xaAX36pcZJpQ+6AQXAUBcIqGppl4i6qGvpovzpizyKkLBIXq9ppnKUj/U5m/C5qUY6
hXBqACRqn7zZpBMAAa74mysKdni6Aayqp37qp60qqIxqpdBJMRwwA7I6q8qZq/+6+p99+qsUKqb6
2ZqVmnpnup6Z6p5G8KG1iZX1RwK5mZtK6pVY2KSmWqqnmqqrSpatCqux+q2x2qtqyavfSa7iGp7g
mq7qGq6Duq7f+qp8qqd5Oq+pWqzpealCOqRMIAAeyqlHiqTROn9KuopMSpDXCgGomqqqmqfu2rAO
+7AQ+67nOrFzGbEWe7EYu677ua0Ka6/HdqaYaoV41I8kSwQC8K8pEbAKAKoDW7CkaqqmugIIq7Dz
uqoZe7M4m7ELmrPs6qA8+7NA67AMy6r0Wq+oyn+8uYrImqkaUrIka5uCAK3QWoX1uaQEy5swW6oy
u7UKu61eG7Rg+7DeGrZkW7b/Znu2F1uzRduxv3mt96q0XRmqUrsETtusJxsYKsuyVmi1V2utEPC3
Wzuz+jkCC0u4GzACaJu4iru4jNu4Oau2eEqz//d1B/uxTXq1JKqm+7qpJOusKPsMAcuyeuuVV0uw
f4utf4uwqruihNu6eIq4K4C4jju7tFu7tpuxsJu7r0uvhKuwM5u1x2aqBDsB1Cq3cPqm8Nm5Jtup
ADu1o+uVpHu1EJCFMJu6gMu1sZu9rRu7I9C93vu94Hu74ju+5Au04Hu+3pun29u7vaufq4u6YFm6
0EuiAUsC/Jq8nHu3nxsLobuy01q602u91iuzgvt/64u+CJzACny4CtzADrwB/ywAwRIcwRQ8wRFb
wRhswRmcwePrwB78wSD8wdqbvSv6uwSctcKbtEsqt1JrAAjgwieLv526v1FrADbsv6FauqsYwAI8
wBgAAR6wAhgwwq0bwkZ8xEj8vSywxEyswU68wU6cxAgMxRksxVZ8xVhMxCT8u6qLuieawvKbrHOb
m/h7svrLvP9gw2qccKPLt6abAj2cugS8AkE8xHY8AhhAuHn8vXuMxX7cvUwcyII8yIRcyIZ8yIgs
yH+8yIzMyFpcwKtrvaV6ujq8wvUJqi2cBPxqxmY8w2jMv9F6wwk3AAn3Ai9AAzQgAiLQAi3wAA8A
x3Gsuqr7wxhQy3SMx7jcx//eewEXkMS8/MvADMKJnMg4UMzGbMzDnMwosMzLnMzDPAI4gAKK3MgO
zMvoC8zY3MvW3MBDjMexa8dCTMfiHMk9TL2VPL+XnMmbnLyc7MlpvMY3TMoKMACmfMqpvMqtzMOx
DMQIG8QQMAIekMcCncu4PALbbMQYkM2/XMsMzdDO/NAoEM0SHdHS/NCFzMwY3cyHDMLLTM1GfNDf
q9C/bNC9DL4DLdC2nNLg3M+Au88BXMlxm842LLWbzMmdjJU0DAhqfMMsS8qknAIDkAKofAA7TNQu
zc/+XMfh3NBMjQEf8AFNHdVR/dRS7dAWbdEafdWI/MuBzNVaPcgXUNGIXNX/ZF3WDU3VZI3WeOzU
UG3WDC3E4BzE/izL5VyqcCy/lozDoWu/9mvTN10VOw2qoOrT8wzUKXDKq3gA+JzPf+sDPpABGZC6
HgABJ2ACHmACmG3ZdlzLmW0CGGACbf3ZoV3LH+DZU20CLFDVpU3VpZ3abM3UT80CH3ABH8DEXi3I
Ya0DhIwCFyDIvL3E2EzIvAzWuA3MYM3Vww3cxs0C2IwBgnzWTw3VaO3UqL3ao03aoC3dpq3a243d
1D3d313aAC3ame3PmJ26JpC6kJ26PuDKD9ACYUy/K0vTfe3XZ5yyO+2/hB3UQR0CL5ACRH3PLXAA
EODeD+DYj/23HgDZJ9Dg/w7e0CZQ2Z293ZjN1BUe1ReO4ROe4RmuAzrw1B4e3TqQ0B/g4SZu4rx8
4iee4it+AR4OzCoe4iW+xE3NxE9N27Nd27Y927R92zlO27Id3dEd1Syw4Rxu5BCO5GSd4Zyt5J+d
2bV82Z1d2fzc4H97An+73nDs3qzcAiKwikEdqoLdwvxqAPbdyYAd2Po9z/ydAiEQAgAu1DRA4CnQ
5dZ74AoO2RngAXzO4Hz+4LUM6BjQ4ExN6E3t4Ih+Agwt6A2+3ZVt4RRuAh8u6TH+4T3+4yhe2yc+
2xjw4SVe6ZMO6ia+2qMO4p7+6ae+6ahe2h7+5Bru6BG+6IY+6IbO6LMu1f+3TuuKHui1fgJ8/ucN
/usODsTrDQGRDQGO/bcp8N5xrspBGtNs7L+hW9N+HaIAoOYG4NM+bdg5AOdEjdgErsqL3cqu3Ng+
MNnoDtl9vud8XsuQzdDv3tDxztR6Xu8ZAO/3Lu/3rgMR0OAq7u8mntmiLuRCXuoqbuqgfeKQXtZM
7uoOz9ClneQMDeVknesZsOsYMO/unu8an/H5XtUdH/Icf++/ru6TTezHnuyO/QAFzvLTy8oiQNTy
K8/RDq0zbcMCYOZnntOBgO37PQD8nQM5EOf+fQAEjsriPu5/68roDsSOzedP39COzdBTL/U+INVV
39RZv/ER4OGQreIX3/X/Hu7goq4DmA3qCX/iZ2/2lF7pAC/qbz/2pv3oEr/o3Z3oGK/v9P7xGXD1
Vl/LW48Bga/1fk/1hQ/45+4BT8/nxn7u/IzsPpC67l3grAwBdJ4CqozKNPDfPz3PVijYN8/XZ768
ac7T2c7mbA7UN5ADRH0Ab07gB4DKlh/LlY/uHsD0t/8Av87nuJ/7TO3KUg38US38hm/4Jx4BX2/i
el72EY72be/hza8DcR/jyX/iGaD812/i/X4CY8/9J/722w/qyz/ixf/3tUz85/8A6f/76k/W6I8B
vc/7up/7u4/nTV/uf2vnXW7UrQ8EKeHrFUopBgqkwmBgNqFNwZRaBVyx/9lstJkcfL+p7+2WOqRy
ocM6RIQcIA4aLQ4RiSAevafV0vf9/vowCAEJMQwPFQcVDx8eI3R0Hh8kJx8tH30sfTYzMixDJTNO
RC1PUE9JR0FNLTN8MiIlO2V1YFtvP1lzP3N1X30OO4UbKR0fkRsZExFbHhqjkxWT9zwe9bDzIB76
IPIAvyH68Ozwzg7mzFJC2gfElpieoEgE6quoEAAEtPqxuLogAROGzLocOdawaUNkDh0HEGjg0ZPn
zp47gABZw4gxWqEWhyKEFLkRkMgIGzFJSvmgkytgLn3FlBQBlstMlHBWUkmMWCiePEX19JFTZ6iQ
JBk5W/bRI8mOGPb0sf/GJ1DUQFI1Yrwj7ts5iG/QEWnXLsc7L0ucAJSCzwo/f1rUDpRLBh3dhG/G
hnhTZ46HPH77WrwjwkNFa4NFYLjz9I5JxxEQQxbheOPIPiIpzfK5yebPUClnPo6UU7NKnKZOg870
uaToo4Mli2xscjYhxIoTP7VN+DBvwXoM+wWOuA7fvTTgoDNDNocYeGfTRrlngO2Ufdff/uMywIBc
MM7RJRRfB85D83nMT1W/noa1hlNdx5c/n/5jm/Xx59e/nz/99f8BDHCPv+o4j7xvxFtHOSHAWIK7
eaIQgLrqrnMruysA4s47sw4YIDzx7iqvwDj8ckDA9YhIMcU9+mtRNJv/RHFRxhlprFGkE3FUL70R
HyovuQQXNOsLgZBoAkIpJmSrwgu1i0JDucR4p0MzQAxRxPTSy3GqvELQI4EvbQyzNBgtEdPMM2XU
EseHPDjPzb1+BNI5IYl8UC0Jq6MCOyYz7G5DMc7wsMofeXTA0EPbTFTNPb5s1NFG0YxU0klrfNTS
SxtddD0Td3wzThAVNCvKBrmLLsIkleTHwuz63PCLKQcd7wA3DY2D00RNVBNTRyl9TIWQYuxV2GEj
2BVTTfW49dBlC1wDrCoVHFWu7o48NU9VmcRwO1fB6DBWEB2YdVZbDcVVU2PRBTMCFdht18Z2VdAh
3vp+JdZe19LNN1M1/5Vt0zxPPwXSQyGnLfVOVPFZks8MuX1V0G/FDXfZicvtN1f19N0V3o057rje
+eQN+eN7h+0445PRBdBicylu9tlBzRhY2oHUivBahS+Mq2FvH45V4lkpnpjl/1B+1OOjkebYsXiZ
DpnGpDsWE2qoiy5aZZaDPjRiiNcANMqZNawZ4VT3ZLXVDTsUtOcqf8562aHXqzqBqemum12R6bVb
7735rlvulP+z2O22uUZnYG7FvlZPbBfezk/v0l5j7W/bztrcuKvuu+51RRYZXnnX1Vz00Uk/+u9L
A8fa7a25dhhxg61VHGezowABhMcH0ED3wyUvPCGJB0fU4tMv5Tv0X/9hgEHedmHIofmm2+0c+uNL
r97j5E0mPuMSuC/B0aGD5p7ircNdg/tBB+6gg4YTVxzbVd8CyPYnQdjdYW99Jz/4is3V3tHSsce8
5ClvY8s7mvQ8Z73Scc9j/ktXDyDYg0etjGIQHF/5QARBEKltAOp73cHcN7v4cQEEPNCQ7UCANvxx
rXL7G54Dq8dAASYtgQq04dFkaDoHXgqCqBPcxCy4LNaJR33iUVuHPOgqsY2NbPDzh/xSaAAUekd3
ulvhGqqoAfE4QH1cVF8HBtfFRCVAfY76YhkbhcY0dmBuZ+wAu9y4sQj2YGM5VIEdOTbAALarezns
Y/fYhUc8wquPdyz/AR8PWcg6lgCCKmjk0dz4qEia8YtfOqMk2UjJL97KjV7cpKHOeIAirqGIoRzY
AeonlyzWDE8hZFzOSGjCKQ4EhSi0ooeymMU1OCCXuuti0MTIKTW6cZiZXGMbvwhHYipzmex6pDMP
6bE/+nGazpwjHa0pR2xy7JoRbFc3n+nIa6oPksRc4yQtScxLHvOcZ/TXGUEJT0+6MSG9rOLA7Jc7
DdTSdgBppexeSbsm8ICgPJgfLQ/6hX16yHZarKdDD1BFoPFSd0GraMU6oIEvVbFRHE2A7h4FUhXo
Dl4kVaYKktkucp7Umt7U5ja96VJxbpOlKH0jvFa6sZTaFKbPTOlO/3eq05xy1KMfBalRO3pUpBqV
qBVtU0Y1YKiLHmqqVSyfRLFoRcndU59fmGJ3pHg7LvzzZgEdIRQKmlaE8tN2PEAlW1GY1d9JNaoU
mypdHfBRECQgrxvV6FKTOjeTsquKG8tlHG2q0jNyk6Y4valiHRtZyQqVsjVlaU4tW1INbCywjjqq
UpVq1Lxmca93pShel3XRiEJUrlgEgeQGdlDZwrWfsXNltgAAEIJ2p6BgMChtc0fb1751iw6wXdCO
m1qNUpSvzf3sXzs7WMLmcqT2NKkGHpvYjmF2spbNbnUNu1mOcTen5L0pd6WrWc76NaR/BS10kZrX
+jW3fhO7qGkr2v/ahNhuv6/lnUG9msIBCFesUCBrnkT4RC7slrcm/AJB0TZg/8aKv1tM7sQubKjj
JmDDfbXdlz7sqBDb7mi2FK/HpJteyG73u4NN74tPrF4Zg1fGMEYxCOAl4r3qGMQ75rCPOcwD+oIg
r8Yl8rKSm2Ej9xdEJWSy62brVROClZVMTJhZz4pWHnShtwPo8oNNeICC4q/Cbx3uGpR8KBSqOckf
zutve+xjFPYYXiRmF1vrfOIUx1izehZvYaf7Zz5X18+DJnS7AE1jRAvazzjuGArZ9eM4N2rOku6x
owzaXIOy+chGPrKSyxxXNFc4uClM2ywP2lstj9XKbSlbdiQUBQb/N9jBaVVrh2w95jXkesxZoy2n
a6ljflLa0XfGswpoW+f6Tfdo1g10Fhe9TzsjG64eM3GibWzsYz8arnEO9qVBLGT6Clm+nfZ0Ldks
RDOPmq3e4jWEfQvhd7Pafe/DbaxX3QUDfFmt3ZIyQUEE8LQWl2JpdQBBl2Xr5jZK4QwXN7wKWmxt
S7xddp52x6hb0lpWfNvUJvHFN7bxaYP84iKneI7bStBHNfxLKm85ufmqckMhPOEGPxTNAy6egQPc
QxAuIbzlAmFab5ne9U6wP/Bdsyc1zN9HTAjAITYxHtR86hNrbpFRZj2Q37Diyj451xu4w6uPfeZV
d6Gh8pcQDqaN/+lghZ0/W724V8N6iW7H3c5etUKos/DgvHYb2bNOuq1zPdlg16HYAV/km5t9f2nv
XeSYTrO3w73e9r43deq+9Mjzzt1uzV/ZCxo8wAdec4MHu60Nv17ENwrrrZc641fn+CO6ru1hW+KB
KYRluic9Lm7fPOQf7/izL2v0pE/98fu2+ny1/urDn5jj1Q5btm+eyrePu9ydCGs8Zd73v7/fFT/v
fOb3tWjIN3+OlV+18Tdf/GiH/uwPR33bJ+761tG99rfPfc0zHfjg9137i6/8zk+B0k971k/x2g/6
og/y4q/2qq/KcK+JcAsLpgDzeK/39o//vm9yCgcAme90BtBuCv9Q7A6Qr9rP/WSvd3hn877A7urO
Ao3u/vAv//Tv7iKv/ziQ75wv8bTH/EbwB3nQ9U5QAfFnBVmwBeeP/iJQAifwCqrAAl/Q7o7QdYqQ
CD1w7IAwC7Vw+YKQ/YZQAeFv+uTvAa2v8iyvCfcBHzAvCqVwCoHP6dLu9RaPYjQN5sjPWFyuaPIw
Dy+FD7dQbkoQAcWP5jAo7cJwCsHABetu+ypvSbLvQtgCCtkwbBBxBYMvDstuDoMmAWQOC3fFDzNm
D8UNU0DxD3clEBPvBMsODFWQAadQEV9wCXNv7u6tOtZwEtvwCN/wEjuQEAkxa7rQUkoxX4axD0cx
C1ExGb1QFRf/LwV5xgiPEBYXEQZj8OiY5FokERcz0PtOyf++xdb6ru9+cRzTavRUrhxXDh1fzuHS
8RyPkRMLCh7ZEdOmDvAUDuvKkfnKsRPF8Rf7kfEQzuaezvNapxVp7xWTMAplcRYfMVsUJxujkBJt
8AbvBw5jBRzfTRP/kR/rMNfokeVE8SNZDh498s3sUB71sSTf7eoyEvRsbiPN7t10jiBj5RArUSLZ
EEkW8sqs0SHdByIjsvsQEQe5Zu9CD/QyMSnD8VA6siNNEuZCDyWlMh6fsimr0iTHjiOx0iTFseYW
LyZ9ESyRcixDb9eMkiaNyCAbkAWlMCcNrP54siFr8SdpMCcl/7ISd9Ebz3KXkjIsYa/g6rHIZI4j
BxMqDTMrDxMfE1Mjqe71WtIf/RIw5bDvAo4g924BobESpVEhqdEMHRENtcAMGdEtoYASb5IoK3Mg
K1MpNzJoILPqXlMpw3Iyl1IjY9M1MfLdYBP2yNHmXtMsUxM4MdMVEXIzY7EzRbMnJ1A0K7Au7TIX
dbEig1PM0BLq/PErJdMra7MvxZI1a/M2tzM8cfMoswY8HTMcZ1I4VRM4bfImjfM4dxLBzhA0KZA5
R/MCX/Au8XIDqXM91xPqvvM6b5M8j3I2x7IrD5RAIzM7W9M2FzRA3UrXqNPzLrM/h/MgoxEnSZMR
7RP76PMtOv+0OW+RNPVzKL9vzCrUOi0z13CTNv0OO3sTHL9SRl3yJanON1+0Ro9yQgfOLG3NP9mT
OjMzQ8kwJ++zQz/zQ/tBVUL0PkmzNIWSBRkQlXquOinUSi9TOxmTRufwNQOSN0PPS6fuOmfUMRlv
IAUOS9WUJveuSiUHwsSQLTV0Q5GTOZNUSZc0DZt0NJ9U30zTDaXTG4kQXJixUMtTayR0UBX1/dQy
TuX0PaeRQ5v0TvE0NCtkT520T6EzOk/JIhf1U0G1SmQyVEm1SpyOCt1zTuk0PqtRBvHU3jBVRJ3z
Of+UUyOnCks1Vwf1R3V1UU/1GYmTSBPSSKEwVmG1UmHtM43/NVM1tVZtlT8FtVeldVqJ8Fd5Zkpv
EgkhNVLrdFLnE1lB1BGXVVY11U+jVEpRFVdzkFrZVVetdfawdS0RsS379EiNVVnB1SHxdVyLtVw3
FVCNUF0fb13blRUF9mDfdWDjNVizlV6f1F7v9VjztQmPdVypAChJ9F9NNGChNWERVmE/NmQ9dmQX
FlU5Nls3xGFXtVu9FV8nFjQrVk+XtV+ftERRVi5K9mQXVmB11mRz9md9Nmjl9WZTVlWJVVIj1mVf
Vklj1mLJFT/zU2OJdiCAtmettmqxFkOndmvvslwhNlb3lRaXFg2bVmZnlk9rVmq5dm3Ztm3dtmBU
dmVZ1U5jyXZsl7ZpnZZZM9Zm37Zv/fZv2adrvbZYLTZs5dJuK7Vs85Zm+7RrAfdxIZdr23JYH5Zl
MTVsETdz87RiF3dW09ZxIzd0RVdbHddfrcVyQ9RwNXd1kc5wLZZxy7V0nXV0aTfyJvd2KVdTv/Zy
y5Z1fRcS97VzR9R0cbd4a7c4Zdd4lXfyiPctkRZse/d3pfcaXfdsMbZ5lzd7k3d7tbd7uTd3sfd0
59Yz63Z6zXc5q9dYYTd8xeZ7vfd9k5d95ZfyUNc+Vfd8KzUIAAA7
------=_NextPart_94915C5ABAF209EF376268C8--

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



From seamoby-admin@ietf.org  Thu Dec 12 13:44:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06552
	for <seamoby-archive@lists.ietf.org>; Thu, 12 Dec 2002 13:44:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCIbQv07061;
	Thu, 12 Dec 2002 13:37:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCIa3v06398
	for <seamoby@optimus.ietf.org>; Thu, 12 Dec 2002 13:36:03 -0500
Received: from bsn-mail-01.bstormnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06058
	for <seamoby@ietf.org>; Thu, 12 Dec 2002 13:33:03 -0500 (EST)
From: Pat Calhoun <pcalhoun@bstormnetworks.com>
To: seamoby@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1039687118.1845.19.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 12 Dec 2002 01:58:38 -0800
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Goodbye SPAM
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Although I could swear it was setup properly (you should see the number
of e-mails I need to reject on a daily basis), it wasn't. I just updated
the mailing list's configuration to no longer allow spam.

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


From mailnull@www1.ietf.org  Thu Dec 12 13:45:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06581
	for <seamoby-archive@odin.ietf.org>; Thu, 12 Dec 2002 13:45:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCIll807530
	for seamoby-archive@odin.ietf.org; Thu, 12 Dec 2002 13:47:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCIllv07527
	for <seamoby-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 13:47:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06566
	for <seamoby-web-archive@ietf.org>; Thu, 12 Dec 2002 13:44:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCIbQv07061;
	Thu, 12 Dec 2002 13:37:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCIa3v06398
	for <seamoby@optimus.ietf.org>; Thu, 12 Dec 2002 13:36:03 -0500
Received: from bsn-mail-01.bstormnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06058
	for <seamoby@ietf.org>; Thu, 12 Dec 2002 13:33:03 -0500 (EST)
From: Pat Calhoun <pcalhoun@bstormnetworks.com>
To: seamoby@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1039687118.1845.19.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 12 Dec 2002 01:58:38 -0800
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Goodbye SPAM
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Although I could swear it was setup properly (you should see the number
of e-mails I need to reject on a daily basis), it wasn't. I just updated
the mailing list's configuration to no longer allow spam.

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



From seamoby-admin@ietf.org  Fri Dec 20 11:40:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01249
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 11:40:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKGgmv25768;
	Fri, 20 Dec 2002 11:42:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKGaAv24898
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 11:36:10 -0500
Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01034
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 11:32:41 -0500 (EST)
Received: from mothost.mot.com (mothost.mot.com [129.188.137.101])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id gBKGZidv013285
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 09:35:44 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id JAA18179 for <Seamoby@ietf.org>; Fri, 20 Dec 2002 09:35:43 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6MAT5H>; Fri, 20 Dec 2002 10:35:43 -0600
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: Seamoby@ietf.org
Date: Fri, 20 Dec 2002 10:35:43 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] CARD - FMIPv6 protocol interworking
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hello All,

The CARD design team would like to solicit WG consensus about CARD 
and FMIPv6 protocol inter-working.  The selection of anyone method 
from the proposed list would help us to focus in the right direction 
during the next phase of the protocol design. The high-level description
of the various approaches with their relative merits and de-merits is 
listed below:
 
Tight Coupling Approach 
Intermediate Approach
Loose Coupling Approach 

Tight Coupling Approach: In this case, we can define CARD signaling as 
an extension to the FMIPv6 messages. This makes the CARD protocol tightly
coupled with FMIv6 protocol. 

The following are the PROS and CONS of this approach:

PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
CARD and FMIPv6 implementation less complicated. 

CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
This approach may also require modification to the present FMIPv6 protocol. 

Intermediate Approach: In this approach, we can define CARD signaling as 
generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
message including FMIPv6 signaling messages. Additionally, we can also define 
new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
pending. 

The following are the PROS and CONS of this approach:

PROS: This approach enables the deployment of CARD along with any protocol 
including FMIPv6.  This also provides opportunity for additional optimization 
when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
signaling over the FMIPv6 messages. 
 
CONS: The CARD protocol will be slightly more complex compared to the other 
approaches.

Loose Coupling Approach: We can define CARD signaling as new set of messages 
and prohibit the possibility of piggybacking upon any FMIPv6 messages. 

The following are the PROS and CONS of this approach:

PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
is simpler to implement. 
 
CONS: Adds extra over the air messages during critical path of handoff which 
may not be desirable for the most wireless link. 

Please send your choice if any.

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


From mailnull@www1.ietf.org  Fri Dec 20 11:40:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01276
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 11:40:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKGhqe25824
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 11:43:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKGhqv25821
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 11:43:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01252
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 11:40:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKGgmv25768;
	Fri, 20 Dec 2002 11:42:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKGaAv24898
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 11:36:10 -0500
Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01034
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 11:32:41 -0500 (EST)
Received: from mothost.mot.com (mothost.mot.com [129.188.137.101])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id gBKGZidv013285
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 09:35:44 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id JAA18179 for <Seamoby@ietf.org>; Fri, 20 Dec 2002 09:35:43 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2656.59)
	id <WD6MAT5H>; Fri, 20 Dec 2002 10:35:43 -0600
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: Seamoby@ietf.org
Date: Fri, 20 Dec 2002 10:35:43 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Seamoby] CARD - FMIPv6 protocol interworking
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hello All,

The CARD design team would like to solicit WG consensus about CARD 
and FMIPv6 protocol inter-working.  The selection of anyone method 
from the proposed list would help us to focus in the right direction 
during the next phase of the protocol design. The high-level description
of the various approaches with their relative merits and de-merits is 
listed below:
 
Tight Coupling Approach 
Intermediate Approach
Loose Coupling Approach 

Tight Coupling Approach: In this case, we can define CARD signaling as 
an extension to the FMIPv6 messages. This makes the CARD protocol tightly
coupled with FMIv6 protocol. 

The following are the PROS and CONS of this approach:

PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
CARD and FMIPv6 implementation less complicated. 

CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
This approach may also require modification to the present FMIPv6 protocol. 

Intermediate Approach: In this approach, we can define CARD signaling as 
generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
message including FMIPv6 signaling messages. Additionally, we can also define 
new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
pending. 

The following are the PROS and CONS of this approach:

PROS: This approach enables the deployment of CARD along with any protocol 
including FMIPv6.  This also provides opportunity for additional optimization 
when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
signaling over the FMIPv6 messages. 
 
CONS: The CARD protocol will be slightly more complex compared to the other 
approaches.

Loose Coupling Approach: We can define CARD signaling as new set of messages 
and prohibit the possibility of piggybacking upon any FMIPv6 messages. 

The following are the PROS and CONS of this approach:

PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
is simpler to implement. 
 
CONS: Adds extra over the air messages during critical path of handoff which 
may not be desirable for the most wireless link. 

Please send your choice if any.

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



From seamoby-admin@ietf.org  Fri Dec 20 12:40:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02966
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 12:40:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKHhFv29598;
	Fri, 20 Dec 2002 12:43:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKHgEv29563
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 12:42:14 -0500
Received: from fridge.docomolabs-usa.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02945
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 12:38:44 -0500 (EST)
Message-ID: <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>, <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 09:40:04 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>

I favor this approach, for router to mobile communication, at least.

> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6 protocol.
>

I don't see why this should restrict CARD To FMIPv6. FMIPv6 defines some
additional ICMP messages. If the CARD messages are extensions too, the
difference between the loose approach and tight approach isn't so great in my
view. The new ICMP messages can be used with or without handover. Those designed
to be used with handover are FMIPv6, those designed to be used without are CARD.

There has been a discussion in the MIP group about whether the FMIPv6
prehandover signaling should be completely decoupled from handover, but the
discussion has not reached any clear conclusion. One issue is whether decoupling
the signaling would also decouple any signaling between the mobile's current
access router and other access routers (i.e. HI/HAck). If no signaling occurs
between access routers when the FMIPv6 signaling occurs (that is, it is for
information only), then that would be the equivalent of CARD. If signaling does
occur, perhaps to pre-configure a care of address on the new subnet, then it
would be different.

I think a more pressing issue for CARD is whether the same protocol can be used
to exchange CARD information between routers. The current FMIPv6 approach isn't
defined for this, and there are some good arguments why this should be done
using a reliable transport, such as SCTP or TCP, rather than UDP, which came up
during the CT discussion.

> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the other
> approaches.
>

I am opposed to this. It seems the least clean of all the approaches, both
architecturally and implementationally.

> Loose Coupling Approach: We can define CARD signaling as new set of messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement.
>

I'm not sure I follow why. While implementing the protocol might be easier,
since FMIPv6 will be the principle consumer, it might be more complicated to
integrate the two.

> CONS: Adds extra over the air messages during critical path of handoff which
> may not be desirable for the most wireless link.
>

Again, why would this be so? The CARD information can be exchanged between the
AR and MN at any time prior to the handover.

BTW, I think that the Loose Coupling approach might be appropriate for the
inter-router exchange protocol, presuming we want to tackle that. However, I
believe we would need to look at alternatives, such as including CARD
information in the IGP (though that might be messy, given the IETF has three
"standard" IGPs).

            jak


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


From mailnull@www1.ietf.org  Fri Dec 20 12:41:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02996
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 12:41:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKHiKB29628
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 12:44:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKHiJv29625
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 12:44:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02982
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 12:40:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKHhFv29598;
	Fri, 20 Dec 2002 12:43:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKHgEv29563
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 12:42:14 -0500
Received: from fridge.docomolabs-usa.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02945
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 12:38:44 -0500 (EST)
Message-ID: <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>, <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 09:40:04 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>

I favor this approach, for router to mobile communication, at least.

> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6 protocol.
>

I don't see why this should restrict CARD To FMIPv6. FMIPv6 defines some
additional ICMP messages. If the CARD messages are extensions too, the
difference between the loose approach and tight approach isn't so great in my
view. The new ICMP messages can be used with or without handover. Those designed
to be used with handover are FMIPv6, those designed to be used without are CARD.

There has been a discussion in the MIP group about whether the FMIPv6
prehandover signaling should be completely decoupled from handover, but the
discussion has not reached any clear conclusion. One issue is whether decoupling
the signaling would also decouple any signaling between the mobile's current
access router and other access routers (i.e. HI/HAck). If no signaling occurs
between access routers when the FMIPv6 signaling occurs (that is, it is for
information only), then that would be the equivalent of CARD. If signaling does
occur, perhaps to pre-configure a care of address on the new subnet, then it
would be different.

I think a more pressing issue for CARD is whether the same protocol can be used
to exchange CARD information between routers. The current FMIPv6 approach isn't
defined for this, and there are some good arguments why this should be done
using a reliable transport, such as SCTP or TCP, rather than UDP, which came up
during the CT discussion.

> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the other
> approaches.
>

I am opposed to this. It seems the least clean of all the approaches, both
architecturally and implementationally.

> Loose Coupling Approach: We can define CARD signaling as new set of messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement.
>

I'm not sure I follow why. While implementing the protocol might be easier,
since FMIPv6 will be the principle consumer, it might be more complicated to
integrate the two.

> CONS: Adds extra over the air messages during critical path of handoff which
> may not be desirable for the most wireless link.
>

Again, why would this be so? The CARD information can be exchanged between the
AR and MN at any time prior to the handover.

BTW, I think that the Loose Coupling approach might be appropriate for the
inter-router exchange protocol, presuming we want to tackle that. However, I
believe we would need to look at alternatives, such as including CARD
information in the IGP (though that might be messy, given the IETF has three
"standard" IGPs).

            jak


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



From seamoby-admin@ietf.org  Fri Dec 20 15:01:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08690
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 15:01:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKK4Qv05106;
	Fri, 20 Dec 2002 15:04:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKK3hv05091
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 15:03:43 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08622
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 15:00:13 -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 MAA02609;
	Fri, 20 Dec 2002 12:03:10 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBKK39Y00857;
	Fri, 20 Dec 2002 12:03:09 -0800
X-mProtect: <200212202003> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdQsaA06; Fri, 20 Dec 2002 12:03:07 PST
Message-ID: <3E03777C.F4E1F6B7@iprg.nokia.com>
Date: Fri, 20 Dec 2002 12:03:08 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
CC: Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Ajoy,

for MN - AR signaling, it would be good to have ICMP options.
So, I guess that means "Intermediate Approach" without
necessarily endorsing all the associated PROS and CONS.

Regards,

-Rajeev


Singh Ajoy-ASINGH1 wrote:

> Hello All,
>
> The CARD design team would like to solicit WG consensus about CARD
> and FMIPv6 protocol inter-working.  The selection of anyone method
> from the proposed list would help us to focus in the right direction
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is
> listed below:
>
> Tight Coupling Approach
> Intermediate Approach
> Loose Coupling Approach
>
> Tight Coupling Approach: In this case, we can define CARD signaling as
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol.
>
> The following are the PROS and CONS of this approach:
>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6 protocol.
>
> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the other
> approaches.
>
> Loose Coupling Approach: We can define CARD signaling as new set of messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement.
>
> CONS: Adds extra over the air messages during critical path of handoff which
> may not be desirable for the most wireless link.
>
> Please send your choice if any.
>
> Regards,
> Ajoy
> _______________________________________________
> 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 mailnull@www1.ietf.org  Fri Dec 20 15:02:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08709
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 15:02:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKK5NG05140
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 15:05:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKK5Nv05137
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 15:05:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08703
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 15:01:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKK4Qv05106;
	Fri, 20 Dec 2002 15:04:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKK3hv05091
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 15:03:43 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08622
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 15:00:13 -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 MAA02609;
	Fri, 20 Dec 2002 12:03:10 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBKK39Y00857;
	Fri, 20 Dec 2002 12:03:09 -0800
X-mProtect: <200212202003> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdQsaA06; Fri, 20 Dec 2002 12:03:07 PST
Message-ID: <3E03777C.F4E1F6B7@iprg.nokia.com>
Date: Fri, 20 Dec 2002 12:03:08 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
CC: Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Ajoy,

for MN - AR signaling, it would be good to have ICMP options.
So, I guess that means "Intermediate Approach" without
necessarily endorsing all the associated PROS and CONS.

Regards,

-Rajeev


Singh Ajoy-ASINGH1 wrote:

> Hello All,
>
> The CARD design team would like to solicit WG consensus about CARD
> and FMIPv6 protocol inter-working.  The selection of anyone method
> from the proposed list would help us to focus in the right direction
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is
> listed below:
>
> Tight Coupling Approach
> Intermediate Approach
> Loose Coupling Approach
>
> Tight Coupling Approach: In this case, we can define CARD signaling as
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol.
>
> The following are the PROS and CONS of this approach:
>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6 protocol.
>
> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the other
> approaches.
>
> Loose Coupling Approach: We can define CARD signaling as new set of messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement.
>
> CONS: Adds extra over the air messages during critical path of handoff which
> may not be desirable for the most wireless link.
>
> Please send your choice if any.
>
> Regards,
> Ajoy
> _______________________________________________
> 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 20 15:11:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08916
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 15:11:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKE3v06091;
	Fri, 20 Dec 2002 15:14:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKDhv06077
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 15:13:43 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08906
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 15:10:13 -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 MAA03413;
	Fri, 20 Dec 2002 12:13:15 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBKKDDa09566;
	Fri, 20 Dec 2002 12:13:13 -0800
X-mProtect: <200212202013> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdXOrIfR; Fri, 20 Dec 2002 12:13:11 PST
Message-ID: <3E0379D8.C3AF38AC@iprg.nokia.com>
Date: Fri, 20 Dec 2002 12:13:12 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com> <00f301c2a84e$d4dbb840$506015ac@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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hello Jim,

James Kempf wrote:

>
> There has been a discussion in the MIP group about whether the FMIPv6
> prehandover signaling should be completely decoupled from handover, but the
> discussion has not reached any clear conclusion. One issue is whether decoupling
>

On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"

prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
didn't hear any objections. I am willing to say that this is recommended in the
spec,
while the MN MAY also do it during handover if it so wishes (please see the ATL
slides).

> the signaling would also decouple any signaling between the mobile's current
> access router and other access routers (i.e. HI/HAck). If no signaling occurs
> between access routers when the FMIPv6 signaling occurs (that is, it is for
> information only), then that would be the equivalent of CARD. If signaling does
> occur, perhaps to pre-configure a care of address on the new subnet, then it
> would be different.

The implication is that HI/HAck would take place upon receiving FBU. It probably
does not make sense to create and manage handover state without knowledge of
when exactly the MN is undergoing handover (again, see the ATL slides).

Regards,

-Rajeev



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


From mailnull@www1.ietf.org  Fri Dec 20 15:11:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08953
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 15:11:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKKEvY06141
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 15:14:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKEvv06138
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 15:14:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08930
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 15:11:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKE3v06091;
	Fri, 20 Dec 2002 15:14:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKDhv06077
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 15:13:43 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08906
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 15:10:13 -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 MAA03413;
	Fri, 20 Dec 2002 12:13:15 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBKKDDa09566;
	Fri, 20 Dec 2002 12:13:13 -0800
X-mProtect: <200212202013> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdXOrIfR; Fri, 20 Dec 2002 12:13:11 PST
Message-ID: <3E0379D8.C3AF38AC@iprg.nokia.com>
Date: Fri, 20 Dec 2002 12:13:12 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com> <00f301c2a84e$d4dbb840$506015ac@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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hello Jim,

James Kempf wrote:

>
> There has been a discussion in the MIP group about whether the FMIPv6
> prehandover signaling should be completely decoupled from handover, but the
> discussion has not reached any clear conclusion. One issue is whether decoupling
>

On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"

prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
didn't hear any objections. I am willing to say that this is recommended in the
spec,
while the MN MAY also do it during handover if it so wishes (please see the ATL
slides).

> the signaling would also decouple any signaling between the mobile's current
> access router and other access routers (i.e. HI/HAck). If no signaling occurs
> between access routers when the FMIPv6 signaling occurs (that is, it is for
> information only), then that would be the equivalent of CARD. If signaling does
> occur, perhaps to pre-configure a care of address on the new subnet, then it
> would be different.

The implication is that HI/HAck would take place upon receiving FBU. It probably
does not make sense to create and manage handover state without knowledge of
when exactly the MN is undergoing handover (again, see the ATL slides).

Regards,

-Rajeev



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



From seamoby-admin@ietf.org  Fri Dec 20 16:19:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11238
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 16:19:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLLRv09783;
	Fri, 20 Dec 2002 16:21:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLKWv09751
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 16:20:32 -0500
Received: from bsn-mail-01.bstormnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11205
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:17:02 -0500 (EST)
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
From: Pat Calhoun <pcalhoun@bstormnetworks.com>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: James Kempf <kempf@docomolabs-usa.com>,
        Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
In-Reply-To: <3E0379D8.C3AF38AC@iprg.nokia.com>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
	 <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
	 <3E0379D8.C3AF38AC@iprg.nokia.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1040419193.3346.14.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 20 Dec 2002 13:19:53 -0800
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"
> 
> prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> didn't hear any objections. I am willing to say that this is recommended in the
> spec,
> while the MN MAY also do it during handover if it so wishes (please see the ATL
> slides).

Nothing is agreed upon in meetings - we can just gage consensus. We have
to get agreement on the mailing list to get closure.

PatC

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


From mailnull@www1.ietf.org  Fri Dec 20 16:19:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11262
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 16:19:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKLMnE09819
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 16:22:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLMnv09816
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 16:22:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11253
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 16:19:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLLRv09783;
	Fri, 20 Dec 2002 16:21:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLKWv09751
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 16:20:32 -0500
Received: from bsn-mail-01.bstormnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11205
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:17:02 -0500 (EST)
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
From: Pat Calhoun <pcalhoun@bstormnetworks.com>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: James Kempf <kempf@docomolabs-usa.com>,
        Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
In-Reply-To: <3E0379D8.C3AF38AC@iprg.nokia.com>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
	 <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
	 <3E0379D8.C3AF38AC@iprg.nokia.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1040419193.3346.14.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 20 Dec 2002 13:19:53 -0800
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"
> 
> prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> didn't hear any objections. I am willing to say that this is recommended in the
> spec,
> while the MN MAY also do it during handover if it so wishes (please see the ATL
> slides).

Nothing is agreed upon in meetings - we can just gage consensus. We have
to get agreement on the mailing list to get closure.

PatC

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



From seamoby-admin@ietf.org  Fri Dec 20 16:33:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11713
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 16:33:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLa8v10318;
	Fri, 20 Dec 2002 16:36:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLZhv10243
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 16:35:43 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11637
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:32:12 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 20 Dec 2002 13:35:13 -0800
Received: from 138.15.98.100 by by1fd.bay1.hotmail.msn.com with HTTP;
	Fri, 20 Dec 2002 21:35:13 GMT
X-Originating-IP: [138.15.98.100]
From: "Eunsoo Shim" <eunsooshim@hotmail.com>
To: rajeev@iprg.nokia.com, ASINGH1@motorola.com
Cc: Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 16:35:13 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY1-F34oJjMJvCzxeB000198dc@hotmail.com>
X-OriginalArrivalTime: 20 Dec 2002 21:35:13.0538 (UTC) FILETIME=[AE171620:01C2A86F]
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hi,

I also support for the Intermediate Approach.
Thanks.

Eunsoo

>From: Rajeev Koodli <rajeev@iprg.nokia.com>
>To: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
>CC: Seamoby@ietf.org
>Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
>Date: Fri, 20 Dec 2002 12:03:08 -0800
>
>
>Ajoy,
>
>for MN - AR signaling, it would be good to have ICMP options.
>So, I guess that means "Intermediate Approach" without
>necessarily endorsing all the associated PROS and CONS.
>
>Regards,
>
>-Rajeev
>
>
>Singh Ajoy-ASINGH1 wrote:
>
> > Hello All,
> >
> > The CARD design team would like to solicit WG consensus about CARD
> > and FMIPv6 protocol inter-working.  The selection of anyone method
> > from the proposed list would help us to focus in the right direction
> > during the next phase of the protocol design. The high-level description
> > of the various approaches with their relative merits and de-merits is
> > listed below:
> >
> > Tight Coupling Approach
> > Intermediate Approach
> > Loose Coupling Approach
> >
> > Tight Coupling Approach: In this case, we can define CARD signaling as
> > an extension to the FMIPv6 messages. This makes the CARD protocol 
>tightly
> > coupled with FMIv6 protocol.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> > CARD and FMIPv6 implementation less complicated.
> >
> > CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> > This approach may also require modification to the present FMIPv6 
>protocol.
> >
> > Intermediate Approach: In this approach, we can define CARD signaling as
> > generic ICMP options. These ICMP options can be piggybacked upon any 
>ICMP
> > message including FMIPv6 signaling messages. Additionally, we can also 
>define
> > new CARD ICMP messages, which can be used when no outgoing ICMP messages 
>are
> > pending.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS: This approach enables the deployment of CARD along with any 
>protocol
> > including FMIPv6.  This also provides opportunity for additional 
>optimization
> > when deployed with FMIPv6 by exploiting the possibility of piggybacking 
>CARD
> > signaling over the FMIPv6 messages.
> >
> > CONS: The CARD protocol will be slightly more complex compared to the 
>other
> > approaches.
> >
> > Loose Coupling Approach: We can define CARD signaling as new set of 
>messages
> > and prohibit the possibility of piggybacking upon any FMIPv6 messages.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS:De-couples CARD from any other protocol including FMIPv6. Probably 
>this
> > is simpler to implement.
> >
> > CONS: Adds extra over the air messages during critical path of handoff 
>which
> > may not be desirable for the most wireless link.
> >
> > Please send your choice if any.
> >
> > Regards,
> > Ajoy
> > _______________________________________________
> > 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/seamob

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail&xAPID=42&PS=47575&PI=7324&DI=7474&SU= 
http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_addphotos_3mf

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


From mailnull@www1.ietf.org  Fri Dec 20 16:34:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11736
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 16:34:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKLbAS10794
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 16:37:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLbAv10787
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 16:37:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11727
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 16:33:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLa8v10318;
	Fri, 20 Dec 2002 16:36:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKLZhv10243
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 16:35:43 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11637
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:32:12 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 20 Dec 2002 13:35:13 -0800
Received: from 138.15.98.100 by by1fd.bay1.hotmail.msn.com with HTTP;
	Fri, 20 Dec 2002 21:35:13 GMT
X-Originating-IP: [138.15.98.100]
From: "Eunsoo Shim" <eunsooshim@hotmail.com>
To: rajeev@iprg.nokia.com, ASINGH1@motorola.com
Cc: Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 16:35:13 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY1-F34oJjMJvCzxeB000198dc@hotmail.com>
X-OriginalArrivalTime: 20 Dec 2002 21:35:13.0538 (UTC) FILETIME=[AE171620:01C2A86F]
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

Hi,

I also support for the Intermediate Approach.
Thanks.

Eunsoo

>From: Rajeev Koodli <rajeev@iprg.nokia.com>
>To: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
>CC: Seamoby@ietf.org
>Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
>Date: Fri, 20 Dec 2002 12:03:08 -0800
>
>
>Ajoy,
>
>for MN - AR signaling, it would be good to have ICMP options.
>So, I guess that means "Intermediate Approach" without
>necessarily endorsing all the associated PROS and CONS.
>
>Regards,
>
>-Rajeev
>
>
>Singh Ajoy-ASINGH1 wrote:
>
> > Hello All,
> >
> > The CARD design team would like to solicit WG consensus about CARD
> > and FMIPv6 protocol inter-working.  The selection of anyone method
> > from the proposed list would help us to focus in the right direction
> > during the next phase of the protocol design. The high-level description
> > of the various approaches with their relative merits and de-merits is
> > listed below:
> >
> > Tight Coupling Approach
> > Intermediate Approach
> > Loose Coupling Approach
> >
> > Tight Coupling Approach: In this case, we can define CARD signaling as
> > an extension to the FMIPv6 messages. This makes the CARD protocol 
>tightly
> > coupled with FMIv6 protocol.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> > CARD and FMIPv6 implementation less complicated.
> >
> > CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> > This approach may also require modification to the present FMIPv6 
>protocol.
> >
> > Intermediate Approach: In this approach, we can define CARD signaling as
> > generic ICMP options. These ICMP options can be piggybacked upon any 
>ICMP
> > message including FMIPv6 signaling messages. Additionally, we can also 
>define
> > new CARD ICMP messages, which can be used when no outgoing ICMP messages 
>are
> > pending.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS: This approach enables the deployment of CARD along with any 
>protocol
> > including FMIPv6.  This also provides opportunity for additional 
>optimization
> > when deployed with FMIPv6 by exploiting the possibility of piggybacking 
>CARD
> > signaling over the FMIPv6 messages.
> >
> > CONS: The CARD protocol will be slightly more complex compared to the 
>other
> > approaches.
> >
> > Loose Coupling Approach: We can define CARD signaling as new set of 
>messages
> > and prohibit the possibility of piggybacking upon any FMIPv6 messages.
> >
> > The following are the PROS and CONS of this approach:
> >
> > PROS:De-couples CARD from any other protocol including FMIPv6. Probably 
>this
> > is simpler to implement.
> >
> > CONS: Adds extra over the air messages during critical path of handoff 
>which
> > may not be desirable for the most wireless link.
> >
> > Please send your choice if any.
> >
> > Regards,
> > Ajoy
> > _______________________________________________
> > 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/seamob

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail&xAPID=42&PS=47575&PI=7324&DI=7474&SU= 
http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_addphotos_3mf

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



From seamoby-admin@ietf.org  Fri Dec 20 17:00:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12748
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 17:00:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM35v12440;
	Fri, 20 Dec 2002 17:03:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM2Kv12373
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 17:02:20 -0500
Received: from fridge.docomolabs-usa.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12692
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:58:49 -0500 (EST)
Message-ID: <02bb01c2a873$2a715110$506015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@iprg.nokia.com>
Cc: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>, <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com> <00f301c2a84e$d4dbb840$506015ac@T23KEMPF> <3E0379D8.C3AF38AC@iprg.nokia.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 14:00:10 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I've moved the discussion to the MIP list, because it concerns how FMIPv6
signaling is done.

            jak

----- Original Message -----
From: "Rajeev Koodli" <rajeev@iprg.nokia.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>; <Seamoby@ietf.org>
Sent: Friday, December 20, 2002 12:13 PM
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking


>
> Hello Jim,
>
> James Kempf wrote:
>
> >
> > There has been a discussion in the MIP group about whether the FMIPv6
> > prehandover signaling should be completely decoupled from handover, but the
> > discussion has not reached any clear conclusion. One issue is whether
decoupling
> >
>
> On the [mobile ip] mailing list, I saw many folks favoring this "advance
signaling"
>
> prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> didn't hear any objections. I am willing to say that this is recommended in
the
> spec,
> while the MN MAY also do it during handover if it so wishes (please see the
ATL
> slides).
>
> > the signaling would also decouple any signaling between the mobile's current
> > access router and other access routers (i.e. HI/HAck). If no signaling
occurs
> > between access routers when the FMIPv6 signaling occurs (that is, it is for
> > information only), then that would be the equivalent of CARD. If signaling
does
> > occur, perhaps to pre-configure a care of address on the new subnet, then it
> > would be different.
>
> The implication is that HI/HAck would take place upon receiving FBU. It
probably
> does not make sense to create and manage handover state without knowledge of
> when exactly the MN is undergoing handover (again, see the ATL slides).
>
> Regards,
>
> -Rajeev
>
>
>
>

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


From mailnull@www1.ietf.org  Fri Dec 20 17:00:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12774
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 17:00:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKM3xm12477
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 17:03:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM3xv12474
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 17:03:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12751
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 17:00:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM35v12440;
	Fri, 20 Dec 2002 17:03:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM2Kv12373
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 17:02:20 -0500
Received: from fridge.docomolabs-usa.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12692
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 16:58:49 -0500 (EST)
Message-ID: <02bb01c2a873$2a715110$506015ac@T23KEMPF>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@iprg.nokia.com>
Cc: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>, <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com> <00f301c2a84e$d4dbb840$506015ac@T23KEMPF> <3E0379D8.C3AF38AC@iprg.nokia.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Fri, 20 Dec 2002 14:00:10 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I've moved the discussion to the MIP list, because it concerns how FMIPv6
signaling is done.

            jak

----- Original Message -----
From: "Rajeev Koodli" <rajeev@iprg.nokia.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>; <Seamoby@ietf.org>
Sent: Friday, December 20, 2002 12:13 PM
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking


>
> Hello Jim,
>
> James Kempf wrote:
>
> >
> > There has been a discussion in the MIP group about whether the FMIPv6
> > prehandover signaling should be completely decoupled from handover, but the
> > discussion has not reached any clear conclusion. One issue is whether
decoupling
> >
>
> On the [mobile ip] mailing list, I saw many folks favoring this "advance
signaling"
>
> prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> didn't hear any objections. I am willing to say that this is recommended in
the
> spec,
> while the MN MAY also do it during handover if it so wishes (please see the
ATL
> slides).
>
> > the signaling would also decouple any signaling between the mobile's current
> > access router and other access routers (i.e. HI/HAck). If no signaling
occurs
> > between access routers when the FMIPv6 signaling occurs (that is, it is for
> > information only), then that would be the equivalent of CARD. If signaling
does
> > occur, perhaps to pre-configure a care of address on the new subnet, then it
> > would be different.
>
> The implication is that HI/HAck would take place upon receiving FBU. It
probably
> does not make sense to create and manage handover state without knowledge of
> when exactly the MN is undergoing handover (again, see the ATL slides).
>
> Regards,
>
> -Rajeev
>
>
>
>

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



From seamoby-admin@ietf.org  Fri Dec 20 21:19:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18705
	for <seamoby-archive@lists.ietf.org>; Fri, 20 Dec 2002 21:19:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBL2LRv25397;
	Fri, 20 Dec 2002 21:21:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBL2Kov25373
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 21:20:50 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18695
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 21:17:17 -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 SAA15931;
	Fri, 20 Dec 2002 18:20:17 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBL2KDN17106;
	Fri, 20 Dec 2002 18:20:13 -0800
X-mProtect: <200212210220> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdyDRIKt; Fri, 20 Dec 2002 18:20:12 PST
Message-ID: <3E03CFDC.BCEE5AC1@iprg.nokia.com>
Date: Fri, 20 Dec 2002 18:20:12 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@bstormnetworks.com>
CC: James Kempf <kempf@docomolabs-usa.com>,
        Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
		 <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
		 <3E0379D8.C3AF38AC@iprg.nokia.com> <1040419193.3346.14.camel@localhost.localdomain>
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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Pat Calhoun wrote:

> > On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"
> >
> > prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> > didn't hear any objections. I am willing to say that this is recommended in the
> > spec,
> > while the MN MAY also do it during handover if it so wishes (please see the ATL
> > slides).
>
> Nothing is agreed upon in meetings - we can just gage consensus. We have
> to get agreement on the mailing list to get closure.
>

Agreed. However, my suggested changes are based on the discussion on
[mobile ip] list prior to Atlanta meeting. [See thread on "Thoughts on Extending
Handover Capability Extension"]

-Rajeev


>
> PatC

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


From mailnull@www1.ietf.org  Fri Dec 20 21:19:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18726
	for <seamoby-archive@odin.ietf.org>; Fri, 20 Dec 2002 21:19:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBL2MZd25415
	for seamoby-archive@odin.ietf.org; Fri, 20 Dec 2002 21:22:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBL2MZv25412
	for <seamoby-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 21:22:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18708
	for <seamoby-web-archive@ietf.org>; Fri, 20 Dec 2002 21:19:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBL2LRv25397;
	Fri, 20 Dec 2002 21:21:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBL2Kov25373
	for <seamoby@optimus.ietf.org>; Fri, 20 Dec 2002 21:20:50 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18695
	for <Seamoby@ietf.org>; Fri, 20 Dec 2002 21:17:17 -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 SAA15931;
	Fri, 20 Dec 2002 18:20:17 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gBL2KDN17106;
	Fri, 20 Dec 2002 18:20:13 -0800
X-mProtect: <200212210220> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdyDRIKt; Fri, 20 Dec 2002 18:20:12 PST
Message-ID: <3E03CFDC.BCEE5AC1@iprg.nokia.com>
Date: Fri, 20 Dec 2002 18:20:12 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@bstormnetworks.com>
CC: James Kempf <kempf@docomolabs-usa.com>,
        Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>, Seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
		 <00f301c2a84e$d4dbb840$506015ac@T23KEMPF>
		 <3E0379D8.C3AF38AC@iprg.nokia.com> <1040419193.3346.14.camel@localhost.localdomain>
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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Pat Calhoun wrote:

> > On the [mobile ip] mailing list, I saw many folks favoring this "advance signaling"
> >
> > prior toAtlanta IETF. During the fmip presentation at Atlanta on this issue, I
> > didn't hear any objections. I am willing to say that this is recommended in the
> > spec,
> > while the MN MAY also do it during handover if it so wishes (please see the ATL
> > slides).
>
> Nothing is agreed upon in meetings - we can just gage consensus. We have
> to get agreement on the mailing list to get closure.
>

Agreed. However, my suggested changes are based on the discussion on
[mobile ip] list prior to Atlanta meeting. [See thread on "Thoughts on Extending
Handover Capability Extension"]

-Rajeev


>
> PatC

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



From seamoby-admin@ietf.org  Sun Dec 22 15:28:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05443
	for <seamoby-archive@lists.ietf.org>; Sun, 22 Dec 2002 15:28:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBMKUkv20728;
	Sun, 22 Dec 2002 15:30:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBMKRJv20669
	for <seamoby@optimus.ietf.org>; Sun, 22 Dec 2002 15:27:19 -0500
Received: from letters.cs.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05401
	for <seamoby@ietf.org>; Sun, 22 Dec 2002 15:23:26 -0500 (EST)
Received: from vail.cs.ucsb.edu (vail [128.111.52.30])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id gBMKQS604793
	for <seamoby@ietf.org>; Sun, 22 Dec 2002 12:26:28 -0800 (PST)
Date: Sun, 22 Dec 2002 12:26:28 -0800 (PST)
From: "Robert C. Chalmers" <robertc@cs.ucsb.edu>
To: seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
In-Reply-To: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Message-ID: <Pine.LNX.4.21.0212221222430.11615-100000@vail.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

I'm in favor of the intermediate approach. If Fast MIPv6 is available, it
makes sense to allow CARD content to be exchanged inline since the two
protocols do have some overlap in the AR-MN signalling, but I'd hate to
see CARD only applicable to Fast MIPv6.

On Fri, 20 Dec 2002, Singh Ajoy-ASINGH1 wrote:

> Hello All,
> 
> The CARD design team would like to solicit WG consensus about CARD 
> and FMIPv6 protocol inter-working.  The selection of anyone method 
> from the proposed list would help us to focus in the right direction 
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is 
> listed below:
>  
> Tight Coupling Approach 
> Intermediate Approach
> Loose Coupling Approach 
> 
> Tight Coupling Approach: In this case, we can define CARD signaling as 
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
> CARD and FMIPv6 implementation less complicated. 
> 
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
> This approach may also require modification to the present FMIPv6 protocol. 
> 
> Intermediate Approach: In this approach, we can define CARD signaling as 
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
> message including FMIPv6 signaling messages. Additionally, we can also define 
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
> pending. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS: This approach enables the deployment of CARD along with any protocol 
> including FMIPv6.  This also provides opportunity for additional optimization 
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
> signaling over the FMIPv6 messages. 
>  
> CONS: The CARD protocol will be slightly more complex compared to the other 
> approaches.
> 
> Loose Coupling Approach: We can define CARD signaling as new set of messages 
> and prohibit the possibility of piggybacking upon any FMIPv6 messages. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement. 
>  
> CONS: Adds extra over the air messages during critical path of handoff which 
> may not be desirable for the most wireless link. 
> 
> Please send your choice if any.
> 
> Regards,
> Ajoy
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

/****************************************************************

 Robert Chalmers
 UCSB Computer Science Doctoral Candidate
 Network and Multimedia Systems Lab (NMSL)

 "My heart is in the code, but my soul lies in the process"
 
 | robertc@cs.ucsb.edu || http://www.cs.ucsb.edu/~robertc/ |

*****************************************************************/

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


From mailnull@www1.ietf.org  Sun Dec 22 15:28:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05468
	for <seamoby-archive@odin.ietf.org>; Sun, 22 Dec 2002 15:28:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBMKW1t20771
	for seamoby-archive@odin.ietf.org; Sun, 22 Dec 2002 15:32:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBMKW1v20768
	for <seamoby-web-archive@optimus.ietf.org>; Sun, 22 Dec 2002 15:32:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05457
	for <seamoby-web-archive@ietf.org>; Sun, 22 Dec 2002 15:28:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBMKUkv20728;
	Sun, 22 Dec 2002 15:30:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBMKRJv20669
	for <seamoby@optimus.ietf.org>; Sun, 22 Dec 2002 15:27:19 -0500
Received: from letters.cs.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05401
	for <seamoby@ietf.org>; Sun, 22 Dec 2002 15:23:26 -0500 (EST)
Received: from vail.cs.ucsb.edu (vail [128.111.52.30])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id gBMKQS604793
	for <seamoby@ietf.org>; Sun, 22 Dec 2002 12:26:28 -0800 (PST)
Date: Sun, 22 Dec 2002 12:26:28 -0800 (PST)
From: "Robert C. Chalmers" <robertc@cs.ucsb.edu>
To: seamoby@ietf.org
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
In-Reply-To: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Message-ID: <Pine.LNX.4.21.0212221222430.11615-100000@vail.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>

I'm in favor of the intermediate approach. If Fast MIPv6 is available, it
makes sense to allow CARD content to be exchanged inline since the two
protocols do have some overlap in the AR-MN signalling, but I'd hate to
see CARD only applicable to Fast MIPv6.

On Fri, 20 Dec 2002, Singh Ajoy-ASINGH1 wrote:

> Hello All,
> 
> The CARD design team would like to solicit WG consensus about CARD 
> and FMIPv6 protocol inter-working.  The selection of anyone method 
> from the proposed list would help us to focus in the right direction 
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is 
> listed below:
>  
> Tight Coupling Approach 
> Intermediate Approach
> Loose Coupling Approach 
> 
> Tight Coupling Approach: In this case, we can define CARD signaling as 
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
> CARD and FMIPv6 implementation less complicated. 
> 
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
> This approach may also require modification to the present FMIPv6 protocol. 
> 
> Intermediate Approach: In this approach, we can define CARD signaling as 
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
> message including FMIPv6 signaling messages. Additionally, we can also define 
> new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
> pending. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS: This approach enables the deployment of CARD along with any protocol 
> including FMIPv6.  This also provides opportunity for additional optimization 
> when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
> signaling over the FMIPv6 messages. 
>  
> CONS: The CARD protocol will be slightly more complex compared to the other 
> approaches.
> 
> Loose Coupling Approach: We can define CARD signaling as new set of messages 
> and prohibit the possibility of piggybacking upon any FMIPv6 messages. 
> 
> The following are the PROS and CONS of this approach:
> 
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
> is simpler to implement. 
>  
> CONS: Adds extra over the air messages during critical path of handoff which 
> may not be desirable for the most wireless link. 
> 
> Please send your choice if any.
> 
> Regards,
> Ajoy
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

/****************************************************************

 Robert Chalmers
 UCSB Computer Science Doctoral Candidate
 Network and Multimedia Systems Lab (NMSL)

 "My heart is in the code, but my soul lies in the process"
 
 | robertc@cs.ucsb.edu || http://www.cs.ucsb.edu/~robertc/ |

*****************************************************************/

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



From seamoby-admin@ietf.org  Mon Dec 23 01:04:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12333
	for <seamoby-archive@lists.ietf.org>; Mon, 23 Dec 2002 01:04:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBN5vmv10417;
	Mon, 23 Dec 2002 00:57:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBN5urv10395
	for <seamoby@optimus.ietf.org>; Mon, 23 Dec 2002 00:56:53 -0500
Received: from ns.sait.samsung.co.kr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12156
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 00:52:54 -0500 (EST)
Received: from bright (localhost [127.0.0.1])
	by ns.sait.samsung.co.kr (8.12.1/8.12.1) with SMTP id gBN5twHR015921
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 14:55:58 +0900 (KST)
Message-ID: <006701c2aa47$ebff9230$9429024b@bright>
From: "Xiaoming Wang" <xmwang@sait.samsung.co.kr>
To: <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Mon, 23 Dec 2002 14:55:39 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I think the criterion of choice is whether CARD is big enough to be a
seperate one.
It decides the value of profit vs cost.

I'm in favor of the first one: Tight Coupling Approach
And the second one is also OK.

Xiaoming Wang
=========================================================
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea

Phone: 82-31-280-9615
Fax:      82-31-280-9569
EMail:   xmwang@sait.samsung.co.kr
=========================================================

----- Original Message -----
From: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>
To: <Seamoby@ietf.org>
Sent: Saturday, December 21, 2002 01:35
Subject: [Seamoby] CARD - FMIPv6 protocol interworking


> Hello All,
>
> The CARD design team would like to solicit WG consensus about CARD
> and FMIPv6 protocol inter-working.  The selection of anyone method
> from the proposed list would help us to focus in the right direction
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is
> listed below:
>
> Tight Coupling Approach
> Intermediate Approach
> Loose Coupling Approach
>
> Tight Coupling Approach: In this case, we can define CARD signaling as
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol.
>
> The following are the PROS and CONS of this approach:
>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6
protocol.
>
> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also
define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages
are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional
optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking
CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the
other
> approaches.
>
> Loose Coupling Approach: We can define CARD signaling as new set of
messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably
this
> is simpler to implement.
>
> CONS: Adds extra over the air messages during critical path of handoff
which
> may not be desirable for the most wireless link.
>
> Please send your choice if any.
>
> Regards,
> Ajoy
> _______________________________________________
> 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 mailnull@www1.ietf.org  Mon Dec 23 01:05:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12354
	for <seamoby-archive@odin.ietf.org>; Mon, 23 Dec 2002 01:05:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBN68sr11333
	for seamoby-archive@odin.ietf.org; Mon, 23 Dec 2002 01:08:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBN68sv11330
	for <seamoby-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 01:08:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12346
	for <seamoby-web-archive@ietf.org>; Mon, 23 Dec 2002 01:04:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBN5vmv10417;
	Mon, 23 Dec 2002 00:57:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBN5urv10395
	for <seamoby@optimus.ietf.org>; Mon, 23 Dec 2002 00:56:53 -0500
Received: from ns.sait.samsung.co.kr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12156
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 00:52:54 -0500 (EST)
Received: from bright (localhost [127.0.0.1])
	by ns.sait.samsung.co.kr (8.12.1/8.12.1) with SMTP id gBN5twHR015921
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 14:55:58 +0900 (KST)
Message-ID: <006701c2aa47$ebff9230$9429024b@bright>
From: "Xiaoming Wang" <xmwang@sait.samsung.co.kr>
To: <Seamoby@ietf.org>
References: <A5B4C9A2AD89D411AB3E009027B0DA1E07862638@IL27EXM09.cig.mot.com>
Subject: Re: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Mon, 23 Dec 2002 14:55:39 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think the criterion of choice is whether CARD is big enough to be a
seperate one.
It decides the value of profit vs cost.

I'm in favor of the first one: Tight Coupling Approach
And the second one is also OK.

Xiaoming Wang
=========================================================
Network Protocol Technical Group, i-Networking lab
Samsung Advanced Institute of Technology, South Korea

Phone: 82-31-280-9615
Fax:      82-31-280-9569
EMail:   xmwang@sait.samsung.co.kr
=========================================================

----- Original Message -----
From: "Singh Ajoy-ASINGH1" <ASINGH1@motorola.com>
To: <Seamoby@ietf.org>
Sent: Saturday, December 21, 2002 01:35
Subject: [Seamoby] CARD - FMIPv6 protocol interworking


> Hello All,
>
> The CARD design team would like to solicit WG consensus about CARD
> and FMIPv6 protocol inter-working.  The selection of anyone method
> from the proposed list would help us to focus in the right direction
> during the next phase of the protocol design. The high-level description
> of the various approaches with their relative merits and de-merits is
> listed below:
>
> Tight Coupling Approach
> Intermediate Approach
> Loose Coupling Approach
>
> Tight Coupling Approach: In this case, we can define CARD signaling as
> an extension to the FMIPv6 messages. This makes the CARD protocol tightly
> coupled with FMIv6 protocol.
>
> The following are the PROS and CONS of this approach:
>
> PROS: Enables inter-working of CARD and FMIPv6. Probably this will make
> CARD and FMIPv6 implementation less complicated.
>
> CONS: This approach restricts the deployment of CARD to FMIpv6 only.
> This approach may also require modification to the present FMIPv6
protocol.
>
> Intermediate Approach: In this approach, we can define CARD signaling as
> generic ICMP options. These ICMP options can be piggybacked upon any ICMP
> message including FMIPv6 signaling messages. Additionally, we can also
define
> new CARD ICMP messages, which can be used when no outgoing ICMP messages
are
> pending.
>
> The following are the PROS and CONS of this approach:
>
> PROS: This approach enables the deployment of CARD along with any protocol
> including FMIPv6.  This also provides opportunity for additional
optimization
> when deployed with FMIPv6 by exploiting the possibility of piggybacking
CARD
> signaling over the FMIPv6 messages.
>
> CONS: The CARD protocol will be slightly more complex compared to the
other
> approaches.
>
> Loose Coupling Approach: We can define CARD signaling as new set of
messages
> and prohibit the possibility of piggybacking upon any FMIPv6 messages.
>
> The following are the PROS and CONS of this approach:
>
> PROS:De-couples CARD from any other protocol including FMIPv6. Probably
this
> is simpler to implement.
>
> CONS: Adds extra over the air messages during critical path of handoff
which
> may not be desirable for the most wireless link.
>
> Please send your choice if any.
>
> Regards,
> Ajoy
> _______________________________________________
> 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 23 14:41:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13689
	for <seamoby-archive@lists.ietf.org>; Mon, 23 Dec 2002 14:41:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNJiQv32515;
	Mon, 23 Dec 2002 14:44:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNJhGv32470
	for <seamoby@optimus.ietf.org>; Mon, 23 Dec 2002 14:43:16 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13595
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 14:39:12 -0500 (EST)
From: Govind.Krishnamurthi@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gBNJgL828972
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 13:42:21 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5f5809da48ac12f255079@davir02nok.americas.nokia.com>;
 Mon, 23 Dec 2002 13:42:13 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 23 Dec 2002 13:42:13 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Mon, 23 Dec 2002 14:42:12 -0500
Message-ID: <A6D9D7495456414BA08DB655C2AC6712108711@bsebe001.americas.nokia.com>
Thread-Topic: [Seamoby] CARD - FMIPv6 protocol interworking
Thread-Index: AcKoRtZA7lToRKtySTexXIi1iRurPACc6h1Q
To: <ASINGH1@motorola.com>, <Seamoby@ietf.org>
X-OriginalArrivalTime: 23 Dec 2002 19:42:13.0698 (UTC) FILETIME=[643ADA20:01C2AABB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBNJhGv32471
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello Ajoy,
I support the Intermediate Approach. 

Thanks,
Govind.

-----Original Message-----
From: ext Singh Ajoy-ASINGH1 [mailto:ASINGH1@motorola.com]
Sent: Friday, December 20, 2002 11:36 AM
To: Seamoby@ietf.org
Subject: [Seamoby] CARD - FMIPv6 protocol interworking


Hello All,

The CARD design team would like to solicit WG consensus about CARD 
and FMIPv6 protocol inter-working.  The selection of anyone method 
from the proposed list would help us to focus in the right direction 
during the next phase of the protocol design. The high-level description
of the various approaches with their relative merits and de-merits is 
listed below:
 
Tight Coupling Approach 
Intermediate Approach
Loose Coupling Approach 

Tight Coupling Approach: In this case, we can define CARD signaling as 
an extension to the FMIPv6 messages. This makes the CARD protocol tightly
coupled with FMIv6 protocol. 

The following are the PROS and CONS of this approach:

PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
CARD and FMIPv6 implementation less complicated. 

CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
This approach may also require modification to the present FMIPv6 protocol. 

Intermediate Approach: In this approach, we can define CARD signaling as 
generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
message including FMIPv6 signaling messages. Additionally, we can also define 
new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
pending. 

The following are the PROS and CONS of this approach:

PROS: This approach enables the deployment of CARD along with any protocol 
including FMIPv6.  This also provides opportunity for additional optimization 
when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
signaling over the FMIPv6 messages. 
 
CONS: The CARD protocol will be slightly more complex compared to the other 
approaches.

Loose Coupling Approach: We can define CARD signaling as new set of messages 
and prohibit the possibility of piggybacking upon any FMIPv6 messages. 

The following are the PROS and CONS of this approach:

PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
is simpler to implement. 
 
CONS: Adds extra over the air messages during critical path of handoff which 
may not be desirable for the most wireless link. 

Please send your choice if any.

Regards,
Ajoy
_______________________________________________
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 mailnull@www1.ietf.org  Mon Dec 23 14:41:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13727
	for <seamoby-archive@odin.ietf.org>; Mon, 23 Dec 2002 14:41:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBNJjWW32554
	for seamoby-archive@odin.ietf.org; Mon, 23 Dec 2002 14:45:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNJjVv32551
	for <seamoby-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 14:45:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13694
	for <seamoby-web-archive@ietf.org>; Mon, 23 Dec 2002 14:41:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNJiQv32515;
	Mon, 23 Dec 2002 14:44:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBNJhGv32470
	for <seamoby@optimus.ietf.org>; Mon, 23 Dec 2002 14:43:16 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13595
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 14:39:12 -0500 (EST)
From: Govind.Krishnamurthi@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gBNJgL828972
	for <Seamoby@ietf.org>; Mon, 23 Dec 2002 13:42:21 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5f5809da48ac12f255079@davir02nok.americas.nokia.com>;
 Mon, 23 Dec 2002 13:42:13 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 23 Dec 2002 13:42:13 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: [Seamoby] CARD - FMIPv6 protocol interworking
Date: Mon, 23 Dec 2002 14:42:12 -0500
Message-ID: <A6D9D7495456414BA08DB655C2AC6712108711@bsebe001.americas.nokia.com>
Thread-Topic: [Seamoby] CARD - FMIPv6 protocol interworking
Thread-Index: AcKoRtZA7lToRKtySTexXIi1iRurPACc6h1Q
To: <ASINGH1@motorola.com>, <Seamoby@ietf.org>
X-OriginalArrivalTime: 23 Dec 2002 19:42:13.0698 (UTC) FILETIME=[643ADA20:01C2AABB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBNJhGv32471
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer,
	Handoff Candidate Discovery,
	and Dormant Mode Host Alerting  <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>,
	<mailto:seamoby-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello Ajoy,
I support the Intermediate Approach. 

Thanks,
Govind.

-----Original Message-----
From: ext Singh Ajoy-ASINGH1 [mailto:ASINGH1@motorola.com]
Sent: Friday, December 20, 2002 11:36 AM
To: Seamoby@ietf.org
Subject: [Seamoby] CARD - FMIPv6 protocol interworking


Hello All,

The CARD design team would like to solicit WG consensus about CARD 
and FMIPv6 protocol inter-working.  The selection of anyone method 
from the proposed list would help us to focus in the right direction 
during the next phase of the protocol design. The high-level description
of the various approaches with their relative merits and de-merits is 
listed below:
 
Tight Coupling Approach 
Intermediate Approach
Loose Coupling Approach 

Tight Coupling Approach: In this case, we can define CARD signaling as 
an extension to the FMIPv6 messages. This makes the CARD protocol tightly
coupled with FMIv6 protocol. 

The following are the PROS and CONS of this approach:

PROS: Enables inter-working of CARD and FMIPv6. Probably this will make 
CARD and FMIPv6 implementation less complicated. 

CONS: This approach restricts the deployment of CARD to FMIpv6 only.  
This approach may also require modification to the present FMIPv6 protocol. 

Intermediate Approach: In this approach, we can define CARD signaling as 
generic ICMP options. These ICMP options can be piggybacked upon any ICMP 
message including FMIPv6 signaling messages. Additionally, we can also define 
new CARD ICMP messages, which can be used when no outgoing ICMP messages are 
pending. 

The following are the PROS and CONS of this approach:

PROS: This approach enables the deployment of CARD along with any protocol 
including FMIPv6.  This also provides opportunity for additional optimization 
when deployed with FMIPv6 by exploiting the possibility of piggybacking CARD 
signaling over the FMIPv6 messages. 
 
CONS: The CARD protocol will be slightly more complex compared to the other 
approaches.

Loose Coupling Approach: We can define CARD signaling as new set of messages 
and prohibit the possibility of piggybacking upon any FMIPv6 messages. 

The following are the PROS and CONS of this approach:

PROS:De-couples CARD from any other protocol including FMIPv6. Probably this
is simpler to implement. 
 
CONS: Adds extra over the air messages during critical path of handoff which 
may not be desirable for the most wireless link. 

Please send your choice if any.

Regards,
Ajoy
_______________________________________________
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



