From mip6-bounces@ietf.org Mon May 02 11:23:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DScli-0006qA-Oo; Mon, 02 May 2005 11:23:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DSclg-0006eW-9P
	for mip6@megatron.ietf.org; Mon, 02 May 2005 11:23:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25710
	for <mip6@ietf.org>; Mon, 2 May 2005 11:23:30 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DSczM-0005vE-PT
	for mip6@ietf.org; Mon, 02 May 2005 11:37:42 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j42FN9o21628; Mon, 2 May 2005 17:23:09 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j42FN9NZ027153; Mon, 2 May 2005 17:23:09 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200505021523.j42FN9NZ027153@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] Comments on draft-ietf-mip6-ikev2-ipsec-01 
In-reply-to: Your message of Thu, 14 Apr 2005 15:17:57 PDT.
	<425EEC15.2000103@iprg.nokia.com> 
Date: Mon, 02 May 2005 17:23:09 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >    okay. atleast we agree that the tunnel mode shouldnt be the default.
   >    you want it explicitly mentioned in the draft?
   >    
   > => I don't believe the word default is necessary: IMHO we should just
   > present things in the right order and explain there are two alternatives
   > to the selector = MH protocol.
   > 
   >    > the default mode should be the same than in 3776, i.e.,
   >    > MH protocol as the selector. But the two others (all traffic and only
   >    > the critical MH types) have to be allowed.
   >    
   > => in fact any selector set which provides the right protection should be
   > allowed... The two alternatives need to be detailed because they have
   > some advantages so should become common. Of course both sides should
   > agree before.
   
   so you want the default mode be the same as in RFC 3776, but present
   the "tunnel everything" mode and the "MH type as a selector" as two
   options?
   
=> yes but even without the word default and of course a SHOULD or a MUST
support.

   I disagree with this. IMHO, the "MH type as a selector" should be
   supported atleast by the Home Agent, so that some mobiles can take
   advantage of this.

=> you are trying to enforce a market decision through a standard
specification... This won't work. And don't forget the MN and HA managers
must agree about security policy (and this choice is part of it) before
any operation...

   the "tunnel everything mode" can be specified
   as part of privacy solution documents.
   
=> IMHO we should constraint the options and provide one as the basic one.
Anything more won't help in the real world.

Regards

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 02 15:53:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DSgzE-0007am-Qg; Mon, 02 May 2005 15:53:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DSgzA-0007Zi-89; Mon, 02 May 2005 15:53:44 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27215;
	Mon, 2 May 2005 15:53:42 -0400 (EDT)
Message-Id: <200505021953.PAA27215@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 02 May 2005 15:53:42 -0400
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-aaa-ha-goals-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv6 Working Group of the IETF.

	Title		: Goals for AAA-HA interface
	Author(s)	: G. Giaretta, et al.
	Filename	: draft-ietf-mip6-aaa-ha-goals-00.txt
	Pages		: 17
	Date		: 2005-5-2
	
In commercial deployments Mobile IPv6 can be a service offered by a 
   Mobility Services Provider (MSP). In this case all protocol 
   operations may need to be explicitely authorized and traced. A 
   convenient approach to do that is to define an interface between the 
   Home Agent (HA) and the AAA infrastructure of the MSP, which stores 
   user's credentials and service profiles. The availability of this 
   interface can be useful also to enable dynamic Mobile IPv6 
   bootstrapping on both the mobile node and the designated HA.
   This document describes various scenarios where an interface between 
   the HA and the AAA infrastructure of the MSP is required. 
   Furthermore, a list of design goals for this interface is provided.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-aaa-ha-goals-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-aaa-ha-goals-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip6-aaa-ha-goals-00.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--NextPart--






From mip6-bounces@ietf.org Mon May 02 17:43:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DSihL-0003A9-0E; Mon, 02 May 2005 17:43:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DSihJ-0003A1-Gi
	for mip6@megatron.ietf.org; Mon, 02 May 2005 17:43:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18647
	for <mip6@ietf.org>; Mon, 2 May 2005 17:43:23 -0400 (EDT)
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DSiv3-0003G2-9p
	for mip6@ietf.org; Mon, 02 May 2005 17:57:38 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j42LhCmg014807; Mon, 2 May 2005 16:43:12 -0500 (CDT)
Message-ID: <42769EF0.8D90AF5D@alcatel.com>
Date: Mon, 02 May 2005 16:43:12 -0500
From: Tim Ozugur <tim.ozugur@alcatel.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by auds952.usa.alcatel.com
	id j42LhCmg014807
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Call For Participation: BWAN 2005
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


(Apologies if you are receiving this message more than once)

------------------------------------------------------------------
                   CALL FOR PARTICIPATION

                 International Workshop on=20
Broadband Wireless Access Network on fixed network (BWAN 2005)
                   (http://www.bwan.org/)

                ORLANDO, FL - JUNE 15, 2005

co-located with International Conference on Multimedia Services=20
     Access Networks (MSAN '05: http://www.msan.org)

                   CO_SPONSORED BY IEEE

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

Scope:

Workshop: Broadband Wireless Access based on fixed Network=20
(xDSL, FTTx, etc ).=20

This Workshop will deal about complementary wireless broadband access
network based on wired network (xDSL, FTTx, etc), 3G/4G and also about
different techniques that can solved the tremendous challenges making
the sharing of each phone line accessible through wireless access with a
minimum guarantee of service for any connected user. In this workshop,
the challenges to develop a new low cost mobile or semi-mobile access
network with low powering unit will be explored and that may complement
UMTS.=20

The workshop is intended to present new architectures of fixed network
supporting mobility and/or nomadic features for wireless access (802.11,
WiMax,=85802.20=85.), the sharing of the network access, bandwidth sharin=
g
on radio access. (Single Hop, mesh,=85) and discuss about the perspective=
s
of shared access network enhanced with wireless extension based on
technologies such as WiFi,.. 802.16,.. 802.20, etc to maximize the
performance of the overall link and reduce the costs. Within the
framework of BWAN 2005, a new research field to prepare the next
generation of network access.=20

Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications
based on Internet.=20

Workshop Topics:
- New Architectures and technologies for broadband wireless=20
  access on fixed network(xDSL/FTTx,etc) with mobility features=20
- AAA (Authentification, Authorization, Accounting)=20
- Micro and macro mobility=20
- Medium access control (QoS, bandwidth sharing, fairness)=20
- End to end security and privacy issues on Mobile and/or nomadic=20
  Access Network=20
- Low cost and low power integrated xDSL/FTTx+WiFi modem with=20
  mobility enhancement=20
- Network cost performance and Business Models SLA-based services=20
- Radio extension such as 802.xy (WiFi, WiMax, etc) =20

Relating Topics:=20
- Modulation, coding and antennas (MIMO)=20
- Interference mitigation for multiple access=20
- Complementary solutions to UMTS=20
- Location-Based Services Applications=20
- Scalability issues to large number of sites=20
- Standard and regulations=20
- IPv6 impact=20
- Mesh extensions

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 03 13:52:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DT1ZP-0002Kw-IS; Tue, 03 May 2005 13:52:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DT1ZO-0002Kr-82
	for mip6@megatron.ietf.org; Tue, 03 May 2005 13:52:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14827
	for <mip6@ietf.org>; Tue, 3 May 2005 13:52:28 -0400 (EDT)
Received: from nairobi.ucdavis.edu ([169.237.104.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DT1nI-0008BY-GR
	for mip6@ietf.org; Tue, 03 May 2005 14:06:54 -0400
Received: from tremex.ucdavis.edu (tremex.ucdavis.edu [169.237.104.172])
	by nairobi.ucdavis.edu (8.12.10/8.12.9/it-defang-5.2.0) with ESMTP id
	j43HqOLB016828
	for <mip6@ietf.org>; Tue, 3 May 2005 10:52:25 -0700 (PDT)
Received: from tremex.ucdavis.edu (localhost [127.0.0.1])
	by tremex.ucdavis.edu (8.12.10/8.12.9/UCD5.2.0) with ESMTP id
	j43HqOdS007097
	for <mip6@ietf.org>; Tue, 3 May 2005 10:52:24 -0700 (PDT)
Received: (from www@localhost)
	by tremex.ucdavis.edu (8.12.10/8.12.9/Submit) id j43HqOi2007096;
	Tue, 3 May 2005 10:52:24 -0700 (PDT)
Date: Tue, 3 May 2005 10:52:24 -0700 (PDT)
Message-Id: <200505031752.j43HqOi2007096@tremex.ucdavis.edu>
To: mip6@ietf.org
From: "Fan Zhao" <fanzhao@ucdavis.edu>
X-Errors-To: fanzhao@blue.ucdavis.edu
X-Mailer: Geckomail-b16
X-Originating-IP: [128.120.178.196]
X-User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Scanned-By: MIMEDefang 2.49 on 169.237.104.195
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Subject: [Mip6] Call for Paper: JSAC-MRNM
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


       PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES       

                            CALL FOR PAPERS                            
            IEEE Journal on Selected Areas in Communications            
                  MOBILE ROUTERS AND NETWORK MOBILITY                  

  http://www.argreenhouse.com/society/J-SAC/Calls/mobile_routers.html

Network mobility support is concerned with managing the mobility of an 
entire network that is changing its point of attachment to the Internet 
and thus its reachability in the Internet topology. If network mobility 
is not explicitly supported by some mechanisms, existing sessions break 
and connectivity to the global Internet is lost. A mobile network is 
composed of Mobile Router(s) (MR) and Mobile Network Nodes (MNN) that 
can be fixed or mobile. There has been rapid development in network 
mobility support, i.e., providing Internet connectivity to the networks 
that move using mobile routers since the inception of Mobile IPv4 in 
1996. Seamless Internet access in public transportation such as in 
trains and busses can be possible if mobile routers are used. Cars with 
low-power sensors seamlessly connected to the Internet constitute yet 
another example of networks which move. To date, some airline companies 
announced Internet connectivity support during commercial flights and 
this trend is expected to accelerate and cover most if not all flights. 

This issue is focused on modeling, analysis, and simulation of network 
mobility support protocols. We solicit papers presenting original and 
unpublished work including, but not limited to the following topics: 

* Modeling and Analysis of Network Mobility 
    o Modeling, analysis and simulation of mobile router 
    o Protocols for route optimization 
    o Mobility issues inside a mobile network 
    o Mobile IPv6 extensions for route optimization 
    o Nested mobile networks 
    o Multihomed mobile networks 
    o Operational issues to deploy mobile networks 
    o Auto-configuration for mobile networks 
    o Mobile router support on cellular phone platforms 

* Services in the Networks that Move 
    o Service advertisement and discovery protocols in networks that
      move 
    o Specifications nad models of services for network mobility 
    o Encryption and authentication in service access for network
      mobility 

* Security Issues in Network Mobility 
    o Security analysis of present network mobility support protocols 
    o Applications of AAA and EAP to network mobility 
    o Interaction with security-enhanced modules in other layers 
      (vertically) or other middle boxes (horizontally) 

Prospective authors should follow the IEEE J-SAC manuscript format 
described in the Information for Authors. Authors MUST submit their 
draft manuscripts through the EDAS peer review website, together with a 
short abstract (approximately 150 words) in the EDAS website form. 
Please note potential authors should create their own accounts through 
the EDAS peer review website before submitting manuscript(s). EDAS will 
accept manuscripts in PDF format only. There will be one round of 
reviewers and acceptance will be limited to those papers requiring only 
moderate revisions. The following timetable applies: 

Manuscript Submission: JUNE 1, 2005
Acceptance Notification: December 1, 2005
Final Manuscript Due: March 1, 2006
Publication: 3rd Quarter 2006

Guest Editorial Board: 

Behcet Sarikaya
Computer Science Dept
Univ of Northern British Columbia
Prince George, BC
Canada V2N 4Z9
sarikaya@unbc.ca

S. Felix Wu
Dept of Computer Science
Univ of California at Davis
Davis, CA 95616 USA
wu@cs.ucdavis.edu

Gopal Dommety
Cisco Systems, Inc
170 West Tasman Dr
San Jose, CA 95134-1706 USA
gdommety@cisco.com

Claude Castelluccia
INRIA Rhône-Alpes ZIRST
655 Ave de l'Europe
Montbonnot
38334 Saint Ismier cedex
France
claude.castelluccia@inria.fr

Thierry Ernst
Jun Murai Lab
Keio Univ K-square
Town Campus
1488-8 Ogura, Saiwai-ku,
Kawasaki, Kanagawa 212-0054
Japan
ernst@sfc.wide.ad.jp

Charles E. Perkins
Communication Systems Lab
Nokia Research Center
313 Fairchild Dr
Mountain View, CA 94943 USA
charliep@iprg.nokia.com

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 04 14:14:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTOOK-0003on-G3; Wed, 04 May 2005 14:14:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DTOOJ-0003oc-3g
	for mip6@megatron.ietf.org; Wed, 04 May 2005 14:14:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09715
	for <mip6@ietf.org>; Wed, 4 May 2005 14:14:33 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DTOcQ-0007Cd-Dj
	for mip6@ietf.org; Wed, 04 May 2005 14:29:11 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j44IEVM26340
	for <mip6@ietf.org>; Wed, 4 May 2005 21:14:31 +0300 (EET DST)
X-Scanned: Wed, 4 May 2005 21:14:22 +0300 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id j44IEMO8009521
	for <mip6@ietf.org>; Wed, 4 May 2005 21:14:22 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00m8ZWLX; Wed, 04 May 2005 21:14:21 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j44IEKu26720
	for <mip6@ietf.org>; Wed, 4 May 2005 21:14:21 +0300 (EET DST)
Received: from esebh006.NOE.Nokia.com ([172.21.138.88]) by
	esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 4 May 2005 21:14:01 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh006.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 4 May 2005 21:14:01 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 4 May 2005 13:13:57 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 4 May 2005 13:13:49 -0500
Message-ID: <456943D540CFC14A8D7138E64843F8535BAEA0@daebe101.NOE.Nokia.com>
Thread-Topic: Please review draft-irtf-mobopts-ro-enhancements-00.txt
Thread-Index: AcVQ1QUtp2C4lDdbQemmEoS4Igarhw==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 04 May 2005 18:13:57.0257 (UTC)
	FILETIME=[09CC5790:01C550D5]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Please review draft-irtf-mobopts-ro-enhancements-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


The Mobopts RG has produced the following ID:
http://www.ietf.org/internet-drafts/draft-irtf-mobopts-ro-enhancements-00=
.txt

Please review the ID and comment.

-Basvaaraj

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 05 16:24:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTmtg-0007kT-9W; Thu, 05 May 2005 16:24:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTmtc-0007jZ-Co; Thu, 05 May 2005 16:24:32 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09203;
	Thu, 5 May 2005 16:24:29 -0400 (EDT)
Message-Id: <200505052024.QAA09203@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 05 May 2005 16:24:28 -0400
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-firewalls-02.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv6 Working Group of the IETF.

	Title		: Mobile IPv6 and Firewalls: Problem statement
	Author(s)	: F. Le, et al.
	Filename	: draft-ietf-mip6-firewalls-02.txt
	Pages		: 23
	Date		: 2005-5-5
	
Network elements such as firewalls are an integral aspect of a
   majority of IP networks today, given the state of security in the
   Internet, threats, and vulnerabilities to data networks.  Current IP
   networks are predominantly based on IPv4 technology and hence
   firewalls have been designed for these networks.  Deployment of IPv6
   networks is currently progressing, albeit at a slower pace.
   Firewalls for IPv6 networks are still maturing and in development.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-firewalls-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mip6-firewalls-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-firewalls-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-mip6-firewalls-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--NextPart--






From mip6-bounces@ietf.org Fri May 06 02:39:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTwVC-0000Zj-4Z; Fri, 06 May 2005 02:39:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DTwVA-0000Ze-Fc
	for mip6@megatron.ietf.org; Fri, 06 May 2005 02:39:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05316
	for <mip6@ietf.org>; Fri, 6 May 2005 02:39:54 -0400 (EDT)
Received: from bay106-f16.bay106.hotmail.com ([65.54.161.26] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DTwjb-0003D7-9C
	for mip6@ietf.org; Fri, 06 May 2005 02:54:52 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 5 May 2005 23:39:42 -0700
Message-ID: <BAY106-F164B641EE089C83D025D25F91B0@phx.gbl>
Received: from 65.54.161.203 by by106fd.bay106.hotmail.msn.com with HTTP;
	Fri, 06 May 2005 06:39:42 GMT
X-Originating-IP: [65.54.161.203]
X-Originating-Email: [adnan_kh79@hotmail.com]
X-Sender: adnan_kh79@hotmail.com
From: "adnan khalid" <adnan_kh79@hotmail.com>
To: mip6@ietf.org
Date: Fri, 06 May 2005 06:39:42 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 06 May 2005 06:39:42.0384 (UTC)
	FILETIME=[6262A300:01C55206]
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Subject: [Mip6] (no subject)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org





_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 06 09:18:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DU2j8-0004h5-WF; Fri, 06 May 2005 09:18:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DU2j4-0004dR-7O; Fri, 06 May 2005 09:18:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13226;
	Fri, 6 May 2005 09:18:40 -0400 (EDT)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DU2xX-0003pD-ST; Fri, 06 May 2005 09:33:41 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IG200ANCL445R@szxga01-in.huawei.com>; Fri,
	06 May 2005 21:21:41 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IG200ANQL442Z@szxga01-in.huawei.com>; Fri,
	06 May 2005 21:21:40 +0800 (CST)
Received: from keshavaak ([10.18.4.181])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IG2002QGLAHNC@szxml01-in.huawei.com>; Fri,
	06 May 2005 21:25:31 +0800 (CST)
Date: Fri, 06 May 2005 18:48:32 +0530
From: Keshava Ayanur <keshavaak@huawei.com>
To: ipv6@ietf.org, mip6@ietf.org
Message-id: <000001c5523e$1ab581c0$b504120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: 
Subject: [Mip6] Anycast Address becoming Multicast address ....
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: keshavak@huawei.com
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1569809658=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1569809658==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_D8e7vK12IzTJGV9TgT3gbg)"

This is a multi-part message in MIME format.

--Boundary_(ID_D8e7vK12IzTJGV9TgT3gbg)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi,

When the global unicast address with prefix 2 (ex: DADA::100/2) is given for
the interface, Mobile IPV6 anycast address corresponding to this should be
as below( RFC 2526).

 

 Format of Reserved Subnet Anycast Addresses:

 

   |              n bits            |    121-n bits  |   7 bits   |

  +---------------------------------+-----------.-------+------------ +

   |      subnet prefix         | 111..111111 | anycast ID |

  +---------------------------------+------------------+----------- -+

                                      |   interface identifier field  |

 

So MIP6 any cast address corresponding to this global unicast address
(DADA::100/2) will be 

FFFF:FFFF:FFFF:FFFF:FFFE as  the subnet prefix will 11 (prefix length is 2
only)

 

This  FFFF:FFFF:FFFF:FFFF:FFFE is a multicast address.

            

 

But as per RFC 3513 IPv6 Addressing Architecture,

 "Anycast addresses are allocated from the unicast address space, using any
of the defined unicast address formats"

 

            Can someone clarify this in-discrepancy?

 

 

Regards,

keshava

            


--Boundary_(ID_D8e7vK12IzTJGV9TgT3gbg)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>When the global unicast address with
prefix 2 (ex: DADA::100/2) is given for the interface, Mobile IPV6 anycast
address corresponding to this should be as below( RFC 2526).</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;Format
of Reserved Subnet Anycast Addresses:</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
n bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp; 121-n bits&nbsp; |&nbsp;&nbsp; 7 bits&nbsp;&nbsp; |</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;
+---------------------------------+-----------.-------+------------ +</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subnet
prefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 111..111111 | anycast
ID |</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;+---------------------------------+------------------+-----------
-+</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp; interface identifier field&nbsp; |</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>So MIP6 any cast address corresponding
to this global unicast address (DADA::100/2) will be </span></font></p>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>FFFF:FFFF:FFFF:FFFF:FFFE<font
color=blue><span style='color:blue'> </span></font></span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>as </span></font><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;the
subnet prefix will 11 (prefix length is 2 only)</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>This&nbsp; <b><span
style='font-weight:bold'>FFFF:FFFF:FFFF:FFFF:FFFE<font color=blue><span
style='color:blue'> </span></font>is a multicast address<font color=blue><span
style='color:blue'>.</span></font></span></b></span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-indent:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>But as per RFC 3513 IPv6 Addressing
Architecture,</span></font></p>

<p class=MsoNormal style='margin-left:.5in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&#8220;Anycast
addresses are allocated from the unicast address space, using any of the
defined unicast address formats<font color=navy><span style='color:navy'>&#8221;</span></font></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Can
someone clarify this in-discrepancy?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Regards,</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>keshava</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

</div>

</body>

</html>

--Boundary_(ID_D8e7vK12IzTJGV9TgT3gbg)--


--===============1569809658==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============1569809658==--




From mip6-bounces@ietf.org Fri May 06 22:08:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DUEkC-0007VG-Is; Fri, 06 May 2005 22:08:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DUCr4-0003kx-03; Fri, 06 May 2005 20:07:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24758;
	Fri, 6 May 2005 20:07:35 -0400 (EDT)
Received: from farside.isc.org ([204.152.187.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DUD5d-0002lg-QU; Fri, 06 May 2005 20:22:43 -0400
Received: from drugs.dv.isc.org (localhost [IPv6:::1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by farside.isc.org (Postfix) with ESMTP id F30F2677EF;
	Sat,  7 May 2005 00:07:25 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.13.1/8.13.1) with ESMTP id j4706UQr057192;
	Sat, 7 May 2005 10:06:40 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200505070006.j4706UQr057192@drugs.dv.isc.org>
To: keshavak@huawei.com
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Fri, 06 May 2005 18:48:32 +0530."
	<000001c5523e$1ab581c0$b504120a@china.huawei.com> 
Date: Sat, 07 May 2005 10:06:30 +1000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Fri, 06 May 2005 22:08:38 -0400
Cc: mip6@ietf.org, ipv6@ietf.org
Subject: [Mip6] Re: Anycast Address becoming Multicast address .... 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> Hi,
> 
> When the global unicast address with prefix 2 (ex: DADA::100/2) is given for
> the interface, Mobile IPV6 anycast address corresponding to this should be
> as below( RFC 2526).
> 
>  
> 
>  Format of Reserved Subnet Anycast Addresses:
> 
>  
> 
>    |              n bits            |    121-n bits  |   7 bits   |
> 
>   +---------------------------------+-----------.-------+------------ +
> 
>    |      subnet prefix         | 111..111111 | anycast ID |
> 
>   +---------------------------------+------------------+----------- -+
> 
>                                       |   interface identifier field  |
> 
>  
> 
> So MIP6 any cast address corresponding to this global unicast address
> (DADA::100/2) will be 
> 
> FFFF:FFFF:FFFF:FFFF:FFFE as  the subnet prefix will 11 (prefix length is 2
> only)
> 
>  
> 
> This  FFFF:FFFF:FFFF:FFFF:FFFE is a multicast address.
> 
>             
> 
>  
> 
> But as per RFC 3513 IPv6 Addressing Architecture,
> 
>  "Anycast addresses are allocated from the unicast address space, using any
> of the defined unicast address formats"
> 
>  
> 
>             Can someone clarify this in-discrepancy?
> 
>  
> 
>  
> 
> Regards,
> 
> keshava

 
	Well in 2373 the minimum prefix len was 3 for the above
	address.  Basically all the prefixes in 2373 has enough
	bits to distinguish them from a multicast address, i.e. the
	prefix contained atleast one "zero" bit.  They also contained
	enough infomation to distinguish it from a reserved address,
	i.e. one "one" bit.

	The simplest thing may be to say the minimum prefix length is 8.

	Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 10 13:06:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYC1-0003Z9-OG; Tue, 10 May 2005 13:06:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYBw-0003Wz-Ik; Tue, 10 May 2005 13:06:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16493;
	Tue, 10 May 2005 13:06:41 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DVYRI-0006HF-Hi; Tue, 10 May 2005 13:22:36 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DVYBv-0002Rg-Ms; Tue, 10 May 2005 13:06:43 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DVYBv-0002Rg-Ms@newodin.ietf.org>
Date: Tue, 10 May 2005 13:06:43 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org
Subject: [Mip6] Last Call: 'Mobile IPv6 Management Information Base' to
 Proposed Standard 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

The IESG has received a request from the Mobility for IPv6 WG to consider the 
following document:

- 'Mobile IPv6 Management Information Base '
   <draft-ietf-mip6-mipv6-mib-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-07.txt


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 10 13:08:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYDR-0004Bj-Gj; Tue, 10 May 2005 13:08:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYDN-00049b-B3; Tue, 10 May 2005 13:08:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16956;
	Tue, 10 May 2005 13:08:10 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DVYSj-0006PK-GW; Tue, 10 May 2005 13:24:05 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DVYDM-0002Xf-Pt; Tue, 10 May 2005 13:08:12 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DVYDM-0002Xf-Pt@newodin.ietf.org>
Date: Tue, 10 May 2005 13:08:12 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org
Subject: [Mip6] Last Call: 'Preconfigured Binding Management Keys for Mobile
 IPv6' to Proposed Standard 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

The IESG has received a request from the Mobility for IPv6 WG to consider the 
following document:

- 'Preconfigured Binding Management Keys for Mobile IPv6 '
   <draft-ietf-mip6-precfgkbm-01.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip6-precfgkbm-01.txt


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 10 13:27:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYWG-0002UV-5G; Tue, 10 May 2005 13:27:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVYWC-0002T5-4j; Tue, 10 May 2005 13:27:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22653;
	Tue, 10 May 2005 13:27:37 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DVYlY-0008Up-HQ; Tue, 10 May 2005 13:43:32 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DVYWB-0000co-LG; Tue, 10 May 2005 13:27:39 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DVYWB-0000co-LG@newodin.ietf.org>
Date: Tue, 10 May 2005 13:27:39 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org
Subject: [Mip6] UPDATED Last Call: 'Precomputable Binding Management Key Kbm
 for Mobile IPv6' to Proposed Standard 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

The IESG has received a request from the Mobility for IPv6 WG to consider the 
following document:

- 'Precomputable Binding Management Key Kbm for Mobile IPv6 '
   <draft-ietf-mip6-precfgkbm-01.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip6-precfgkbm-01.txt


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 11 06:07:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVo89-00043P-Rl; Wed, 11 May 2005 06:07:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVo86-00042p-N5; Wed, 11 May 2005 06:07:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18669;
	Wed, 11 May 2005 06:07:47 -0400 (EDT)
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DVoNa-00054V-MW; Wed, 11 May 2005 06:23:52 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IGB008KJLNXIW@szxga02-in.huawei.com>; Wed,
	11 May 2005 18:11:57 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IGB005NELNXTW@szxga02-in.huawei.com>; Wed,
	11 May 2005 18:11:57 +0800 (CST)
Received: from sachin1734 ([10.18.4.66])
	by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IGB00D1WLNRG1@szxml02-in.huawei.com>; Wed,
	11 May 2005 18:11:53 +0800 (CST)
Date: Wed, 11 May 2005 03:07:39 -0700
From: Sachin <sachind@huawei.com>
In-reply-to: <000001c5523e$1ab581c0$b504120a@china.huawei.com>
To: deering@cisco.com, ipv6@ietf.org, mip6@ietf.org, Majordomo@anarg.jp
Message-id: <000001c55611$44a82470$4204120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08156cf414e01129f6a937203576bf20
Cc: 
Subject: [Mip6] Issues Related to Mobile Anycast Address
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sachind@huawei.com
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2147307293=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2147307293==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_6RnR6Xgv+JueIBaBR8h4fg)"

This is a multi-part message in MIME format.

--Boundary_(ID_6RnR6Xgv+JueIBaBR8h4fg)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi,

 

Following are two issues related to Anycast can some one plz clarify on
same

 

First as raised by Keshava that anycast address corresponding to unicast
global address becoming multicast addresses, RFC has not put any
specific condition for prefix length, so as per RFC 3513 for the
following unassigned global addresses with prefix length less then 8 the
corresponding mip6 anycast address will be multicast

   Unassigned                            1110           1/16

   Unassigned                            1111 0         1/32

   Unassigned                            1111 10        1/64

   Unassigned                            1111 110       1/128

   Unassigned                            1111 1110 0    1/512

 

"RFC 3513

 

Allocation                            Prefix         Fraction of

                                         (binary)       Address Space

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

   Unassigned (see Note 1 below)         0000 0000      1/256

   Unassigned                            0000 0001      1/256

   Reserved for NSAP Allocation          0000 001       1/128 [RFC1888]

   Unassigned                            0000 01        1/64

   Unassigned                            0000 1         1/32

   Unassigned                            0001           1/16

   Global Unicast                        001            1/8   [RFC2374]

   Unassigned                            010            1/8

   Unassigned                            011            1/8

   Unassigned                            100            1/8

   Unassigned                            101            1/8

   Unassigned                            110            1/8

   Unassigned                            1110           1/16

   Unassigned                            1111 0         1/32

   Unassigned                            1111 10        1/64

   Unassigned                            1111 110       1/128

   Unassigned                            1111 1110 0    1/512

   Link-Local Unicast Addresses          1111 1110 10   1/1024

   Site-Local Unicast Addresses          1111 1110 11   1/1024

   Multicast Addresses                   1111 1111      1/256

 

"

2 The other issue is that for different prefix anycast address formed
can be same for example 

 

ipv6 address DDDD::FDF0:0:0:2/76

ipv6 address DDDD::2/64      

ipv6 address DDDD::FD00:0:0:2/72

 

MIP6 Anycast address

 

DDDD::FDFF:FFFF:FFFF:FFFE

 

 

Mobile nodes from these three different subnet; will generate same mip6
anycast address. So their home agent discovery reply may not be from
correct home network 

 

Kindly comment on this

 

Regards

Sachin

 

-----Original Message-----
From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On Behalf Of
Keshava Ayanur
Sent: Friday, May 06, 2005 6:19 AM
To: ipv6@ietf.org; mip6@ietf.org
Subject: [Mip6] Anycast Address becoming Multicast address ....

 

Hi,

When the global unicast address with prefix 2 (ex: DADA::100/2) is given
for the interface, Mobile IPV6 anycast address corresponding to this
should be as below( RFC 2526).

 

 Format of Reserved Subnet Anycast Addresses:

 

   |              n bits            |    121-n bits  |   7 bits   |

  +---------------------------------+-----------.-------+------------ +

   |      subnet prefix         | 111..111111 | anycast ID |

  +---------------------------------+------------------+----------- -+

                                      |   interface identifier field  |

 

So MIP6 any cast address corresponding to this global unicast address
(DADA::100/2) will be 

FFFF:FFFF:FFFF:FFFF:FFFE as  the subnet prefix will 11 (prefix length is
2 only)

 

This  FFFF:FFFF:FFFF:FFFF:FFFE is a multicast address.

            

 

But as per RFC 3513 IPv6 Addressing Architecture,

 "Anycast addresses are allocated from the unicast address space, using
any of the defined unicast address formats"

 

            Can someone clarify this in-discrepancy?

 

 

Regards,

keshava

            


--Boundary_(ID_6RnR6Xgv+JueIBaBR8h4fg)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Hi,</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Following are two issues related to Anycast can some
one plz clarify on same</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>First as raised by Keshava that anycast address
corresponding to unicast global address becoming multicast addresses, RFC has
not put any specific condition for prefix length, so as per RFC 3513 for the
following unassigned global addresses with prefix length less then 8 the
corresponding mip6 anycast address will be multicast</span></font></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp; </span></font></b><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/16</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/32</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/64</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/128</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 1110 0&nbsp;&nbsp;&nbsp; 1/512</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&#8220;RFC 3513</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Allocation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Prefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fraction of</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(binary)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address Space</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
-----------------------------------&nbsp;&nbsp;
--------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------------</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Unassigned (see
Note 1 below)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0000 0000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1/256</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0000 0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/256</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Reserved for
NSAP Allocation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0000
001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/128 [RFC1888]</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0000 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/64</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0000 1&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1/32</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/16</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Global Unicast&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1/8&nbsp;&nbsp; [RFC2374]</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
010&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/8</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
011&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1/8</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/8</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/8</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/8</span></font></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/16</span></font></b></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp;&nbsp; Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/32</span></font></b></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/64</span></font></b></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/128</span></font></b></p>

<p class=MsoNormal style='text-autospace:none'><b><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
font-weight:bold'>&nbsp;&nbsp;
Unassigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 1110 0&nbsp;&nbsp;&nbsp; 1/512</span></font></b></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Link-Local Unicast
Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1111 1110
10&nbsp;&nbsp; 1/1024</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Site-Local Unicast
Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1111 1110
11&nbsp;&nbsp; 1/1024</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Multicast
Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1111 1111&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/256</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&#8220;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>2 The other issue is that for
different prefix anycast address formed can be same for example </span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>ipv6 address
DDDD::FDF0:0:0:2/76</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>ipv6 address DDDD::2/64&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>ipv6 address
DDDD::FD00:0:0:2/72</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>MIP6 Anycast address</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face="Courier New"><span
style='font-size:9.0pt;font-family:"Courier New"'>DDDD::FDFF:FFFF:FFFF:FFFE</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Mobile nodes from these three different subnet; will
generate same mip6 anycast address. So their home agent discovery reply may not
be from correct home network </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Kindly comment on this</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Regards</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Sachin</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> mip6-bounces@ietf.org
[mailto:mip6-bounces@ietf.org] <b><span style='font-weight:bold'>On Behalf Of </span></b>Keshava
Ayanur<br>
<b><span style='font-weight:bold'>Sent:</span></b> </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Friday, May 06,
 2005</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'> </span></font><font size=2 face=Tahoma><span
 style='font-size:10.0pt;font-family:Tahoma'>6:19 AM</span></font><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><br>
<b><span style='font-weight:bold'>To:</span></b> ipv6@ietf.org; mip6@ietf.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Mip6] Anycast Address
becoming Multicast address ....</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Hi,</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>When the global unicast address with
prefix 2 (ex: DADA::100/2) is given for the interface, Mobile IPV6 anycast
address corresponding to this should be as below( RFC 2526).</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;Format
of Reserved Subnet Anycast Addresses:</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
n bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp; 121-n bits&nbsp; |&nbsp;&nbsp; 7 bits&nbsp;&nbsp; |</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;
+---------------------------------+-----------.-------+------------ +</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subnet
prefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 111..111111 | anycast
ID |</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;+---------------------------------+------------------+-----------
-+</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp; interface identifier field&nbsp; |</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>So MIP6 any cast address
corresponding to this global unicast address (DADA::100/2) will be </span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>FFFF:FFFF:FFFF:FFFF:FFFE<font
color=blue><span style='color:blue'> </span></font></span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>as &nbsp;the
subnet prefix will 11 (prefix length is 2 only)</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>This&nbsp; <b><span
style='font-weight:bold'>FFFF:FFFF:FFFF:FFFF:FFFE<font color=blue><span
style='color:blue'> </span></font>is a multicast address<font color=blue><span
style='color:blue'>.</span></font></span></b></span></font></p>

<p class=MsoNormal style='margin-left:1.0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:.5in'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>But as per RFC 3513
IPv6 Addressing Architecture,</span></font></p>

<p class=MsoNormal style='margin-left:1.0in;line-height:12.0pt;text-autospace:
none'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>&nbsp;&#8220;Anycast
addresses are allocated from the unicast address space, using any of the
defined unicast address formats<font color=navy><span style='color:navy'>&#8221;</span></font></span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Can someone clarify this in-discrepancy?</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Regards,</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>keshava</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></p>

</div>

</body>

</html>

--Boundary_(ID_6RnR6Xgv+JueIBaBR8h4fg)--


--===============2147307293==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============2147307293==--




From mip6-bounces@ietf.org Wed May 11 15:56:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DVxJK-0003Tb-Uf; Wed, 11 May 2005 15:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DVxJJ-0003TR-PE
	for mip6@megatron.ietf.org; Wed, 11 May 2005 15:56:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14663
	for <mip6@ietf.org>; Wed, 11 May 2005 15:55:57 -0400 (EDT)
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVxYo-0003O1-LR
	for mip6@ietf.org; Wed, 11 May 2005 16:12:06 -0400
Received: from ala-mail04.corp.ad.wrs.com (ala-mail04 [147.11.57.145])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA04808
	for <mip6@ietf.org>; Wed, 11 May 2005 12:55:32 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 May 2005 12:55:32 -0700
Message-ID: <FC51183DD7346347B77EEF5DC8655309E0A4BE@ala-mail04.corp.ad.wrs.com>
Thread-Topic: Mip6 Digest, Vol 13, Issue 7
Thread-Index: AcVWEfW2jUwTCDMHQ/KJBFT+JbyYEgAUJutQ
From: "Luo, Tong" <Tong.Luo@windriver.com>
To: <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] RE: Mip6 Digest, Vol 13, Issue 7
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

IPsec is a very important aspect of MIP6. Why there are no configurable
MIB variables for it?

Tong
=20

Date: Tue, 10 May 2005 13:06:43 -0400
From: The IESG <iesg-secretary@ietf.org>
Subject: [Mip6] Last Call: 'Mobile IPv6 Management Information Base'
	to Proposed Standard
To: IETF-Announce <ietf-announce@ietf.org>
Cc: mip6@ietf.org
Message-ID: <E1DVYBv-0002Rg-Ms@newodin.ietf.org>

The IESG has received a request from the Mobility for IPv6 WG to
consider the following document:

- 'Mobile IPv6 Management Information Base '
   <draft-ietf-mip6-mipv6-mib-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-07.txt





_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 12 08:14:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DWCaT-0001HV-GQ; Thu, 12 May 2005 08:14:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DVqrW-0003sJ-PZ
	for mip6@megatron.ietf.org; Wed, 11 May 2005 09:02:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01152
	for <mip6@ietf.org>; Wed, 11 May 2005 09:02:53 -0400 (EDT)
Received: from amber.ccs.neu.edu ([129.10.116.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVr73-0005fu-CQ
	for mip6@ietf.org; Wed, 11 May 2005 09:18:57 -0400
Received: from denali.ccs.neu.edu ([129.10.116.200])
	by amber.ccs.neu.edu with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
	(Exim 4.50) id 1DVqrT-0007PO-Co; Wed, 11 May 2005 09:02:51 -0400
Date: Wed, 11 May 2005 09:02:53 -0400 (EDT)
From: Guevara Noubir <noubir@ccs.neu.edu>
To: mip6@ietf.org
Message-ID: <Pine.GSO.4.58.0505110901520.27086@denali.ccs.neu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
X-Mailman-Approved-At: Thu, 12 May 2005 08:14:44 -0400
Subject: [Mip6] ACM Workshop on Wireless Security (WiSe 2005) 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



(Our apologies if you receive multiple copies of this CFP)


=============================================
ACM Workshop on Wireless Security (WiSe 2005)
=============================================
(in conjunction with ACM MobiCom 2005)

Location: Cologne, Germany

Sponsored by ACM SIGMOBILE (PENDING)

http://www.ee.washington.edu/research/nsl/wise2005

The workshop on Wireless Security will be held in conjunction with ACM
MobiCom 2005. The objective of this workshop is to bring together
researchers from research communities in wireless networking, security,
applied cryptography, and dependability; with the goal of fostering
interaction. With the proliferation of wireless networks, issues related
to secure and dependable operation of such networks are gaining
importance. Topics of interest include, but are not limited to:

- Key management in wireless/mobile environments
- Trust establishment
- Computationally efficient primitives
- Intrusion detection, detection of malicious behavior
- Revocation of malicious parties
- Secure PHY/MAC/routing protocols
- Secure location determination
- Denial of service
- User privacy, location privacy
- Anonymity, prevention of traffic analysis
- Dependable wireless networking
- Identity theft and phishing in mobile networks
- Charging in wireless networks
- Cooperation in wireless networks
- Vulnerability modeling
- Incentive-aware secure protocol design
- Jamming
- Monitoring and surveillance


Paper submission instructions:
------------------------------

Submission of papers based on work-in-progress is encouraged. Submitted
papers must not be previously published elsewhere or currently under
review for any other publication. Please direct any questions about the
paper submission process to the Program Co-Chairs.

All paper submissions will be handled electronically. Authors should
prepare a PostScript or Portable Document Format (PDF) version of their
paper.

Papers must meet the following restrictions: No longer than 10 pages
(single or double column); in font no smaller than 10 points; must fit
properly on US Letter-sized paper (8.5 inch x 11 inch) with reasonable
margins.


Awards:
-------

We gratefully acknowledge funding from the Center of Applied Cybersecurity
Research to sponsor two awards of $500 each: one for best paper and one
for best student paper.


Important dates
================
Paper submission deadline: June 10, 2005
Notification of acceptance: July 10, 2005
Camera-ready papers due: July 15, 2005
Workshop date: Aug 28 - Sept 2, 2005 (in conjunction with Mobicom 2005)


Workshop Co-Chairs:
-------------------
Markus Jakobsson, Indiana University at Bloomington (markus@indiana.edu)
Radha Poovendran, University of Washington (radha@ee.washington.edu)


Program committee:
------------------
Yair Amir, Johns Hopkins University
Farooq Anjum, Stevens Institute of Technology
Srdjan Capkun, Swiss Federal Institute of Technology (EPFL)
Yih-Chun, UC Berkeley
Brian DeCleene, Alphatech
Wenliang (Kevin) Du, Syracuse University
Rick Han, University of Colorado
Jean-Pierre Hubaux, Swiss Federal Institute of Technology (EPFL)
Jiejun Kong, UCLA
Wenke Lee, Georgia Institute of Technology
Mingyan Li, University of Washington
Catherine Meadows, Naval Research Laboratory
Peng Ning, North Carolina State University
Kaisa Nyberg, Nokia Research Center
Adrian Perrig, Carnegie Mellon University
Cliff Wang, Army Research Office
XiaoFeng Wang, Indiana University at Bloomington
Susanne Wetzel, Stevens Institute of Technology
Haitao Zheng, Microsoft Research
Ben Zhao, UCSB


Publicity Co-Chairs:
--------------------
Rick Han, University of Colarado
Guevara Noubir, Northeastern University
Ulrike Meyer Darmstadt University of Technology

Publication Chair:
------------------
Saad Biaz, Auburn University


Treasurer:
----------
Yongguang Zhang, HRL Labs and University of Texas-Austin


WiSe Steering Committee:
------------------------
Adrian Perrig, Carnegie Mellon University
Douglas Maughan, DHS / HSARPA
Nitin Vaidya, University of Illinois

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 12 10:20:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DWEYW-0006Nd-Cu; Thu, 12 May 2005 10:20:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DWEYU-0006NO-Gt
	for mip6@megatron.ietf.org; Thu, 12 May 2005 10:20:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28266
	for <mip6@ietf.org>; Thu, 12 May 2005 10:20:48 -0400 (EDT)
Received: from waga.cysol.co.jp ([210.233.3.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DWEoC-00032E-VY
	for mip6@ietf.org; Thu, 12 May 2005 10:37:06 -0400
Received: from aso.priv.cysol.co.jp (aso.priv.cysol.co.jp [192.168.0.15])
	by waga.cysol.co.jp (8.12.9/8.12.9) with ESMTP id j4CEKPCw026885;
	Thu, 12 May 2005 23:20:25 +0900 (JST)
Received: from [127.0.0.1] (kiras7.priv.cysol.co.jp [192.168.0.157])
	by aso.priv.cysol.co.jp (8.12.9/8.12.9) with ESMTP id j4CEKCIb002301;
	Thu, 12 May 2005 23:20:25 +0900 (JST)
Message-ID: <4283661A.6060106@cysols.com>
Date: Thu, 12 May 2005 23:20:10 +0900
From: Glenn Mansfield Keeni <glenn@cysols.com>
Organization: Cyber Solutions Inc.
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Luo, Tong" <Tong.Luo@windriver.com>
Subject: Re: [Mip6] RE: Mip6 Digest, Vol 13, Issue 7
References: <FC51183DD7346347B77EEF5DC8655309E0A4BE@ala-mail04.corp.ad.wrs.com>
In-Reply-To: <FC51183DD7346347B77EEF5DC8655309E0A4BE@ala-mail04.corp.ad.wrs.com>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,
Luo, Tong wrote:
> Hi,
> 
> IPsec is a very important aspect of MIP6. Why there are no configurable
> MIB variables for it?
This did come up at the early stages of the design discussion.  4. MIB Design
in the draft says-

   "... It is envisaged
   that wherever possible existing MIBS will be used (e.g. IPSec MIB,
   Neighbor Discovery MIB, Tunnel MIB.) for monitor and control of MIPv6
   entities."

Glenn

> 
> Tong
>  
> 
> Date: Tue, 10 May 2005 13:06:43 -0400
> From: The IESG <iesg-secretary@ietf.org>
> Subject: [Mip6] Last Call: 'Mobile IPv6 Management Information Base'
> 	to Proposed Standard
> To: IETF-Announce <ietf-announce@ietf.org>
> Cc: mip6@ietf.org
> Message-ID: <E1DVYBv-0002Rg-Ms@newodin.ietf.org>
> 
> The IESG has received a request from the Mobility for IPv6 WG to
> consider the following document:
> 
> - 'Mobile IPv6 Management Information Base '
>    <draft-ietf-mip6-mipv6-mib-07.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-07.txt
> 
> 
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 12 11:01:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DWFC0-0004M9-Nq; Thu, 12 May 2005 11:01:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DWFBy-0004M4-Rm
	for mip6@megatron.ietf.org; Thu, 12 May 2005 11:01:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00702
	for <mip6@ietf.org>; Thu, 12 May 2005 11:01:36 -0400 (EDT)
Received: from unknown-1-11.wrs.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DWFRh-0003vG-QQ
	for mip6@ietf.org; Thu, 12 May 2005 11:17:55 -0400
Received: from ala-mail04.corp.ad.wrs.com (ala-mail04 [147.11.57.145])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA09881;
	Thu, 12 May 2005 08:01:13 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: Mip6 Digest, Vol 13, Issue 7
Date: Thu, 12 May 2005 08:01:12 -0700
Message-ID: <FC51183DD7346347B77EEF5DC8655309E0A7F0@ala-mail04.corp.ad.wrs.com>
Thread-Topic: [Mip6] RE: Mip6 Digest, Vol 13, Issue 7
Thread-Index: AcVW/gDHzMCCtt8OSE2SksmAlUPVCAABIvxA
From: "Luo, Tong" <Tong.Luo@windriver.com>
To: "Glenn Mansfield Keeni" <glenn@cysols.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Glenn,

Thank you for the clarification. Perhaps it will be very useful and
helpful to identify those existing MIBS (IPSec, ND, Tunnel, etc) in the
draft, and add the relative MIB RFCs/drafts to the references.

Tong =20

-----Original Message-----
From: Glenn Mansfield Keeni [mailto:glenn@cysols.com]=20
Sent: Thursday, May 12, 2005 10:20 AM
To: Luo, Tong
Cc: mip6@ietf.org
Subject: Re: [Mip6] RE: Mip6 Digest, Vol 13, Issue 7

Hi,
Luo, Tong wrote:
> Hi,
>=20
> IPsec is a very important aspect of MIP6. Why there are no=20
> configurable MIB variables for it?
This did come up at the early stages of the design discussion.  4. MIB
Design in the draft says-

   "... It is envisaged
   that wherever possible existing MIBS will be used (e.g. IPSec MIB,
   Neighbor Discovery MIB, Tunnel MIB.) for monitor and control of MIPv6
   entities."

Glenn

>=20
> Tong
> =20
>=20
> Date: Tue, 10 May 2005 13:06:43 -0400
> From: The IESG <iesg-secretary@ietf.org>
> Subject: [Mip6] Last Call: 'Mobile IPv6 Management Information Base'
> 	to Proposed Standard
> To: IETF-Announce <ietf-announce@ietf.org>
> Cc: mip6@ietf.org
> Message-ID: <E1DVYBv-0002Rg-Ms@newodin.ietf.org>
>=20
> The IESG has received a request from the Mobility for IPv6 WG to=20
> consider the following document:
>=20
> - 'Mobile IPv6 Management Information Base '
>    <draft-ietf-mip6-mipv6-mib-07.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action.  Please send any comments to the=20
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-05-24.
>=20
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-07.txt
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sat May 14 13:01:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DX013-0004xT-96; Sat, 14 May 2005 13:01:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DWYw7-000598-K7
	for mip6@megatron.ietf.org; Fri, 13 May 2005 08:06:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07842
	for <mip6@ietf.org>; Fri, 13 May 2005 08:06:34 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DWZC1-00049K-2y
	for mip6@ietf.org; Fri, 13 May 2005 08:23:03 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 366816 for mip6@ietf.org;
	Fri, 13 May 2005 08:02:19 -0400
Mime-Version: 1.0
Message-Id: <p06200711beaa46634c08@[10.0.0.171]>
Date: Fri, 13 May 2005 08:05:19 -0400
To: mip6@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
X-Mailman-Approved-At: Sat, 14 May 2005 13:01:28 -0400
Subject: [Mip6] draft-ietf-mip6-mn-ident-option-02.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hi All,

This is a follow-up message regarding draft-ietf-mip6-mn-ident-option-02.txt.

I have attached the IESG review comments on this document.  The 
comments marked "discuss" are blocking issues that need to be 
resolved before the document will be approved for publication.  There 
are also non-blocking comments (marked "comment") that should be 
considered by the WG but will not block publication.

There was one "discuss" registered on this document (by Sam Hartman) 
that should probably be discussed and resolved by the WG.

Raj and Gopal, do you know when we should expect an update to the 
document that addresses this concern and fixes the other minor issues 
included in the comments?

Thanks,
Margaret

Sam Hartman:
Discuss:
[2005-03-01] This document fails to explain how the identity option 
interacts with
the IKE identity payloads or really how it interacts at all with the
base MIPV6 spec.

This needs to be explained.  IT may have been the intent that this
option not be used with base MIPV6 but for example only used with the
authentication option and other extensions.  If so, that needs to be
explained and there needs to be at least one such use that is
standards track if this is going to be published as standards track.


In addition, this specification does not make any particular form of
the identity option mandatory to implement.  To create interoperable
implementations, this specification needs to
specify a mandatory to implement form of the option.

Scott Hollenbeck:
Comment:
[2005-02-25] RFC 2119 should be added as a normative reference.  It's 
mentioned in section 2, but not cited.

Russ Housley:
Comment:
[2005-03-01]
   In the Abstract: s/Mobile IP6/Mobile IPv6/

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sun May 15 16:41:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXPvb-0005aC-Rx; Sun, 15 May 2005 16:41:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXPvZ-0005a7-UJ
	for mip6@megatron.ietf.org; Sun, 15 May 2005 16:41:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07746
	for <mip6@ietf.org>; Sun, 15 May 2005 16:41:31 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXQBy-0005X1-8i
	for mip6@ietf.org; Sun, 15 May 2005 16:58:31 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id D619089879;
	Sun, 15 May 2005 23:41:09 +0300 (EEST)
Message-ID: <4287B3F0.600@kolumbus.fi>
Date: Sun, 15 May 2005 23:41:20 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org, Charlie P <charliep@iprg.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Mip6] mip6-precfgkbm-01.txt review
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Charlie,

As a part of ongoing last call I have reviewed this draft.

Overall:

- This is a solid draft and, with some modifications, should
  move forward. Its never been my big favorite due to its
  limited applicability, but it is also very efficient where it
  works. More efficient than pretty much anything else
  anyone has come up with in this space, so...

- I found a few areas where you could give more information
  and context to the reader, e.g., explaining the difference
  and impacts of using this vs. RFC 3775 mechanisms.

- I'm not too happy about all the details in the applicability
  statement text, but I have provided alternative suggestions.

Substantial:

- The title, "Precomputable Binding Management Key Kbm
  for Mobile IPv6" is correct, but at least to me, also not very
  descriptive from the point of view of what people want from
  this. What I think most people are interested to hear about
  is that if you have a preconfigured secret then you can use
  this draft for an efficient form of RO security.

  Suggestion: change title to "Securing Mobile IPv6 Route
  Optimization Using a Shared Key".

- Similarly, I think the introduction could say a few words
  to the reader on how this is different wrt base route
  optimization security. Suggested text below.

  "0. Introduction

       This specification introduces an alternative,
       low-latency security mechanism for protecting
       signaling related to the route optimization in
       Mobile IPv6. The default mechanism specified
       in [1] uses a periodic return routability test
       to verify both the "right" of the mobile node
       to a use a specific home address,  as well as
       the validity of the claimed care-of address.
       This mechanism requires no configuration and
       no trusted entities beyond the mobile node's
       home agent.

       The mechanism specified in this specification,
       however, requires the configuration of a shared
       secret between mobile node and its correspondent
       node. As a result, messages relating to the
       routability tests can be omitted, leading to significantly
       smaller latency. In addition, the right to use a specific
       address is assured in a stronger manner than
       in [1]. On the other hand, the applicability
       of this mechanisms is limited due to the need
       for pre-configuration. This mechanism is also
       limited to use only in scenarios where mobile nodes
       can be trusted to not misbehave, as the validity
       of the claimed care-of addresses is not verified."

- Details about replay protection. The draft says

>    For this reason, a correspondent
>    node that uses a precomputable Kbm also MUST keep track of the most
>    recent value of the Sequence Number field of Binding Update messages
>    using the precomputable Kbm value.

  I would be interested in knowing whether this MUST requires
  you to keep the sequence numbers in nvm storage or if the
  intent is to only require this on a per-boot basis. The draft
  might benefit from slight text changes depending on the
  answer to this question. For instance, per-boot semantics
  are OK then s/MUST/SHOULD/ might be appropriate. Otherwise
  the text should probably be explicit about the requirement
  to do this with nvm storage.

- Behavior in a misconfiguration or delayed configuration
  cases. The draft says...

>    The Nonce Indices option SHOULD NOT
>    be present.  If it is present, the nonce indices supplied MAY be
>    ignored and are not included as part of the calculation for the
>    authentication data, which is to be carried exactly as specified
>    in [1].

  However, this implies that if the preshared secret configuration
  is entered to the correspondent node but not yet to the mobile
  node, both preshared approach and base Mipv6 procedure will
  fail.

  I think this is in fact correct, due to the need to avoid
  bidding down attacks to base mechanism. But this
  could be explicitly stated somewhere, maybe in Section 3.

- Requirements for assignment of keys. The draft says:

>     -  the method of assignment for keys between the correspondent node
>        and mobile node results in a stronger security association than
>        what can be provided by the Return Routability procedure.

  This seems a bit weak, imho. It seems to imply that there
  are different methods to assigning the keys and we are not
  being told what they are. I would rather simply require that
  there must be per-mobile node preconfiguration of the
  required data (and I see that in Section 3 you already
  prohibited group keys, good...).

  This would also make it less likely that someone misuses this
  draft in ways it was not intended to be used.

- Nits on applicability stament. The draft says:

>     -  diagnostic procedures
>     -  software development and testing

  I would delete these. Of course anything can be
  used for diagnostics.

- Overall applicability text. Given the above comments,
  I wanted to see if I could come up with some suggested
  text. Here's my attempt:

   "This mechanism is useful in the specific scenario where the following
   conditions are all met:

   -   Mobile node and correspondent node are administered within
       the same domain.

   -   The correspondent node has good reason to trust the actions
       of the mobile node. In particular, the correspondent node
       needs to be certain that the mobile node will not launch
       flooding attacks against a third party as described in
       [2, draft-ietf-mip6-ro-sec].

   -   The configuration effort related to this mechanism
       is acceptable.

   -   There is a desire to take advantage of higher
       efficiency or greater assurance with regards to
       the correctness of the home address offered via
       this mechanism.

   Generally speaking, the required level of trust that the
   correspondent node needs for enabling a precomputable Kbm with a
   mobile node is more often found within relatively small, closed
   groups of users who are personally familiar with each other, or who
   have some external basis for establishing trustworthy interactions.
   A typical example scenario where this mechanism is applicable is
   within a corporation, or between specific users. Application in the
   general Internet use is typically not possible due to the
   configuration effort. Application at a public network operator
   is typically not possible due to requirements placed on the
   trustworthiness of mobile nodes."

- Is there any change wrt the lifetime of bindings created
  through this mechanism vs. RFC 3775? Seems like they
  could be higher.

Editorial:

- Citations

>    The first citation is normative, and the second citation is
>    informative only.

   I'd prefer separate lists, most I-D tools should generate
   them. Don't worry about this if your tool has trouble,
   however.

- Missing space?

> abovementioned

- Change

> very, very

  to just "very"

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 15:02:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXkrL-00071Q-Lm; Mon, 16 May 2005 15:02:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXkrK-00071L-14
	for mip6@megatron.ietf.org; Mon, 16 May 2005 15:02:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24299
	for <mip6@ietf.org>; Mon, 16 May 2005 15:02:30 -0400 (EDT)
Received: from e32.co.us.ibm.com ([32.97.110.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXl7s-0000TZ-Lw
	for mip6@ietf.org; Mon, 16 May 2005 15:19:41 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com
	[9.17.195.11])
	by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j4GJ2K0c212222
	for <mip6@ietf.org>; Mon, 16 May 2005 15:02:20 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j4GJ2KdV076938 for <mip6@ietf.org>; Mon, 16 May 2005 13:02:20 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id
	j4GJ2K7q016200 for <mip6@ietf.org>; Mon, 16 May 2005 13:02:20 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17])
	by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	j4GJ2KJv016168; Mon, 16 May 2005 13:02:20 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1])
	by rotala.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j4GJ2IO4019405; 
	Mon, 16 May 2005 15:02:18 -0400
Message-Id: <200505161902.j4GJ2IO4019405@rotala.raleigh.ibm.com>
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] mip6-precfgkbm-01.txt review 
In-Reply-To: Message from jari.arkko@kolumbus.fi
	of "Sun, 15 May 2005 23:41:20 +0300." <4287B3F0.600@kolumbus.fi> 
Date: Mon, 16 May 2005 15:02:18 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: mip6@ietf.org, Charlie P <charliep@iprg.nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Thanks Jari for the review.

Some followup on your comments (I've just read the document as well).

> - The title, "Precomputable Binding Management Key Kbm
>   for Mobile IPv6" is correct, but at least to me, also not very
>   descriptive from the point of view of what people want from
>   this. What I think most people are interested to hear about
>   is that if you have a preconfigured secret then you can use
>   this draft for an efficient form of RO security.

>   Suggestion: change title to "Securing Mobile IPv6 Route
>   Optimization Using a Shared Key".

I'd go a bit further and add "static" or "pre-configured" to "Shared
Key". Or is the former assumed when the term "shared key" is used?

> - Similarly, I think the introduction could say a few words
>   to the reader on how this is different wrt base route
>   optimization security. Suggested text below.

I definitely agree.

>   "0. Introduction

>        This specification introduces an alternative, low-latency
>        security mechanism for protecting signaling related to the
>        route optimization in Mobile IPv6. The default mechanism
>        specified in [1] uses a periodic return routability test to
>        verify both the "right" of the mobile node to a use a
>        specific home address, as well as the validity of the claimed
>        care-of address.  This mechanism requires no configuration
>        and no trusted entities beyond the mobile node's home agent.

>        The mechanism specified in this specification, however,
>        requires the configuration of a shared secret between mobile
>        node and its correspondent node. As a result, messages
>        relating to the routability tests can be omitted, leading to
>        significantly smaller latency. In addition, the right to use
>        a specific address is assured in a stronger manner than in
>        [1]. On the other hand, the applicability of this mechanisms
>        is limited due to the need for pre-configuration. This
>        mechanism is also limited to use only in scenarios where
>        mobile nodes can be trusted to not misbehave, as the validity
>        of the claimed care-of addresses is not verified."

I think the above is good, and it would have saved me some thinking
had I read it before reviewing the document!

Actually, I view that last part of the above as quite significant.
There may also be problem related to broken implementations and such,
if a CN has a binding cache entry with a long time out that is no
longer correct (e.g., a COA address has been assigned to another
node).

Think also about a hacked cell phone that is able to do a DOS attack
on a specific server/host pair.

> - Overall applicability text. Given the above comments,
>   I wanted to see if I could come up with some suggested
>   text. Here's my attempt:

>    "This mechanism is useful in the specific scenario where the following
>    conditions are all met:

>    -   Mobile node and correspondent node are administered within
>        the same domain.

>    -   The correspondent node has good reason to trust the actions
>        of the mobile node. In particular, the correspondent node
>        needs to be certain that the mobile node will not launch
>        flooding attacks against a third party as described in
>        [2, draft-ietf-mip6-ro-sec].

>    -   The configuration effort related to this mechanism
>        is acceptable.

>    -   There is a desire to take advantage of higher
>        efficiency or greater assurance with regards to
>        the correctness of the home address offered via
>        this mechanism.

>    Generally speaking, the required level of trust that the
>    correspondent node needs for enabling a precomputable Kbm with a
>    mobile node is more often found within relatively small, closed
>    groups of users who are personally familiar with each other, or who
>    have some external basis for establishing trustworthy interactions.
>    A typical example scenario where this mechanism is applicable is
>    within a corporation, or between specific users. Application in the
>    general Internet use is typically not possible due to the
>    configuration effort. Application at a public network operator
>    is typically not possible due to requirements placed on the
>    trustworthiness of mobile nodes."

This (IMO limited) applicability makes me wonder if we should publish
this as experimental rather than standards track.

Thomas

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 15:02:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXkrg-00073R-4Z; Mon, 16 May 2005 15:02:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXkre-00073M-2P
	for mip6@megatron.ietf.org; Mon, 16 May 2005 15:02:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24319
	for <mip6@ietf.org>; Mon, 16 May 2005 15:02:52 -0400 (EDT)
Received: from e5.ny.us.ibm.com ([32.97.182.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXl8F-0000UG-4b
	for mip6@ietf.org; Mon, 16 May 2005 15:20:03 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e5.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j4GJ2ifn005963
	for <mip6@ietf.org>; Mon, 16 May 2005 15:02:44 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j4GJ2iV8144384 for <mip6@ietf.org>; Mon, 16 May 2005 15:02:44 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1])
	by d01av04.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j4GJ2i5N009679
	for <mip6@ietf.org>; Mon, 16 May 2005 15:02:44 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17])
	by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j4GJ2hVL009635; 
	Mon, 16 May 2005 15:02:44 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1])
	by rotala.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j4GJ2hcA019412; 
	Mon, 16 May 2005 15:02:43 -0400
Message-Id: <200505161902.j4GJ2hcA019412@rotala.raleigh.ibm.com>
To: mip6@ietf.org, Charlie P <charliep@iprg.nokia.com>
Date: Mon, 16 May 2005 15:02:43 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: 
Subject: [Mip6] LC review of draft-ietf-mip6-precfgkbm-01.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi.

I've also reviewed this document in response to the IETF LC.

General comment. This document really needs another pass from an
editorial perspective in the sense of being understandable to a
general reader who doesn't already know all about this technology.
The document needs to have more text providing background,
applicability, context, etc. Morever, for someone to do a security
analysis, I suspect there needs to be more background context to
understand what is being proposed and why. E.g., who is assumed to
have this pre-configured info, and how/when do they use it? (Don't
assume that a reader of this document has just read RFC 3775 and is
familiar with all its details!)

I don't think a lot of work is needed here, but a pass needs to be
made with an eye towards making it more understandable to a general
reader is in order.

Personally, I'm not a big fan of this, as I believe it has rather
limited applicability and does not scale. That is, a CN needs per-MN
configuration information. Where will this be useful in practice? Not
in large deployments, I suspect. But in small deployments, I have to
wonder if this assumption actually plays out:

> 2. Applicability Statement
> 
>    Preconfigured shared keys (such as Kcn) between a mobile node and a
>    correspondent node are useful in several specific scenarios:
> 
>     -  mobile node and correspondent node are administered within the
>        same domain, and the correspondent node has good reason to trust
>        the actions of the mobile node

That is, in small deployments that HA and CN may well end up being
topologically near each other (e.g., located in the same region), in
which case the triangular routing isn't a big problem performance
wise. Where you you really want RO to work well is when the MN and CN
are topologically close to each other, but the HA is far away.

I think the applicability statement should explicitely point out that
per-MN configuration is needed on the CN, and part of the
applicability is environments where this is deemed acceptable.

Abstract  really needs beefing up.

Document would benefit from an introduction section targetted towards
a more general reader. As it is, it just starts off with details.

>    When a Binding Update is to be authenticated using such a
>    precomputable binding key (Kbm), the Binding Authorization Data
>    suboption MUST be present.  The Nonce Indices option SHOULD NOT
>    be present.  If it is present, the nonce indices supplied MAY be
>    ignored and are not included as part of the calculation for the
>    authentication data, which is to be carried exactly as specified
>    in [1].

Seem odd that nonce indicies "SHOULD NOT" be present, but upon receipt
it is only a "MAY" that ie be ignorred. Seems like the default would
be to ignore them, since they aren't supposed to be included. Or, if
they are included, do you really want to say they need to be processed
as defined in the base MIPv6 spec? 

Also why are they not covered by the authentication data? Is this
consistent with the base spec? And does it have any security
implications?

>     -  the correspondent node has some guarantee that the mobile node
>        will behave properly (perhaps by contractual agreement)

I must not understand something here. I read the above as saying that
this draft introduces vulnerabiilties not present in the base MIPv6
space, but that those vulnerabilities are acceptable because the MN
and CN are "are under contract, so MN won't be bad." Am I
understanding this correctly?

>     -  diagnostic procedures
> 
>     -  software development and testing

I don't understand these. Are there any examples (and if so, include
them in the document)

Question: when are these extensions used? E.g., what happens if MN has
them configured but CN does not (or vice versa)? Is there a fallback?
is there negotiation? Do things still work?

>    are under the same administration.  The return routability procedure
>    is RECOMMENDED for all general use and MUST be the default, unless
>    the user explicitly overrides this by entering the abovementioned
>    preconfigured data for a particular peer.

Which user? On the MN? on the CN? both?  That is, does the MN (not the
CN) choose when to enable this? How does the CN know which to use?

>    protected against reboots.  If the mobile node were to send a fresh
>    Binding Update to its correspondent node every hour, 24 hours a day,
>    every day of the year, and utilize the same care-of address every
>    time, this would require changing keys every 7 years.  Even if the

Aren't these numbers disingenious? I.e., isn't the timeout associated
with BUs on the order of only a few minutes, and much less than one
hour?

(well, later the document hints that longer lieftimes might be in
use...)

>    There is no upper bound on the lifetime defined for the precomputable
>    Kbm.  As noted, the key is very, very likely to be quite secure
>    over the lifetime of the security association and usefulness of
>    applications between a mobile node and correspondent node that fit
>    the terms specified in section 2.

The document really needs more text about lifetimes. For one thing, it
seems like bad things will happen of the MN and CN have different
ideas of what the lifetime should be.  What does this document
_recommend_? Shouldn't the lifetimes be part of the configuration?
Or???

References need updating.

Thomas

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 15:54:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXlf9-0003V0-A6; Mon, 16 May 2005 15:54:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXlf6-0003UN-Uk
	for mip6@megatron.ietf.org; Mon, 16 May 2005 15:54:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03583
	for <mip6@ietf.org>; Mon, 16 May 2005 15:53:58 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXlvi-0003nc-4j
	for mip6@ietf.org; Mon, 16 May 2005 16:11:10 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j4GJMgU10484;
	Mon, 16 May 2005 12:22:42 -0700
X-mProtect: <200505161922> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdR9pvzX; Mon, 16 May 2005 12:22:40 PDT
Message-ID: <4288FA40.4645F8C2@iprg.nokia.com>
Date: Mon, 16 May 2005 12:53:36 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
References: <4287B3F0.600@kolumbus.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
Subject: [Mip6] Re: mip6-precfgkbm-01.txt review
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello Jari,

Jari Arkko wrote:

> - The title, "Precomputable Binding Management Key Kbm
>   for Mobile IPv6" is correct, but at least to me, also not very
>   descriptive from the point of view of what people want from
>   this. What I think most people are interested to hear about
>   is that if you have a preconfigured secret then you can use
>   this draft for an efficient form of RO security.
> 
>   Suggestion: change title to "Securing Mobile IPv6 Route
>   Optimization Using a Shared Key".

O.K. with me, if no one else objects.

> - Similarly, I think the introduction could say a few words
>   to the reader on how this is different wrt base route
>   optimization security. Suggested text below.
> 
>   "0. Introduction
> 
>        This specification introduces an alternative,
>        low-latency security mechanism for protecting
>        signaling related to the route optimization in
>        Mobile IPv6. The default mechanism specified
>        in [1] uses a periodic return routability test
>        to verify both the "right" of the mobile node
>        to a use a specific home address,  as well as
>        the validity of the claimed care-of address.
>        This mechanism requires no configuration and
>        no trusted entities beyond the mobile node's
>        home agent.
> 
>        The mechanism specified in this specification,
>        however, requires the configuration of a shared
>        secret between mobile node and its correspondent
>        node. As a result, messages relating to the
>        routability tests can be omitted, leading to significantly
>        smaller latency. In addition, the right to use a specific
>        address is assured in a stronger manner than
>        in [1]. On the other hand, the applicability
>        of this mechanisms is limited due to the need
>        for pre-configuration. This mechanism is also
>        limited to use only in scenarios where mobile nodes
>        can be trusted to not misbehave, as the validity
>        of the claimed care-of addresses is not verified."

This is all O.K. with me, and I'm happy to use it.

> - Details about replay protection. The draft says
> 
> >    For this reason, a correspondent
> >    node that uses a precomputable Kbm also MUST keep track of the most
> >    recent value of the Sequence Number field of Binding Update messages
> >    using the precomputable Kbm value.
> 
>   I would be interested in knowing whether this MUST requires
>   you to keep the sequence numbers in nvm storage or if the
>   intent is to only require this on a per-boot basis. The draft
>   might benefit from slight text changes depending on the
>   answer to this question. For instance, per-boot semantics
>   are OK then s/MUST/SHOULD/ might be appropriate. Otherwise
>   the text should probably be explicit about the requirement
>   to do this with nvm storage.

The mobile device ought to avoid re-using old sequence
numbers, and the best way I know of is to store them across
reboots.  I think that "SHOULD" is O.K., as long as designers
are aware of the downside.  That is, if the sequence number
is not stored, then:
- a new key would have to be configured at both devices, or
- the correspondent node would reject future binding updates, or
- replays would be possible.

> - Behavior in a misconfiguration or delayed configuration
>   cases. The draft says...
> 
> >    The Nonce Indices option SHOULD NOT
> >    be present.  If it is present, the nonce indices supplied MAY be
> >    ignored and are not included as part of the calculation for the
> >    authentication data, which is to be carried exactly as specified
> >    in [1].
> 
>   However, this implies that if the preshared secret configuration
>   is entered to the correspondent node but not yet to the mobile
>   node, both preshared approach and base Mipv6 procedure will
>   fail.
> 
>   I think this is in fact correct, due to the need to avoid
>   bidding down attacks to base mechanism. But this
>   could be explicitly stated somewhere, maybe in Section 3.

Do you mean that the draft ought to point out what
happens if the correspondent node is not yet configured?
I could just use your paragraph for that...

> - Requirements for assignment of keys. The draft says:
> 
> >     -  the method of assignment for keys between the correspondent node
> >        and mobile node results in a stronger security association than
> >        what can be provided by the Return Routability procedure.
> 
>   This seems a bit weak, imho. It seems to imply that there
>   are different methods to assigning the keys and we are not
>   being told what they are.

Well, this is exactly right, though.  Why is it "weak"?
Would you prefer that I omit this bullet?

?                     I would rather simply require that
>   there must be per-mobile node preconfiguration of the
>   required data (and I see that in Section 3 you already
>   prohibited group keys, good...).

The draft already does say this in section 3:

   A mobile node MUST use a different value for Kcn for each node in
   its Binding Update List, and a correspondent node MUST ensure that
   every mobile node uses a different value of Kcn. 

Does it need more?


> - Nits on applicability stament. The draft says:
> 
> >     -  diagnostic procedures
> >     -  software development and testing
> 
>   I would delete these. Of course anything can be
>   used for diagnostics.

I can delete them, but I don't agree with your statement!

> - Overall applicability text. Given the above comments,
>   I wanted to see if I could come up with some suggested
>   text. Here's my attempt:
> 
>    "This mechanism is useful in the specific scenario where the following
>    conditions are all met:
> 
>    -   Mobile node and correspondent node are administered within
>        the same domain.
> 
>    -   The correspondent node has good reason to trust the actions
>        of the mobile node. In particular, the correspondent node
>        needs to be certain that the mobile node will not launch
>        flooding attacks against a third party as described in
>        [2, draft-ietf-mip6-ro-sec].
> 
>    -   The configuration effort related to this mechanism
>        is acceptable.
> 
>    -   There is a desire to take advantage of higher
>        efficiency or greater assurance with regards to
>        the correctness of the home address offered via
>        this mechanism.
> 
>    Generally speaking, the required level of trust that the
>    correspondent node needs for enabling a precomputable Kbm with a
>    mobile node is more often found within relatively small, closed
>    groups of users who are personally familiar with each other, or who
>    have some external basis for establishing trustworthy interactions.
>    A typical example scenario where this mechanism is applicable is
>    within a corporation, or between specific users. Application in the
>    general Internet use is typically not possible due to the
>    configuration effort. Application at a public network operator
>    is typically not possible due to requirements placed on the
>    trustworthiness of mobile nodes."

This is fine with me.  I can replace section 2 in
its entirety by this text.


> - Is there any change wrt the lifetime of bindings created
>   through this mechanism vs. RFC 3775? Seems like they
>   could be higher.

The idea is that binding lifetimes can be a lot higher.
The vulnerabilities (small as they are) associated with
return routability are not present.

> - Missing space?
> 
> > abovementioned

This is a word.  Do you prefer having two words instead?

> - Change
> 
> > very, very
> 
>   to just "very"

O.K., but I also think that
"very, very" is correct.

Regards,
Charlie P.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 16:07:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXlsC-0003nP-Ez; Mon, 16 May 2005 16:07:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXls8-0003h1-Pw
	for mip6@megatron.ietf.org; Mon, 16 May 2005 16:07:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09497
	for <mip6@ietf.org>; Mon, 16 May 2005 16:07:26 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXm8g-0005ve-VG
	for mip6@ietf.org; Mon, 16 May 2005 16:24:36 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j4GJa7x03854;
	Mon, 16 May 2005 12:36:07 -0700
X-mProtect: <200505161936> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdBFDYPf; Mon, 16 May 2005 12:36:05 PDT
Message-ID: <4288FD65.44697D5@iprg.nokia.com>
Date: Mon, 16 May 2005 13:07:01 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [Mip6] mip6-precfgkbm-01.txt review
References: <200505161902.j4GJ2IO4019405@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello Thomas,

Thomas Narten wrote:

> I'd go a bit further and add "static" or "pre-configured" to "Shared
> Key". Or is the former assumed when the term "shared key" is used?

O.K.  "Shared key" does NOT imply preconfigured -- for instance,
AAA can distribute shared keys.

> Actually, I view that last part of the above as quite significant.
> There may also be problem related to broken implementations and such,
> if a CN has a binding cache entry with a long time out that is no
> longer correct (e.g., a COA address has been assigned to another
> node).

This seems to be a low-probability event in IPv6.

...

> >    Generally speaking, the required level of trust that the
> >    correspondent node needs for enabling a precomputable Kbm with a
> >    mobile node is more often found within relatively small, closed
> >    groups of users who are personally familiar with each other, or who
> >    have some external basis for establishing trustworthy interactions.
> >    A typical example scenario where this mechanism is applicable is
> >    within a corporation, or between specific users. Application in the
> >    general Internet use is typically not possible due to the
> >    configuration effort. Application at a public network operator
> >    is typically not possible due to requirements placed on the
> >    trustworthiness of mobile nodes."
> 
> This (IMO limited) applicability makes me wonder if we should publish
> this as experimental rather than standards track.

I think we already have a lot of experience with this, and
know that it works.  It was, after all, the _only_ method
available until the return routability was devised, and it
was deleted from the base specification only at the last
minute, sigh.  What is the rationale for experimental?
It is already well laid out exactly what that applicability
is for the specification.  The behavior is easier to predict
than RFC 3775.  I think it should be published as a Proposed
Standard.

Regards,
Charlie P.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 16:13:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXlxh-0007cT-GX; Mon, 16 May 2005 16:13:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXlxf-0007by-Vn
	for mip6@megatron.ietf.org; Mon, 16 May 2005 16:13:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12439
	for <mip6@ietf.org>; Mon, 16 May 2005 16:13:09 -0400 (EDT)
Received: from e4.ny.us.ibm.com ([32.97.182.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXmEG-00070w-Cq
	for mip6@ietf.org; Mon, 16 May 2005 16:30:21 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236])
	by e4.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j4GKD0NB021134
	for <mip6@ietf.org>; Mon, 16 May 2005 16:13:01 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j4GKD0Xn112744 for <mip6@ietf.org>; Mon, 16 May 2005 16:13:00 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1])
	by d01av04.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j4GKD0ik014292
	for <mip6@ietf.org>; Mon, 16 May 2005 16:13:00 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17])
	by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j4GKD0Iv014269; 
	Mon, 16 May 2005 16:13:00 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1])
	by rotala.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j4GKCxuh020236; 
	Mon, 16 May 2005 16:13:00 -0400
Message-Id: <200505162013.j4GKCxuh020236@rotala.raleigh.ibm.com>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6] mip6-precfgkbm-01.txt review 
In-Reply-To: Message from charliep@iprg.nokia.com
	of "Mon, 16 May 2005 13:07:01 PDT." <4288FD65.44697D5@iprg.nokia.com> 
Date: Mon, 16 May 2005 16:12:59 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Charlie.

> O.K.  "Shared key" does NOT imply preconfigured -- for instance,
> AAA can distribute shared keys.

Good point!

> > Actually, I view that last part of the above as quite significant.
> > There may also be problem related to broken implementations and such,
> > if a CN has a binding cache entry with a long time out that is no
> > longer correct (e.g., a COA address has been assigned to another
> > node).

> This seems to be a low-probability event in IPv6.

I think arguing either way requires making assumptions, and I don't
know that either set of assumptions will prove correct ten years from
now...

> I think we already have a lot of experience with this, and know that
> it works.  It was, after all, the _only_ method available until the
> return routability was devised, and it was deleted from the base
> specification only at the last minute, sigh.  What is the rationale
> for experimental?  It is already well laid out exactly what that
> applicability is for the specification.  The behavior is easier to
> predict than RFC 3775.  I think it should be published as a Proposed
> Standard.

To be clear, I'm somewhat on the fence. I agree that PS is correct
from the perspective of "it works, it's been vetted for
interoperability, it can advance up the standards track, and if you
are going to implement something like this, this protocol is what you
should implement...". Ooops, I think I just argued for PS. :-)

The signal I don't like to send is that this (because it is a
standard) is something everyone should implement. And PS sometimes
does that. So, if the applicability statement is clear and accurate, I
think that would address my concern adequately.

Thomas

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 16 16:51:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DXmZ4-0002zu-GW; Mon, 16 May 2005 16:51:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DXmYx-0002qw-3f
	for mip6@megatron.ietf.org; Mon, 16 May 2005 16:51:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19166
	for <mip6@ietf.org>; Mon, 16 May 2005 16:51:40 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXmpZ-0001YU-0D
	for mip6@ietf.org; Mon, 16 May 2005 17:08:53 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j4GKKQN20539;
	Mon, 16 May 2005 13:20:26 -0700
X-mProtect: <200505162020> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdAZ87Tb; Mon, 16 May 2005 13:20:24 PDT
Message-ID: <428907C7.C9A14B6F@iprg.nokia.com>
Date: Mon, 16 May 2005 13:51:19 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [Mip6] LC review of draft-ietf-mip6-precfgkbm-01.txt
References: <200505161902.j4GJ2hcA019412@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello again Thomas,

Thomas Narten wrote:

> General comment. This document really needs another pass from an
> editorial perspective in the sense of being understandable to a
> general reader who doesn't already know all about this technology.
> The document needs to have more text providing background,
> applicability, context, etc. Morever, for someone to do a security
> analysis, I suspect there needs to be more background context to
> understand what is being proposed and why. E.g., who is assumed to
> have this pre-configured info, and how/when do they use it? (Don't
> assume that a reader of this document has just read RFC 3775 and is
> familiar with all its details!)

I think we have to assume some familiarity with RFC 3775.  It is
unrealistic to think that someone would implement this
specification without first understanding Mobile IPv6.

I also don't believe we can specify:

>         ...                     who is assumed to
> have this pre-configured info, and how/when do they use it?

As long as they get the key and configure it, and follow
the specification, what else needs to be said??

Or maybe I am missing your point, and if you have some
suggested text I could add it to the specification.

> I don't think a lot of work is needed here, but a pass needs to be
> made with an eye towards making it more understandable to a general
> reader is in order.

Do you mean a reader who has no clue about RFC 3775?

> I think the applicability statement should explicitely point out that
> per-MN configuration is needed on the CN, and part of the
> applicability is environments where this is deemed acceptable.

It does say this:

>   A mobile node MUST use a different value for Kcn for each node in
>   its Binding Update List, and a correspondent node MUST ensure that
>   every mobile node uses a different value of Kcn.

Should it say more?

> Abstract  really needs beefing up.

This is a very, very small specification.  I think it
should stay that way.  What additional idea do you think
should be expressed in the abstract?

> Document would benefit from an introduction section targetted towards
> a more general reader. As it is, it just starts off with details.

Jari sent some text for the Introduction, and I am planning
to use that.  Do you think it is sufficient?

> Seem odd that nonce indicies "SHOULD NOT" be present, but upon receipt
> it is only a "MAY" that ie be ignorred. Seems like the default would
> be to ignore them, since they aren't supposed to be included. Or, if
> they are included, do you really want to say they need to be processed
> as defined in the base MIPv6 spec?

I really wanted to say that they are ignored for the case
of preconfigured keys.

> Also why are they not covered by the authentication data? Is this
> consistent with the base spec? And does it have any security
> implications?

Since they are ignored, I am sure there is no security implication.
However, perhaps they should be covered by the Authenticator, to
avoid special rules in this case for the calculation.

I think it's better to just not send the Nonce Indices option
at all.

> >     -  the correspondent node has some guarantee that the mobile node
> >        will behave properly (perhaps by contractual agreement)
> 
> I must not understand something here. I read the above as saying that
> this draft introduces vulnerabiilties not present in the base MIPv6
> space, but that those vulnerabilities are acceptable because the MN
> and CN are "are under contract, so MN won't be bad." Am I
> understanding this correctly?

The draft clearly states the applicability conditions.
Under these conditions, the danger of misusing care-of
addresses is supposed to eliminated.  If there is a danger
of misusing care-of addresses, then the draft is not
applicable.  Thus, we can say that the vulnerability
of misusing care-of addrsses, which would otherwise be
present, is prevented by adherence to the applicability
conditions.


> >     -  diagnostic procedures
> >
> >     -  software development and testing
> 
> I don't understand these. Are there any examples (and if so, include
> them in the document)

I believe that everyone who has debugged a Mbbile IP has used
some sort of preconfigured keys to do the testing.  How should
I express this in the document?

> Question: when are these extensions used? E.g., what happens if MN has
> them configured but CN does not (or vice versa)? Is there a fallback?
> is there negotiation? Do things still work?

As Jari points out, things don't work well when the
preconfigured keys are not preconfigured.  Also, they
don't work well when the wrong keys are preconfigured.
There is a very long list of things that don't work
when things are broken.  For instance, if there is a
bug in the Mobile IPv6 implementation, it does not
work.

This is how Mobile IPv4 works.

> >    are under the same administration.  The return routability procedure
> >    is RECOMMENDED for all general use and MUST be the default, unless
> >    the user explicitly overrides this by entering the abovementioned
> >    preconfigured data for a particular peer.
> 
> Which user? On the MN? on the CN? both?  That is, does the MN (not the
> CN) choose when to enable this? How does the CN know which to use?

Both sides have to agree.  I don't understand how it could
be different.  The user does explicitly override the return
routability procedure for the particular peer.

> >    protected against reboots.  If the mobile node were to send a fresh
> >    Binding Update to its correspondent node every hour, 24 hours a day,
> >    every day of the year, and utilize the same care-of address every
> >    time, this would require changing keys every 7 years.  Even if the
> 
> Aren't these numbers disingenious? I.e., isn't the timeout associated
> with BUs on the order of only a few minutes, and much less than one
> hour?

The lifetime for the Binding Update is in the Binding Update.  It can
be a lot longer if there are preconfigured keys, since the danger of
replay protection is nearly absent.  The binding lifetime for the
preconfigured keys is until somemone wants to reconfigure the machines.
The vulnerability associated with return routability does not exist.


> The document really needs more text about lifetimes. For one thing, it
> seems like bad things will happen of the MN and CN have different
> ideas of what the lifetime should be.  What does this document
> _recommend_? Shouldn't the lifetimes be part of the configuration?
> Or???

The lifetime of the Binding Update is in the Binding Update
message.  There is no expiration lifetime associated with the
preconfigured key, because there is no significant danger of
replay. 

Regards,
Charlie P.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 17 11:13:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DY3lR-0000v8-Ma; Tue, 17 May 2005 11:13:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DY3lO-0000uL-0C
	for mip6@megatron.ietf.org; Tue, 17 May 2005 11:13:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04912
	for <mip6@ietf.org>; Tue, 17 May 2005 11:13:39 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DY428-0004al-NK
	for mip6@ietf.org; Tue, 17 May 2005 11:31:02 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 16D3A89879;
	Tue, 17 May 2005 18:13:30 +0300 (EEST)
Message-ID: <428A0A24.4070608@kolumbus.fi>
Date: Tue, 17 May 2005 18:13:40 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>,
	"Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6] mip6-precfgkbm-01.txt review
References: <200505162013.j4GKCxuh020236@rotala.raleigh.ibm.com>
In-Reply-To: <200505162013.j4GKCxuh020236@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


>>O.K.  "Shared key" does NOT imply preconfigured -- for instance,
>>AAA can distribute shared keys.
>>    
>>
>
>Good point!
>  
>
I would actually rather see this draft and its security
considerations focus on the preconfigured case.

Of course we may develop a AAA mechanism to deliver
keys for this at a later stage. But I'm uneasy with claiming
generality to new situations without seeing the system
level specifications of how that works and why its
efficient/good idea/secure etc.

Keep it simple, and short. Work on add-ons and new
documents later if you want AAA to key this.

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 17 11:19:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DY3qg-0002Jj-6W; Tue, 17 May 2005 11:19:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DY3qd-0002JY-VY
	for mip6@megatron.ietf.org; Tue, 17 May 2005 11:19:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05301
	for <mip6@ietf.org>; Tue, 17 May 2005 11:19:05 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DY47P-0004tO-Lv
	for mip6@ietf.org; Tue, 17 May 2005 11:36:28 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 7985089879;
	Tue, 17 May 2005 18:18:58 +0300 (EEST)
Message-ID: <428A0B6D.3090601@kolumbus.fi>
Date: Tue, 17 May 2005 18:19:09 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6] LC review of draft-ietf-mip6-precfgkbm-01.txt
References: <200505161902.j4GJ2hcA019412@rotala.raleigh.ibm.com>
	<428907C7.C9A14B6F@iprg.nokia.com>
In-Reply-To: <428907C7.C9A14B6F@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Charles E.Perkins wrote:

>>Question: when are these extensions used? E.g., what happens if MN has
>>them configured but CN does not (or vice versa)? Is there a fallback?
>>is there negotiation? Do things still work?
>>    
>>
>
>As Jari points out, things don't work well when the
>preconfigured keys are not preconfigured.  Also, they
>don't work well when the wrong keys are preconfigured.
>There is a very long list of things that don't work
>when things are broken.  For instance, if there is a
>bug in the Mobile IPv6 implementation, it does not
>work.
>  
>
Generally speaking we want our protocols to fail
gracefully, have reasonable fallbacks when something
is not configured correctly etc. However, this does
not always apply. For instance, in this case I believe
we have some worries about bidding down attacks,
if we were to default to RR if this procedure fails (or
vice versa, neither procedure is strictly more secure
than the other).

So, I believe what Charlie you have written for the
behaviour on this point is more or less correct. But
as I pointed out in my review it would be useful to
document the rationale in Section 3. No, I don't
have text beyond what I have written above, sorry.

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 18 09:15:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DYOOT-0004ST-TG; Wed, 18 May 2005 09:15:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DYGah-0007bW-JE; Wed, 18 May 2005 00:55:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26299;
	Wed, 18 May 2005 00:55:27 -0400 (EDT)
Received: from none.cs.umass.edu ([128.119.241.136])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DYGra-0002Jd-Iz; Wed, 18 May 2005 01:12:58 -0400
Received: from [10.0.1.2] (c-24-218-59-49.hsd1.ma.comcast.net [24.218.59.49])
	by none.cs.umass.edu (8.12.8/8.12.5) with ESMTP id j4I4tIUf021783;
	Wed, 18 May 2005 00:55:19 -0400
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <80edcc3dfa17b1b9a8918718a7c4bce8@cs.umass.edu>
Content-Transfer-Encoding: quoted-printable
From: Deepak Ganesan <dganesan@cs.umass.edu>
Date: Wed, 18 May 2005 00:55:18 -0400
To: Deepak Ganesan <dganesan@cs.umass.edu>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 18 May 2005 09:15:24 -0400
Cc: 
Subject: [Mip6] DIAL M-POMC 2005: Workshop on Foundation of Mobile Computing
	CFP
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Our apologies if you receive multiple copies of this CFP.

       =A0PRELIMINARY CALL FOR PAPERS - DIAL M-POMC 2005

            The Third ACM/SIGMOBILE International Workshop on
                          Foundation of Mobile Computing

                     September 2, 2005 - Cologne, Germany
                      (co-located with ACM MobiCom 2005)

		http://gridnet.nec-labs.com/dialm

          =A0=A0=A0=A0=A0=A0=A0       =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0IMP=
ORTANT DATES

                Paper submission due:            May 30, 2005
                Notification of acceptance:      July 5, 2005
                Camera-ready version due:    July 20, 2005


DIAL M-POMC is devoted to algorithms and modeling in the context of
mobile and wireless computing and communications. It is intended to be
a lively meeting, covering many of the algorithmic aspects of this
field ranging from operations research to radio engineering
problems. In particular, it aims at fostering the cooperation among
practitioners and theoreticians of the field.

This workshop is a merging of two workshops: DIAL M (Discrete
Algorithms and Methods for Mobile Computing and Communications), which
was held annually from 1997 to 2004 as a workshop in conjunction with
ACM/SIGMOBILE MobiCom; and POMC (Principles of Mobile Computing),
which was held in 2001 in conjunction with the ACM/SIGACT and SIGOPS
Symposium on Principles of Distributed Computing (PODC), and in 2002
in conjunction with the ACM International Symposium on Distributed
Computing (DISC).

DIAL M-POMC 2005 will be composed of invited and peer-reviewed
contributed talks.

SCOPE: Mobile computing and communications devices will have an
enormous impact on our lifestyle over the next several decades. The
mobility of distributed computing components raises a number of
interesting, and difficult, algorithmic issues. This workshop is
devoted to algorithms and methods in the context of mobile and
wireless computing and communications. The workshop is intended to
foster cooperation among researchers in mobile computing and
researchers in discrete and distributed algorithms.

PAPERS: All submitted papers will be rigorously reviewed by technical
program committee members. Accepted papers will be published in the
workshop proceedings. Technical papers describing original, previously
unpublished research, not currently under review by another conference
or journal, are solicited. Contributions are solicited in all areas
related to mobile and wireless computing and communications where
discrete algorithms and methods are utilized. Specific topics include,
but are not limited to:

- Channel assignment and management
- Cryptography and security
- Handover (handoff)
- Routing, multicast and broadcast
- Scheduling
- Synchronization
- Selfish behavior and cooperation
- Energy saving methods and protocols
- Ad hoc and sensor networking
- Localization and location tracking
- Error correcting codes
- Protocol optimization
- Dynamic networks
- Cooperation enforcement
- Dynamic graph algorithms
- Modeling

SUBMISSION INSTRUCTIONS: All paper submissions will be handled
electronically (see the conference web page for details). Authors
should prepare an electronic version of their full paper. Papers must
not exceed 11 pages (US Letter size, 8.5 x 11 inches) including text,
figures and references. The font size must be at least 11 points.


Program Co-Chairs
Suman Banerjee
Univ. of Wisconsin, Madison
suman@cs.wisc.edu

Samrat Ganguly
NEC Labs
samrat@nec-labs.com

Publicity Chair
Deepak Ganesan
Univ. of Massachusetts
dganesan@cs.umass.edu

Steering Committee
Ian Akyildiz (Georgia Tech)
Maurizio Bonuccelli (U. of Pisa)
Afonso Ferreira (INRIA)
Errol Lloyd (U. of Delaware)
Nancy Lynch (MIT)
Andre Schiper (EPFL)
Arunabha Sen (ASU)
Nitin Vaidya (UIUC)

Program Committee (partial list)

  Stefano Basagni(Northeastern University) basagni@ece.neu.edu
  Stephan Eidenbenz (Los Alamos National Labs) eidenben@lanl.gov
  Andras Farago (UT Dallas) farago@utdallas.edu
  Kamal Jain (Microsoft Research) kamalj@microsoft.com
  Li (Erran) Li (Bell Labs) erranlli@dnrc.bell-labs.com
  Archan Misra (IBM TJ Watson Research Center) archan@us.ibm.com
  Vishal Misra (Columbia University) misra@cs.columbia.edu
  S. Muthukrishnan (Rutgers) muthu@cs.rutgers.edu
  Dina Papagiannaki (Intel Research, Cambridge)=20
dina.papagiannaki@intel.com
  Cynthia Phillips (Sandia National Labs) caphill@sandia.gov
  Chiara Petrioli (University of Roma) petrioli@di.uniroma1.it
  Lili Qiu (University of Texas Austin) lili@cs.utexas.edu
  Rajmohan Rajaraman (Northeastern University) rraj@ccs.neu.edu
  Raghupathy Sivakumar (Georgia Institute of Technology)=20
siva@ece.gatech.edu
  Aravind Srinivasan (University of Maryland) srin@cs.umd.edu
  Martha Steenstrup  (Stow Research) steenie@rcn.com
  Subhash Suri (University of California Santa Barbara) suri@cs.ucsb.edu


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 19 02:03:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DYe82-0000mQ-G8; Thu, 19 May 2005 02:03:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DYe7z-0000mL-Vb
	for mip6@megatron.ietf.org; Thu, 19 May 2005 02:03:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06553
	for <mip6@ietf.org>; Thu, 19 May 2005 02:03:26 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DYeP4-0006bl-PK
	for mip6@ietf.org; Thu, 19 May 2005 02:21:08 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j4J635l14239; Thu, 19 May 2005 08:03:05 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j4J6350V035548; Thu, 19 May 2005 08:03:05 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200505190603.j4J6350V035548@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] Please review draft-irtf-mobopts-ro-enhancements-00.txt 
In-reply-to: Your message of Wed, 04 May 2005 13:13:49 CDT.
	<456943D540CFC14A8D7138E64843F8535BAEA0@daebe101.NOE.Nokia.com> 
Date: Thu, 19 May 2005 08:03:05 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:
   
   The Mobopts RG has produced the following ID:
   draft-irtf-mobopts-ro-enhancements-00.txt
   
   Please review the ID and comment.
   
=> I have two concerns with this document:
 - first there is already a good document about the (in)security of
   the current routing optimization,
 - second I really believe the document is going to the wrong direction:
   Concerns I've heard about RO/RR are:
    * RR is not secure enough for the main security problem: possible
      remote redirection of one's traffic
    * RR is too heavy for a server with thousands of mobile clients.
   So for instance CGA, which can be considered as not very secure by
   itself, is a right improvment because it protects home addresses
   against thefts. And at the contrary CBA, which tries to protect
   against a secondary and IMHO FUD threat (just look at a botnet
   presentation at RIPE/NANOG/...), adds only complexity.

Regards

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sat May 21 07:19:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DZS1C-0002GA-RU; Sat, 21 May 2005 07:19:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DZS19-0002EG-D9
	for mip6@megatron.ietf.org; Sat, 21 May 2005 07:19:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29266
	for <mip6@ietf.org>; Sat, 21 May 2005 07:19:41 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DZMSQ-0004xV-VA
	for mip6@ietf.org; Sat, 21 May 2005 01:23:32 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 1A82F89869;
	Sat, 21 May 2005 08:05:01 +0300 (EEST)
Message-ID: <428EC18B.5030507@kolumbus.fi>
Date: Sat, 21 May 2005 08:05:15 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
References: <200505161902.j4GJ2hcA019412@rotala.raleigh.ibm.com>		<428907C7.C9A14B6F@iprg.nokia.com>
	<428A0B6D.3090601@kolumbus.fi> <428E99A2.D1054968@iprg.nokia.com>
In-Reply-To: <428E99A2.D1054968@iprg.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, mip6@ietf.org
Subject: [Mip6] Re: New revision of draft-ietf-mip6-precfgkbm
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Charles E.Perkins wrote:

>>Generally speaking we want our protocols to fail
>>gracefully, have reasonable fallbacks when something
>>is not configured correctly etc.
>>    
>>
>In this case, the graceful fallback position is that
>the mobile node and correspondent node can't use
>route optimization until the shared data is corrected.
>Even so, they ought to be able to communicate by way
>of the home agent.
>  
>
Yes. And this is good enough for me.

(Even better would have been if we could
fallback to regular RO, but as explained in
previous e-mails, I don't think we can do that.)

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sat May 21 07:23:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DZS5H-0003wQ-2i; Sat, 21 May 2005 07:23:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DZS5F-0003va-AB
	for mip6@megatron.ietf.org; Sat, 21 May 2005 07:23:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02609
	for <mip6@ietf.org>; Sat, 21 May 2005 07:23:55 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DZJo7-00045z-AT
	for mip6@ietf.org; Fri, 20 May 2005 22:33:44 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j4L1hsK14295;
	Fri, 20 May 2005 18:43:54 -0700
X-mProtect: <200505210143> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd9XwRDE; Fri, 20 May 2005 18:43:52 PDT
Message-ID: <428E99A2.D1054968@iprg.nokia.com>
Date: Fri, 20 May 2005 19:14:58 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>, Thomas Narten <narten@us.ibm.com>
References: <200505161902.j4GJ2hcA019412@rotala.raleigh.ibm.com>
	<428907C7.C9A14B6F@iprg.nokia.com> <428A0B6D.3090601@kolumbus.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
Subject: [Mip6] New revision of draft-ietf-mip6-precfgkbm
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



Hello folks,

I have created a revised specification according to
comments received during Last Call.  It is available
at the following URL:
   http://people.nokia.net/~charliep/txt/mobilev6/precfg.txt

I would like to submit it to the Internet Draft
directories ASAP, so please let me know if I have
made appropriate resolutions for your comments.

I have one comment on some previous e-mail...

Jari Arkko wrote:

> Generally speaking we want our protocols to fail
> gracefully, have reasonable fallbacks when something
> is not configured correctly etc.

In this case, the graceful fallback position is that
the mobile node and correspondent node can't use
route optimization until the shared data is corrected.
Even so, they ought to be able to communicate by way
of the home agent.

I think that is pretty much O.K.  It might be nice for
some indication to be brought to the user's attention,
so that the problem could be identified and corrected.
But, user interface details don't belong in this
document, I don't think.

Regards,
Charlie P.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sun May 22 16:10:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DZwmG-0003SI-L2; Sun, 22 May 2005 16:10:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DZwmF-0003S9-AP
	for mip6@megatron.ietf.org; Sun, 22 May 2005 16:10:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21745
	for <mip6@ietf.org>; Sun, 22 May 2005 16:10:21 -0400 (EDT)
Received: from warsaw.ucdavis.edu ([169.237.104.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DZx44-0001jR-3A
	for mip6@ietf.org; Sun, 22 May 2005 16:28:49 -0400
Received: from citheronia.ucdavis.edu (citheronia.ucdavis.edu
	[169.237.104.183])
	by warsaw.ucdavis.edu (8.12.10/8.12.9/it-defang-5.2.0) with ESMTP id
	j4MKAILH018493
	for <mip6@ietf.org>; Sun, 22 May 2005 13:10:19 -0700 (PDT)
Received: from citheronia.ucdavis.edu (localhost [127.0.0.1])
	by citheronia.ucdavis.edu (8.12.10/8.12.9/UCD5.2.0) with ESMTP id
	j4MKAIU7003113
	for <mip6@ietf.org>; Sun, 22 May 2005 13:10:18 -0700 (PDT)
Received: (from www@localhost)
	by citheronia.ucdavis.edu (8.12.10/8.12.9/Submit) id j4MKAIBZ003112;
	Sun, 22 May 2005 13:10:18 -0700 (PDT)
Date: Sun, 22 May 2005 13:10:18 -0700 (PDT)
Message-Id: <200505222010.j4MKAIBZ003112@citheronia.ucdavis.edu>
To: mip6@ietf.org
From: "Fan Zhao" <fanzhao@ucdavis.edu>
X-Errors-To: fanzhao@blue.ucdavis.edu
X-Mailer: Geckomail-b16
X-Originating-IP: [128.120.178.196]
X-User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Scanned-By: MIMEDefang 2.49 on 169.237.104.195
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Subject: [Mip6] Call for Paper: JSAC-MRNM (The deadline is approaching)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


       PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES       

                            CALL FOR PAPERS                            
            IEEE Journal on Selected Areas in Communications            
                  MOBILE ROUTERS AND NETWORK MOBILITY                  

  http://www.argreenhouse.com/society/J-SAC/Calls/mobile_routers.html

Network mobility support is concerned with managing the mobility of an 
entire network that is changing its point of attachment to the Internet 
and thus its reachability in the Internet topology. If network mobility 
is not explicitly supported by some mechanisms, existing sessions break 
and connectivity to the global Internet is lost. A mobile network is 
composed of Mobile Router(s) (MR) and Mobile Network Nodes (MNN) that 
can be fixed or mobile. There has been rapid development in network 
mobility support, i.e., providing Internet connectivity to the networks 
that move using mobile routers since the inception of Mobile IPv4 in 
1996. Seamless Internet access in public transportation such as in 
trains and busses can be possible if mobile routers are used. Cars with 
low-power sensors seamlessly connected to the Internet constitute yet 
another example of networks which move. To date, some airline companies 
announced Internet connectivity support during commercial flights and 
this trend is expected to accelerate and cover most if not all flights. 

This issue is focused on modeling, analysis, and simulation of network 
mobility support protocols. We solicit papers presenting original and 
unpublished work including, but not limited to the following topics: 

* Modeling and Analysis of Network Mobility 
    o Modeling, analysis and simulation of mobile router 
    o Protocols for route optimization 
    o Mobility issues inside a mobile network 
    o Mobile IPv6 extensions for route optimization 
    o Nested mobile networks 
    o Multihomed mobile networks 
    o Operational issues to deploy mobile networks 
    o Auto-configuration for mobile networks 
    o Mobile router support on cellular phone platforms 

* Services in the Networks that Move 
    o Service advertisement and discovery protocols in networks that
      move 
    o Specifications nad models of services for network mobility 
    o Encryption and authentication in service access for network
      mobility 

* Security Issues in Network Mobility 
    o Security analysis of present network mobility support protocols 
    o Applications of AAA and EAP to network mobility 
    o Interaction with security-enhanced modules in other layers 
      (vertically) or other middle boxes (horizontally) 

Prospective authors should follow the IEEE J-SAC manuscript format 
described in the Information for Authors. Authors MUST submit their 
draft manuscripts through the EDAS peer review website, together with a 
short abstract (approximately 150 words) in the EDAS website form. 
Please note potential authors should create their own accounts through 
the EDAS peer review website before submitting manuscript(s). EDAS will 
accept manuscripts in PDF format only. There will be one round of 
reviewers and acceptance will be limited to those papers requiring only 
moderate revisions. The following timetable applies: 

Manuscript Submission: JUNE 1, 2005
Acceptance Notification: December 1, 2005
Final Manuscript Due: March 1, 2006
Publication: 3rd Quarter 2006

Guest Editorial Board: 

Behcet Sarikaya
Computer Science Dept
Univ of Northern British Columbia
Prince George, BC
Canada V2N 4Z9
sarikaya@unbc.ca

S. Felix Wu
Dept of Computer Science
Univ of California at Davis
Davis, CA 95616 USA
wu@cs.ucdavis.edu

Gopal Dommety
Cisco Systems, Inc
170 West Tasman Dr
San Jose, CA 95134-1706 USA
gdommety@cisco.com

Claude Castelluccia
INRIA Rhône-Alpes ZIRST
655 Ave de l'Europe
Montbonnot
38334 Saint Ismier cedex
France
claude.castelluccia@inria.fr

Thierry Ernst
Jun Murai Lab
Keio Univ K-square
Town Campus
1488-8 Ogura, Saiwai-ku,
Kawasaki, Kanagawa 212-0054
Japan
ernst@sfc.wide.ad.jp

Charles E. Perkins
Communication Systems Lab
Nokia Research Center
313 Fairchild Dr
Mountain View, CA 94943 USA
charliep@iprg.nokia.com

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 23 17:01:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DaK32-0000uZ-4C; Mon, 23 May 2005 17:01:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DaK2z-0000uO-NV
	for mip6@megatron.ietf.org; Mon, 23 May 2005 17:01:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20833
	for <mip6@ietf.org>; Mon, 23 May 2005 17:01:11 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaKL1-0000np-C7
	for mip6@ietf.org; Mon, 23 May 2005 17:19:52 -0400
Message-ID: <023701c55fda$b7245cd0$016115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <mip6@ietf.org>
Date: Mon, 23 May 2005 14:02:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Multiple BUs per packet?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Suppose a MN has multiple home/care of addresses assigned to an interface,
or it has multiple interfaces, each with a separate set of home/care of
addresses assigned to it. Suppose further that the MN is using more than one
address set with a particular CN.

When the MN moves (if it has multiple interfaces, both interfaces move),
would it be acceptable for the MN to send one packet with two BU Mobility
Headers in it, for both addresses?

I assume that different sets of Bmk would be required, since the Bmk
calculation requires the home address to be used.

            jak



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 23 17:15:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DaKGl-0003KE-PX; Mon, 23 May 2005 17:15:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DaKGj-0003K6-Rh
	for mip6@megatron.ietf.org; Mon, 23 May 2005 17:15:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21715
	for <mip6@ietf.org>; Mon, 23 May 2005 17:15:23 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.flariontech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaKYl-0001Go-Vo
	for mip6@ietf.org; Mon, 23 May 2005 17:34:05 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	ftmailgfi.flariontech.com with Microsoft SMTPSVC(5.0.2195.6713);
	Mon, 23 May 2005 17:15:13 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Multiple BUs per packet?
Date: Mon, 23 May 2005 17:14:07 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBC8CB@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] Multiple BUs per packet?
Thread-Index: AcVf26yBGkGU/kRFTHGZRCVIMTMjTQAAFgwA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "James Kempf" <kempf@docomolabs-usa.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 23 May 2005 21:15:13.0761 (UTC)
	FILETIME=[828C6510:01C55FDC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


 > Suppose a MN has multiple home/care of addresses assigned to=20
 > an interface,
 > or it has multiple interfaces, each with a separate set of=20
 > home/care of
 > addresses assigned to it. Suppose further that the MN is=20
 > using more than one
 > address set with a particular CN.
 >=20
 > When the MN moves (if it has multiple interfaces, both=20
 > interfaces move),
 > would it be acceptable for the MN to send one packet with=20
 > two BU Mobility
 > Headers in it, for both addresses?

=3D> Not in the current spec. I'm assuming that you are talking=20
about a MN that uses multiple addresses with the same CN (i.e.
the same CN address). Obviously this is only possible if=20
the MN has more than one HoA.=20
The Bicasting draft solved this problem between the MN and MAP/AR
but that's based on an HA-like SA.

With a CN you'd have to run RR twice.

Hesham

 >=20
 > I assume that different sets of Bmk would be required, since the Bmk
 > calculation requires the home address to be used.
 >=20
 >             jak
 >=20
 >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 23 18:34:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DaLUu-0007gb-OV; Mon, 23 May 2005 18:34:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLUs-0007gR-HR
	for mip6@megatron.ietf.org; Mon, 23 May 2005 18:34:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05847
	for <mip6@ietf.org>; Mon, 23 May 2005 18:34:04 -0400 (EDT)
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaLmw-0006SM-HO
	for mip6@ietf.org; Mon, 23 May 2005 18:52:46 -0400
Received: from usdaln07347 (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j4NMXtCR012197; Mon, 23 May 2005 17:33:55 -0500 (CDT)
Message-Id: <200505232233.j4NMXtCR012197@auds953.usa.alcatel.com>
From: "Tim Ozugur" <tim.ozugur@alcatel.com>
To: <mip6@ietf.org>
Date: Mon, 23 May 2005 17:33:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-index: AcVPYqCdGhRw/vEsTTy5gWxhKF55nwQgYPcAAADQ3jA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Call For Participation: BWAN 2005
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


(Apologies if you are receiving this message more than once)

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

                   CALL FOR PARTICIPATION

   International Workshop on Broadband Wireless Access 
              Network on fixed network (BWAN 2005)
                   (http://www.bwan.org/)

                ORLANDO, FL - JUNE 15, 2005

     co-located with International Conference on 
    Multimedia Services Access Networks (MSAN'05) 

                   CO_SPONSORED BY IEEE

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

International Workshop on Broadband Wireless Access Network on fixed network
(BWAN 2005) will host a panel entitled "Future of Telecom Industry".

PANEL:

Today, Telecom Industry is moving in a new era where broadband wireless
access is progressing quickly towards multi-access even though there are
still technical challenges to tackle and new interesting business models are
appearing in parallel for the benefit of customers. So, what will be the
Telecom Industry and communication orientations for the future?

A panel, including leaders like Global operators and industrials, such as 

- Alcatel
- Alvarion
- Flarion Technologies
- Telenor

will discuss some key challenges, including "Trends and Strategies on the
Broadband mobile Wireless access network in 2010" during the BWAN workshop.

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



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 24 11:03:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Daaw8-0005eI-HT; Tue, 24 May 2005 11:03:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DaF30-0003Ee-1h; Mon, 23 May 2005 11:40:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06402;
	Mon, 23 May 2005 11:40:51 -0400 (EDT)
Received: from xenia3-in0.renault.fr ([193.194.133.17]
	helo=xenia3.mc2.renault.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DaFKz-0000Jm-Nj; Mon, 23 May 2005 11:59:30 -0400
Received: from univers4.mc2.renault.fr (univers4-in0.mc2.renault.fr
	[10.210.68.9])
	by xenia3.mc2.renault.fr (8.13.1/8.13.1) with ESMTP id j4NFej9C028255; 
	Mon, 23 May 2005 17:40:45 +0200 (MEST)
Received: from hepatite1.mc2.renault.fr (hepatite1.mc2.renault.fr
	[10.210.68.19])
	by univers4.mc2.renault.fr (8.13.4/8.13.4) with SMTP id j4NFeXAD014342; 
	Mon, 23 May 2005 17:40:33 +0200 (MEST)
Received: from univers3-in0.mc2.renault.fr(10.210.68.1) by
	hepatite1.mc2.renault.fr via csmap 
	id be9f74cc_cba0_11d9_8377_0002b3cb50ff_12410;
	Mon, 23 May 2005 17:38:43 +0200 (CEST)
Received: from su356aos (su356aos.mc2.renault.fr [138.21.107.59])
	by univers3.mc2.renault.fr (8.13.1/8.13.1) with ESMTP id j4NFboWZ026089;
	Mon, 23 May 2005 17:37:50 +0200 (MEST)
Received: from su358aos (su358aos.mc2.renault.fr [138.21.107.206])
	by wsmtp54.mc2.renault.fr
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTP id <0IGY00J3U8R250@wsmtp54.mc2.renault.fr>; Mon,
	23 May 2005 17:37:50 +0200 (MEST)
Received: from FR20016868 ([10.230.213.114]) by wsmtpin57.mc2.renault.fr
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with SMTP id <0IGY00MD08R2KL@wsmtpin57.mc2.renault.fr>; Mon,
	23 May 2005 17:37:50 +0200 (MEST)
Date: Mon, 23 May 2005 17:37:41 +0200
From: LASNIER-REDDAN Edouard <Edouard.Lasnier-Reddan@renault.com>
To: mip6@ietf.org, nemo@ietf.org
Message-id: <02b701c55fad$5b8f3520$72d5e60a@corp.noxiane.net>
Organization: Renault
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
Content-type: multipart/mixed; boundary="Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)"
X-Priority: 3
X-MSMail-priority: Normal
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
X-Mailman-Approved-At: Tue, 24 May 2005 11:03:14 -0400
Cc: HORKAY Francois <francois.horkay@renault.com>
Subject: [Mip6] Requirement of a Car Manufacturer for real MIPv6 large
 deployments (IPv4 NAT traversal feature)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format...

--Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)
Content-type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by univers3.mc2.renault.fr
	id j4NFboWZ026089
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear NEMO WG participants,





The car manufacturer RENAULT is involved in several research projects
dealing with IP mobility since 2001. One of our major achievements was the
RENAULT Laguna "IPv6 Car", supporting Mobile IPv6. This telematic concept
car received the "Murai Award" in 2003 in Tokyo for its capability to
support GPRS (2G European cellular network) / Wifi vertical handover, using
Mobile IPv6 with IPv4 NAT traversal feature (the NAT traversal function,
called "DOORS", was developed by Cisco Systems, it did provide efficient
results and is compatible with our deployment constraints for further
commercial exploitations).



Mobile IPv6 is considered by the car manufacturers as a key technology for
the deployment of next generation Telematic services, such as remote
diagnosis, fleet management, etc.

This trend has been confirmed by the current work of the research project
GST - Global System for Telematics, in which RENAULT, BMW, DAIMLER CHRYSLER,
FIAT and many other actors of the Telematic Industry work on standardization
convergence : IPv6 is now part of the core specification for a European
standard for telematics, mainly because of its mobility features.



If it is agreed by the automotive industry that IPv6 paves the future of the
telematic market, the existing constraints on the deployment of Mobile IPv6
makes the finalization of the standard very sensitive:



1.      For the car manufacturers, Mobile IPv6 will have to be deployed soon
on top of existing cellular networks, such as GPRS, EDGE or UMTS, all based
on IPv4. In order to remain independent from the mobile telecom operator, it
is mandatory to deploy Mobile IPv6 with a NAT traversal support. Deploying
MIPv6 without a NAT traversal feature would be a non sense: if the car
manufacturers have to setup technical agreements with the mobile telecom
operators to deploy MIPv6, then many other solutions can be considered, and
MIPv6 leads to a situation of dependence toward the mobile telecom
operators, which is not acceptable.
MIPv6 should not limit the possible business models : it should enable the
actors of the value chain to define their business model, and in this MIPv6
context, it means that MIPv6 should be flexible and not compel the Home
Agent to be directly connected to the Internet.



2.      Having NAT traversal feature is a required feature but the technical
solution defined at the IETF should take into consideration the deployment
constraints. In the next 18 months, MIPv6 will be mainly deployed for pilot
experiments, for validation before a wider deployment. In this context, the
Home Agent is in many cases in existing small networks dedicated to pilot
experiments initially designed for IPv4, with NAT boxes on the Internet
interface. This constraint is a fact, and is valid for many projects.



3.      On a long term perspective, the car manufacturers - or any actors
from the telematic industry supplying IP mobility support for the cars -
will deploy MIPv6 on their enterprise networks. Those networks are secured,
designed for IPv4, and most probably the Home Agent will not be directly
interfaced with the Internet, it will be a secured equipment in the core of
the network, behind NATs.
This problem is in fact very common as enterprise networks are connected to
the Internet behind NATs in general.



If the deployment of Mobile IPv6 requires re-designing the car manufacturers
networks because security policies and existing NAT features are not
supported, then Mobile IPv6 will remain a beautiful idea that no company
will be able to deploy.



Mobile IPv6 should support multiple IPv4 Network Address Translation (in the
access networks, and in front of the Home network). The Home Agent may be
deployed on IPv4 networks behind NAT access to the Internet.



I have currently several industrial projects for which I could deploy MIPv6
_for real_ if the IPv4 NAT traversal would be normalized and enable Home
Agent to be connected to the internet behind NATs and other boxes.



Edouard LASNIER REDDAN, Telecom Solution for Telematics, RENAULT, on May
2nd, 2005



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


Cordialement / Best Regards / Mit Freundlichen Gr=FCssen

Edouard Lasnier Reddan.
edouard.lasnier-reddan@renault.com
Office : + 33 (0)1 76 84 71 93 / Fax :  + 33 (0)1 76 84 91 16
RENAULT
13 avenue Paul Langevin / API : FR EQV NOV 3 32
92359 Le Plessis Robinson Cedex
France

--Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)
Content-type: text/x-vcard; name="Edouard LASNIER REDDAN.vcf"
Content-Disposition: attachment; filename="Edouard LASNIER REDDAN.vcf"
Content-Transfer-Encoding: 7BIT

BEGIN:VCARD
VERSION:2.1
N:LASNIER REDDAN;Edouard
FN:Edouard LASNIER REDDAN
ORG:Renault;DTSI - T2IA / 50820
TITLE:IT & Telematic Engineer
TEL;WORK;VOICE:+33 (0)1 76 84 71 93
TEL;CELL;VOICE:+ 33 (0)6 07 26 87 20
TEL;WORK;FAX:+33 (0)1 76 84 91 16
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Novadis, 3=E8me =E9tage, Module 1;13 avenue Paul Langevin =0D=0AAPI : FR EQ=
V NOV 3 32=0D=0A=0D=0AFrance=0D=0A;Le Plessis Robinson Cedex;92;92359;France
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Novadis, 3=E8me =E9tage, Module 1=0D=0A13 avenue Paul Langevin =0D=0AAPI : F=
R EQV NOV 3 32=0D=0A=0D=0AFrance=0D=0A=0D=0ALe Plessis Robinson Cedex, 92 92=
359=0D=0AFrance
ADR;HOME:;;;;;;France
LABEL;HOME:France
X-WAB-GENDER:2
EMAIL;PREF;INTERNET:edouard.lasnier-reddan@renault.com
REV:20050523T153741Z
END:VCARD

--Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)
Content-Type: text/plain; name="disclaimer.txt"
Content-Disposition: inline; filename="disclaimer.txt"
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
Content-Transfer-Encoding: 7bit

-- Disclaimer ------------------------------------
Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.
***
This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.
--Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)--




From mip6-bounces@ietf.org Thu May 26 19:01:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbRLu-0001NF-HZ; Thu, 26 May 2005 19:01:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DbRLs-0001N6-TN
	for mip6@megatron.ietf.org; Thu, 26 May 2005 19:01:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22084
	for <mip6@ietf.org>; Thu, 26 May 2005 19:01:17 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbReY-0001G0-89
	for mip6@ietf.org; Thu, 26 May 2005 19:20:39 -0400
Message-ID: <0abd01c56246$fe2927f0$016115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <mip6@ietf.org>, <mobopts@irtf.org>
Date: Thu, 26 May 2005 16:02:22 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Mip6] Review of draft-irtf-mobopts-ro-enhancements-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Raj requested I review this draft. Here is my review.

            jak

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

Editorial meta-comment: While I found the draft to be very good, it is quite
long, and I think it could be improved by dropping some parts that are
superficial and not relevent to the basic theme. For example, Sections 5.13
through 5.17, Section 6.2.1, and some material in Section 6.3 on the same
topics. These sections all talk about handover optimizations schemes that do
not involve improvements in the basic Mobile IPv6 route optimization
algorithm and its security, return routability, which is the basic theme of
the document. There is a very extensive academic literature on HMIP, FMIP,
and other local optimizations for Mobile IP handover, and none of this has
been cited or reviewed in this draft. Removing the material on this would
help to focus and shorten the draft.

Specific comments:

page 6: lightway and does not -> lightweight and does not

page 6: "On the other hand, the return routability procedure usually
consumes one round-trip time" - The number I've seen cited is 1.5 RTT on the
average.

Section 2.0: I believe Pekka Nikander has a MIP6 WG draft
(draft-ietf-mip6-ro-sec-02.txt) that discusses many of the issues that are
discussed in this and subsequent sections. This draft should be referenced
somewhere here.

Section 2.3, 2nd last para: I was looking here for the standard "ingress
filtering will handle redirection-based DoS attacks" here, and the
refutation of why that isn't practical. It might be useful to put in a
forward reference, since it is dealt with later in the paper.

Section 3.2, end of 1st para: The impact on the core Internet of
bidirectional tunneling is actually quite minimal given the amount of dark
fiber left over from the Boom. It has been estimated that less that 10% of
the cross-continent fiber in North America is lit, and the number is
probably similar for intercontinental and other long distance links in other
countries. There is of course still an issue with access networks, but the
real impact of always tunneling through the home agent is on RTT latency.
This is sometimes known as "the two Japanese in America" problem, where two
people from Japan come to America, and call each other through their Mobile
IP home agents back in Japan.

Section 3.2, begining of the 2nd para: I'm not clear what the relationship
between the CN and authorization for a home address has to do with
deployment of route optimization. There is an even more basic issue, that is
that modifications for route optimization which utilize end-to-end signaling
require that every CN in the IPv6 Internet support them. While we are yet
far away from widespread deployment of IPv6, the longer such end-to-end
optimizations are delayed, the less likely that every CN will support them.

Section 3.2, 3rd para: and so does without -> and does so without

Section 3.2, 5th para: The preconfigured keys draft should be cited here.

Section 3.2, 6th para: This paragraph misses the issue of CRL checks. These
could be a significant issue when using certificates for route optimization
security.

Section 3.2, 9th para: In my mind, the primary argument against depending on
ingress filtering is that there is no incentive - financial, regulatory, or
legal - for ISPs to deploy it. A diligent ISP will of course do so, but a
corrupt ISP might even have a financial incentive to not deploy it, if
redirection-based DoS attacks using route optimization ever become possible
and are exploited for financial gain. This has been an issue with spam, for
example. I think something to that effect needs to be said. While some
people might be offended by this, the need for security in the Internet
results from the fact that, lacking any incentives to the contrary, some
people will do bad things if they can get away with it and it can result in
financial gain. Most discussions of security ignore this basic fact of human
nature, and treat the problem like solar physics or something.

Section 3.2, 10th para: This section loses sight of the fact that malware
installed surreptitiously on a host may compromise it even if the host has a
trust relationship with the home agent service provider. The issue is not
the trust relationship but rather that the home agent service provider has a
record of who the user is and can cut them off if they start behaving badly.
Now how the home agent service provider is supposed to detect whether or not
a particular host is behaving badly is another story.

Section 3.3, 1st para: against the tree -> against the three

Section 3.3, 3rd para: This said -> That said

Section 3.3, 4th para: But here again could the attacker launch -> But here
again, the attacker can launch

Section 3.3, 5th para: that is called "space-and-time shift attacks" -> that
is called a "space-and-time-shift attack"
for a better point of time -> for a better point in time

Section 4.1, 2nd para: This isn't clear. If the MN sends a BU to the CN,
then it isn't a round trip, it's one way. I'm assuming here that the text
isn't including the HoTI/HoT, CoTI/CoT in that calculation. If so, then I
think the average would be 2 RTs, 1.5 for the RR signaling and 0.5 for the
BU.

Section 4.2, 3rd & 4th para: I've never been convinced that a mobile node
would want to keep optimized routes hot while it was in dormant mode, and
this example doesn't convince me either. Route optimization helps with RTT
latency, and such latency is an issue primarily in real time traffic. The
example given here, a messaging server (presumably IM), is a store and
forward system that will derive little benefit from keeping routes hot
during optimization. Even for real time traffic, like VoIP, the CN still has
to do SIP signaling to initiate the connection, and while there is some
amount of urgency to the signaling above a store and forward application, it
still is not going to suffer if the traffic is routed through the home
agent. The latency involved in initiating the IP connection with the dormant
mode mobile node through paging is likely to exceed any benefit from keeping
optimized routes hot.

Section 4.3, 1st para: lightway -> lightweight
In some cases, however, may better security be useful -> ????

Section 4.3, 2nd para: mobility management can the Internet as whole not ->
mobility management, the Internet as a whole can not

Section 5, meta comment:
One issue the entire document has ignored is route optimization for mobile
networks. As noted above, since end to end route optimization technquies
require support in every IPv6 node, a host-based route optimization
technique that is adopted for next-gen MIPv6 but doesn't support mobile
networks may preclude widespread use of route optimization for mobile
networks because it might be difficult to get the support in a broad enough
collection of IPv6 nodes. Section 6.3.2, paragraph 1 makes the argument that
the current set of new RO techniques is likely to be directed at specific
usage scenerios, but I'm not so sure that's likely to be the case.

Section 5, para 1: many enhancements techniques -> many enhancement
techniques

Section 5, para 1: Are the tradeoffs between universal applicablity v.s.
efficiency discussed in this paper anywhere? This would be the ideal paper
to have the discussion.

Section 5.1, para 2: IP-ddress -> IP-address
can anyway do without route optimization -> can do without route
optimization anyway

Section 5.1, para 3: Again, I've heard 1.5 RTT for this.

Section 5.2, para 1: same problem as in 5.1 para 2

Section 5.4, para 1: I've never heard the term "critical phase" used.

Section 5.4, para 2: One issue raised earlier in the paper was the frequency
of signaling. Here, it seems to be advocating doing a home address test
every 3.5 mintues regardless of whether movement is immanent or not. This
seems a contradiction.

anyway re-initiate the correspondent registration -> re-initiate the
correspondent registration anyway

Section 5.5, para 2: Later in the paper, you discuss this, but the
statistical uniqueness properties of CGAs suggest that the care-of test
might not be needed since the probability of another node having exactly the
same interface identifier is fairly low. I think you should state that here.
It is the same tradeoff that optimistic DAD makes. The argument you advance
later in the paper that the attacker can still mount an attack on the subnet
is irrelevent. An attacker can do that without using route optimization, by
creating a zombie and programming it to iterate through non-existant
addresses in the victim subnet.

Section 5.6, para 1: until it has been told about this -> until it has been
told.
are usually lost and must be transmitted -> are usually lost and must be
retransmitted

Section 5.7: I think it might be worthwhile to include a paragragh
describing how the mobile node's credit is measured. I recently attempted to
construct a bandwidth measuring algorithm and found it not so simple. There
are probably very simple ways to do it, but I think they may not be obvious
to the casual reader.

Section 5.7, para 5: Thus, its is the -> Thus, it is the

Section 5.7, para 5.7: I wonder if the Spot Check tokens aren't a potential
state depletion threat. Since they are essentially per flow state, an
attacker could iterate creating a bunch of flows until the victim's Spot
Check token storage was exhausted.

Section 5.8, para 2: it in general hard -> it is in general hard
Actually, I think it is impossible for the correspondent to know that two
home addresses are from the same node unless the interface identifier is the
same. The interface identifier is what is used for routing on the last hop
link, and so only it will determine if two packets with destination
addresses known to be home addresses and the same subnet prefix go to the
same node.

Section 5.9, para 4: RFC 3972 describes how to compute CGAs such that an
attacker can't claim ownership. It used the said subnet prefix trick, and
should probably be cited.

Section 5.10: This section seems to imply that the CoA test can be
eliminated with preconfiguration, but I think that is too optimistic. Even
if two nodes that trust each other initially are preconfigured, subsequently
one or the other can be infected with malware without the owner knowing and
become untrustworthy.

Section 6.2.2, para 2: The assumption that mobile nodes are fair-minded
turns out to be quite far stretching. -> ??????
from figure Figure 1, -> from Figure 1,
and a trust relationship for misuse prevention -> and an address
authorization for misuse prevention

Section 6.2.2, para 4: These things said, -> That said,
protocol bendable to different -> protocol customizable to different

Section 6.2.3: Here is the discussion of statistical uniqueness and its
effect on the need for the CoA test. The point about network attacks in the
2nd para is really irrelevant, as noted above.

Section 6.2.4, 4th para: that mobility-managment protocols -> that these
mobility-management protocols

Section 6.2.4: Can CBA somehow get rid of the need to re-authorize every 7
minutes? If the MN is building credit, then perhaps it doesn't need to
re-authorize because its ability to attack is limited by the credit. Of
course, the issue of the home address test would have to be addressed too,
but I think it worthwhile to explore this, since the signaling overhead of
RR is onerous.

Section 6.3.1: This section could be removed too.

Section 6.3.2: final, all-encompassing method -> widespread method
Actually, I disagree with this conclusion. I think the current crop of
limited applicability RO security protocols are likely to die from lack of
implementation and interest and a next gen protocol, possibly including CGA
and CBA, that is widely applicable and a big improvement on RR is likely to
have more success.

Section 6.3.2: One issue that I've never really seen dealt with is whether
or not RO is really needed. Nobody has measured this. Skype seems to get by
with lots of indirect routes For example, our experiments show that when we
make a Skype call from one node in our San Jose lab to another, it goes
through a supernode in Europe, yet the quality of the call is fine.
Everybody seems to be assuming this is a problem, but nobody seems to have
set up a network and actually measured whether it is *really* a problem,
with MOS scores, etc.













_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 26 23:25:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbVTx-00014e-0i; Thu, 26 May 2005 23:25:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DbVTv-00014U-OL
	for mip6@megatron.ietf.org; Thu, 26 May 2005 23:25:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09780
	for <mip6@ietf.org>; Thu, 26 May 2005 23:25:52 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbVmd-0006ye-Bi
	for mip6@ietf.org; Thu, 26 May 2005 23:45:16 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate7) with ESMTP id j4R3XlP7023044
	for <mip6@ietf.org>; Thu, 26 May 2005 20:33:47 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j4R3TmXD010452
	for <mip6@ietf.org>; Thu, 26 May 2005 22:29:48 -0500 (CDT)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <KPLC6G6Q>; Thu, 26 May 2005 22:25:50 -0500
Message-ID: <1B631E11D496D711BB2800065BFCB6A11B7A7084@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: mip6@ietf.org, mobopts@irtf.org
Date: Thu, 26 May 2005 22:25:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: 
Subject: [Mip6] Review Comments and Questions on
	draft-irtf-mobopts-ro-enhancemen ts-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2115103205=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

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

--===============2115103205==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5626B.C5E6D54C"

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_01C5626B.C5E6D54C
Content-Type: text/plain

Here are some comments and questions I have from reviewing the draft. 
 
Thanks,
Vidya
 
1. The draft provides a good, comprehensive overview of the security aspects of RO and the solution space in general. However, given that there is already a draft on RO security, perhaps the security aspects should be integrated with that draft and this draft should attempt to cover the solution space alone? 
 
2. Need for "fast" RO - The draft mentions in a few places (including section 4) that one of the objectives for RO is latency optimization. I belong to the group that is yet to be convinced that there is a real need for "fast" RO. In my mind, there is a need for fast handoffs, but not necessarily fast RO. I don't think that RO is going to satisfy the latency requirements of real-time applications. Link layer mechanisms are defining methods to reduce the handoff latency to less than 100ms or so. Such enhancements are useful during inter-subnet handoffs only if the network layer latency can be reduced to adding very marginal latency on top of that. Do we really think RO is going to buy us that? Given that any design for RO cannot control the relative positions of the CN and the MN, it doesn't seem like any RO solution can claim that. The need for such applications really drives us towards FMIP-like approaches. 
 
I still think RO can be useful - when long periods of traffic exchange happens between an MN and CN, it may be better to get away from triangular routing. I noticed that James brought up the point of almost ubiquitous wireline bandwidth perhaps eliminating the need for RO. While that is a very valid argument against the real need for RO, I think it will still be good to design the support for RO, before widespread deployment of CNs that don't support it. 
 
I am only questioning the need for latency reduction as a design objective for an RO solution. 
 
3. One of the situations in which RO can be useful is when the RO solution allows the MN and CN to continue communication during a period of HA unavailability (failure, for e.g.). The current RR solution does not achieve this, due to the necessity for short lifetimes and hence the need for home address tests via the HA every so often. It may be worthwhile adding this to the design goals for the solution. 
 
4. Section 3.3 (last paragraph) mentions the fact that the current RR solution trades off protection against attacks on CN's processing capacity for protection against CN's memory. Perhaps an RO solution can be flexible enough to allow the CN to determine what trade off makes sense in a particular case? 
 
5. Section 6.2.1 talks about HMIP and FMIP-like proposals. I am not sure I understand how such proposals can replace RO. For e.g., the use of FMIP will remove stringent latency requirements on RO, but not provide a solution for RO itself, right? 
 

------_=_NextPart_001_01C5626B.C5E6D54C
Content-Type: text/html
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05U
RU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9VVMtQVNDSUkiPg0KPFRJVExFPk1lc3NhZ2U8L1RJVExF
Pg0KDQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4wMC4yODAwLjE0OTgiIG5hbWU9R0VORVJBVE9S
PjwvSEVBRD4NCjxCT0RZPg0KPERJVj48IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9y
bWF0IC0tPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPkhlcmUgYXJlIA0Kc29tZSBjb21tZW50cyBh
bmQgcXVlc3Rpb25zIEkgaGF2ZSBmcm9tIHJldmlld2luZyB0aGUgZHJhZnQuIDwvRk9OVD48L0RJ
Vj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5UaGFua3MsPC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBmYWNlPUFyaWFsIHNpemU9Mj5WaWR5YTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1B
cmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNp
emU9Mj4xLiBUaGUgZHJhZnQgcHJvdmlkZXMgYSBnb29kLCBjb21wcmVoZW5zaXZlIA0Kb3ZlcnZp
ZXcgb2YgdGhlIHNlY3VyaXR5IGFzcGVjdHMgb2YgUk8gYW5kIHRoZSBzb2x1dGlvbiBzcGFjZSBp
biBnZW5lcmFsLiANCkhvd2V2ZXIsIGdpdmVuIHRoYXQgdGhlcmUgaXMgYWxyZWFkeSBhIGRyYWZ0
IG9uIFJPIHNlY3VyaXR5LCBwZXJoYXBzIHRoZSANCnNlY3VyaXR5IGFzcGVjdHMgc2hvdWxkIGJl
IGludGVncmF0ZWQgd2l0aCB0aGF0IGRyYWZ0IGFuZCB0aGlzIGRyYWZ0IHNob3VsZCANCmF0dGVt
cHQgdG8gY292ZXIgdGhlIHNvbHV0aW9uIHNwYWNlIGFsb25lPyA8L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQg
ZmFjZT1BcmlhbCBzaXplPTI+Mi4gTmVlZCBmb3IgImZhc3QiIFJPIC0gVGhlIGRyYWZ0IG1lbnRp
b25zIGluIGEgZmV3IA0KcGxhY2VzIChpbmNsdWRpbmcgc2VjdGlvbiA0KSB0aGF0IG9uZSBvZiB0
aGUgb2JqZWN0aXZlcyBmb3IgUk8gaXMgbGF0ZW5jeSANCm9wdGltaXphdGlvbi4gPC9GT05UPjxG
T05UIGZhY2U9QXJpYWwgc2l6ZT0yPkkgYmVsb25nIHRvIHRoZSBncm91cCB0aGF0IGlzIHlldCAN
CnRvIGJlIGNvbnZpbmNlZCB0aGF0IHRoZXJlIGlzIGEgcmVhbCBuZWVkIGZvciAiZmFzdCIgUk8u
IEluIG15IG1pbmQsIHRoZXJlIGlzIGEgDQpuZWVkIGZvciBmYXN0IGhhbmRvZmZzLCBidXQgbm90
IG5lY2Vzc2FyaWx5IGZhc3QgUk8uIEkgZG9uJ3QgdGhpbmsgdGhhdCBSTyBpcyANCmdvaW5nIHRv
IHNhdGlzZnkgdGhlIGxhdGVuY3kgcmVxdWlyZW1lbnRzIG9mIHJlYWwtdGltZSBhcHBsaWNhdGlv
bnMuIExpbmsgbGF5ZXIgDQptZWNoYW5pc21zIGFyZSBkZWZpbmluZyBtZXRob2RzIHRvIHJlZHVj
ZSB0aGUgaGFuZG9mZiBsYXRlbmN5IHRvIGxlc3MgdGhhbiAxMDBtcyANCm9yIHNvLiBTdWNoIGVu
aGFuY2VtZW50cyBhcmUgdXNlZnVsIGR1cmluZyBpbnRlci1zdWJuZXQgaGFuZG9mZnMgb25seSBp
ZiB0aGUgDQpuZXR3b3JrIGxheWVyIGxhdGVuY3kgY2FuIGJlIHJlZHVjZWQgdG8gYWRkaW5nIHZl
cnkgbWFyZ2luYWwgbGF0ZW5jeSBvbiB0b3Agb2YgDQp0aGF0LiBEbyB3ZSByZWFsbHkgdGhpbmsg
Uk8gaXMgZ29pbmcgdG8gYnV5IHVzIHRoYXQ/IEdpdmVuIHRoYXQgYW55IGRlc2lnbiBmb3IgDQpS
TyBjYW5ub3QgY29udHJvbCB0aGUgcmVsYXRpdmUgcG9zaXRpb25zIG9mIHRoZSBDTiBhbmQgdGhl
IE1OLCBpdCBkb2Vzbid0IHNlZW0gDQpsaWtlIGFueSBSTyBzb2x1dGlvbiBjYW4gY2xhaW0gdGhh
dC4gVGhlIG5lZWQgZm9yIHN1Y2ggYXBwbGljYXRpb25zIHJlYWxseSANCmRyaXZlcyB1cyB0b3dh
cmRzIEZNSVAtbGlrZSBhcHByb2FjaGVzLiA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9
QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBz
aXplPTI+SSBzdGlsbCB0aGluayBSTyBjYW4gYmUgdXNlZnVsIC0gd2hlbiBsb25nIHBlcmlvZHMg
DQpvZiB0cmFmZmljIGV4Y2hhbmdlIGhhcHBlbnMgYmV0d2VlbiBhbiBNTiBhbmQgQ04sIGl0IG1h
eSBiZSBiZXR0ZXIgdG8gZ2V0IGF3YXkgDQpmcm9tIHRyaWFuZ3VsYXIgcm91dGluZy4gSSBub3Rp
Y2VkIHRoYXQgSmFtZXMgYnJvdWdodCB1cCB0aGUgcG9pbnQgb2YgYWxtb3N0IA0KdWJpcXVpdG91
cyB3aXJlbGluZSBiYW5kd2lkdGggcGVyaGFwcyBlbGltaW5hdGluZyB0aGUgbmVlZCBmb3IgUk8u
Jm5ic3A7V2hpbGUgDQp0aGF0Jm5ic3A7aXMgYSB2ZXJ5IHZhbGlkIGFyZ3VtZW50IGFnYWluc3Qg
dGhlIHJlYWwgbmVlZCBmb3IgUk8sIEkgdGhpbmsgaXQgd2lsbCANCnN0aWxsIGJlIGdvb2QgdG8g
ZGVzaWduIHRoZSBzdXBwb3J0IGZvciBSTywgYmVmb3JlIHdpZGVzcHJlYWQgZGVwbG95bWVudCBv
ZiBDTnMgDQp0aGF0IGRvbid0IHN1cHBvcnQgaXQuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQg
ZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFy
aWFsIHNpemU9Mj5JIGFtIG9ubHkgcXVlc3Rpb25pbmcgdGhlIG5lZWQgZm9yIGxhdGVuY3kgDQpy
ZWR1Y3Rpb24gYXMgYSBkZXNpZ24gb2JqZWN0aXZlIGZvciBhbiBSTyBzb2x1dGlvbi4gPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjMuIE9uZSBvZiB0aGUgc2l0dWF0aW9ucyBp
biB3aGljaCBSTyBjYW4gYmUgdXNlZnVsIA0KaXMgd2hlbiB0aGUgUk8gc29sdXRpb24gYWxsb3dz
IHRoZSBNTiBhbmQgQ04gdG8gY29udGludWUgY29tbXVuaWNhdGlvbiBkdXJpbmcgYSANCnBlcmlv
ZCBvZiBIQSB1bmF2YWlsYWJpbGl0eSAoZmFpbHVyZSwgZm9yIGUuZy4pLiBUaGUgY3VycmVudCBS
UiBzb2x1dGlvbiBkb2VzIA0Kbm90IGFjaGlldmUgdGhpcywgZHVlIHRvIHRoZSBuZWNlc3NpdHkg
Zm9yIHNob3J0IGxpZmV0aW1lcyBhbmQgaGVuY2UgdGhlIG5lZWQgDQpmb3IgaG9tZSBhZGRyZXNz
IHRlc3RzIHZpYSB0aGUgSEEgZXZlcnkgc28gb2Z0ZW4uIEl0IG1heSBiZSB3b3J0aHdoaWxlIGFk
ZGluZyANCnRoaXMgdG8gdGhlIGRlc2lnbiBnb2FscyBmb3IgdGhlIHNvbHV0aW9uLiA8L0ZPTlQ+
PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+NC4gU2VjdGlvbiAzLjMgKGxhc3QgcGFyYWdy
YXBoKSBtZW50aW9ucyB0aGUgZmFjdCANCnRoYXQgdGhlIGN1cnJlbnQgUlIgc29sdXRpb24gdHJh
ZGVzIG9mZiBwcm90ZWN0aW9uIGFnYWluc3QgYXR0YWNrcyBvbiBDTidzIA0KcHJvY2Vzc2luZyBj
YXBhY2l0eSBmb3IgcHJvdGVjdGlvbiBhZ2FpbnN0IENOJ3MgbWVtb3J5LiBQZXJoYXBzIGFuIFJP
IHNvbHV0aW9uIA0KY2FuIGJlIGZsZXhpYmxlIGVub3VnaCB0byBhbGxvdyB0aGUgQ04gdG8gZGV0
ZXJtaW5lIHdoYXQgdHJhZGUgb2ZmIG1ha2VzIHNlbnNlIA0KaW4gYSBwYXJ0aWN1bGFyIGNhc2U/
IDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNw
OzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj41LiBTZWN0aW9uIDYuMi4xIHRh
bGtzIGFib3V0IEhNSVAgYW5kIEZNSVAtbGlrZSANCnByb3Bvc2Fscy4gSSBhbSBub3Qgc3VyZSBJ
IHVuZGVyc3RhbmQgaG93IHN1Y2ggcHJvcG9zYWxzIGNhbiByZXBsYWNlIFJPLiBGb3IgDQplLmcu
LCB0aGUgdXNlIG9mIEZNSVAgd2lsbCByZW1vdmUgc3RyaW5nZW50IGxhdGVuY3kgcmVxdWlyZW1l
bnRzIG9uIFJPLCBidXQgbm90IA0KcHJvdmlkZSBhIHNvbHV0aW9uIGZvciBSTyBpdHNlbGYsIHJp
Z2h0PyA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4m
bmJzcDs8L0RJVj48L0JPRFk+PC9IVE1MPg0K

------_=_NextPart_001_01C5626B.C5E6D54C--


--===============2115103205==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============2115103205==--




From mip6-bounces@ietf.org Fri May 27 03:43:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbZUw-0008QI-Fd; Fri, 27 May 2005 03:43:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DbZUs-0008QD-9j
	for mip6@megatron.ietf.org; Fri, 27 May 2005 03:43:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18513
	for <mip6@ietf.org>; Fri, 27 May 2005 03:43:08 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]
	ident=[U2FsdGVkX19SCSFAkNyEpzLsYxK3l0IDigemB11hWVI=])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbZnc-00041e-9r
	for mip6@ietf.org; Fri, 27 May 2005 04:02:33 -0400
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1DbZUj-000219-AF; Fri, 27 May 2005 09:43:07 +0200
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1DbZUi-0003rP-AR; Fri, 27 May 2005 09:43:00 +0200
Message-ID: <4296CF83.1080000@tm.uka.de>
Date: Fri, 27 May 2005 09:42:59 +0200
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: MIP6 <mip6@ietf.org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -18.0 (------------------)
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Content-Transfer-Encoding: 7bit
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: [Mip6] Francis' Review of draft-irtf-mobopts-ro-enhancements (was
 Re: FW: Please review draft-irtf-mobopts-ro-enhancements-00.txt)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

I probably should have sent this to the MIP6 mailing list, too.

- Christian


-------- Original Message --------
Subject: Francis' Review of draft-irtf-mobopts-ro-enhancements (was Re: 
FW: Please review draft-irtf-mobopts-ro-enhancements-00.txt)
Date: Fri, 27 May 2005 09:22:23 +0200
From: Christian Vogt <chvogt@tm.uka.de>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
CC: Basavaraj.Patil@nokia.com, Jari Arkko <jari.arkko@ericsson.com>, 
MOBOPTS <mobopts@irtf.org>

Hi Francis,

first of all, thanks for reviewing the document and commenting on it.
We revised the document and put the new, preliminary version here:

http://doc.tm.uka.de/2005/draft-irtf-mobopts-ro-enhancements-01-pre.txt

BTW, Vidya and James both did a review as well, so there is going to be
another round of revision.

Below are my responses to your, Francis', comments.

> - abstract: IMHO the goals of improvements/alternatives are in the
> wrong order: signaling messages/latency/etc can be improved only
> because the security is better. (same about 4.x section order)

Hmm, there wasn't actually an intention to prioritize the proposals,
Francis.  But it might be wise to do so.  Do you think that the order

(1) low latency
(2) increased security
(3) reduced signaling overhead

is capable of reaching agreement?  It seems that there is a common
ground to at least not increase the latency of standard Mobile IPv6.  In
other words, many of the described proposals have merits in terms of
reduced latency, even if their primary goal is to increase security.
(OMIPv6 is a good example.  If you combine it with Credit-Based
Authorization, which is what we will do in Mipshop, you get both, higher
security and lower latency.)

> - 1.introduction: to put HIP at the same level than Mobile IPv6 and 
> Mobile IP is a clear bias.

Ok, this document is about Mobile IPv6, so it should be made clear in
the introduction.  Re-wrote that part.

> - 1.introduction: IKE is only a standard way to dynamically establish
>  security associations. (same comment about section 3)

Right.

> - 2.3flooding attacks: arguments about amplification are specious: 
> the current real world threat is DDoS and the main defense against 
> it, the ingress filtering (BCPs 38 and 84), i.e., we are either 
> vulnerable or not vulnerable to both DDoS and RO reflection attacks 
> (modulo the use of "real" alternate care-of addresses). So I consider
>  the 2.3 section as delibarately incomplete.

Francis, I added a sub-section 1.1, "A Note on Source Address
Filtering", to the introduction that attends to the ongoing discussion
about whether or not ingress filtering is a suitable replacement for
care-of-address tests.  The estimate of many folks, that it is not, has
shaped the design of Mobile IPv6, and it was a basis for this document, too.

But you are right that one should render the assumption clearer, and
justify it, within this document.  I think that the new sub-section
accomplishes this.  Its signification is the same as section 1.1.1 in
draft-ietf-mip6-ro-sec-02, which Gabriel added for similar reasons.

I also added draft-dupont-mipv6-3bombing-01 to the references.

> - 3.1registration procedure: ESP (with non-null encryption and 
> authentication) support is mandatory for HAs and use is recommended 
> for mobile nodes. At least the word "optionally" before encrypted is
> wrong.

Are you positive, Francis?  As far as I know, use of ESP encryption is
not mandatory for both MN or HA.  This is what RFC 3775 says about this:

++++
5.1.  Binding Updates to Home Agents

    The mobile node and the home agent MUST use an IPsec security
    association to protect the integrity and authenticity of the Binding
    Updates and Acknowledgements.  Both the mobile nodes and the home
    agents MUST support and SHOULD use the Encapsulating Security Payload
    (ESP) [6] header in transport mode and MUST use a non-NULL payload
    authentication algorithm to provide data origin authentication,
    connectionless integrity and optional anti-replay protection.  Note
    that Authentication Header (AH) [5] is also possible but for brevity
    not discussed in this specification. [...]
++++

And RFC 3776 says in the introduction:

++++
    The control traffic between the mobile node and the home agent
    requires message authentication, integrity, correct ordering and
    anti-replay protection.  The mobile node and the home agent must have
    an IPsec security association to protect this traffic.  [...]
++++

I am not quite sure how this relates to what it says in section 4.3,
however:

++++
    The following requirements apply to both home agents and mobile
    nodes:

       [...]
       Mandatory support for encryption and integrity protection
       algorithms is as defined in RFC 2401 [2], RFC 2402 [8], and RFC
       2406 [3].  [...]
++++

Can you comment on this?

> - 3.2goals and assumptions: the discussion about the size of the PKI
> is misleading: first the number of certificates is the number of
> mobile nodes, not the number of possible home addresses [...]

Right, it's done.

> nodes, not the number of possible home addresses, second X.509 PKIs 
> are hierarchical and can handle very large numbers of end entities (I
> know examples of PKIs with millions of certificates). The only real
> issue is it seems a global PKI is not wanted by people (and not for
> security reasons :-) so should not be considered as available in any
> time scale.

The scalability issue is not so much meant to be a technical one, but is
more about acceptance, administrative feasibility, and performance.
But, yes, the text might have been a bit imprecise here.  So I
re-wrote it with your concerns in mind.  Here are the new paragraphs
from section 3.2:

++++
    Public-key cryptography requires some external binding between a
    public key and the identity this public key is supposed to protect.
    Certificates issued by a trusted authority can usually do this job,
    although there is little experience with using home addresses as
    identifiers in the certificates.  (E.g., the home address could be
    placed into a certificate's Subject AltName field.)  Given a
    certificate that binds a public key to a home address, the owner of
    this home address can authenticate itself as such by signing some
    arbitrary piece of data with its private key.  Since everybody can
    verify the signature with the mobile node's public key, this proves,
    in the end, that the mobile node actually knows the private key
    complementing the certified public key, and the certificate authority
    vouches that the public key, in turn, is associated with the home
    address.  The eventual decision to not depend the security of Mobile
    IPv6 on public-key cryptography was sparked by problems related to
    scalability, performance, administrative feasibility, and acceptance
    as explained next.

    There are differing opinions on whether public-key infrastructures
    (PKIs) could scale up to hundreds of millions of mobile nodes.  Some
    people argue they do, as there are already examples of PKIs with
    millions of certificates.  But apart from an increase just in the
    number of certificates, a shift in application patterns can be
    anticipated as well:  Public-key infrastructures (PKI) are nowadays
    used only for the types of applications that really can't go without
    the strong protection certificates provide.  But as soon as mobility
    joins the set of applications, not only does the number of nodes
    using certificates increase, but the new users, the mobile nodes,
    would also most likely have their certificates checked at a much
    higher frequency than other nodes use to do for other applications.
    It is unclear whether PKIs could handle this new workload.

    Another issue is performance from the user's perspective:
    Certificate verification takes some time, especially when multiple
    levels of PKI hierarchies are involved.  If this delay happens only
    at the beginning of a session, most users would probably come to
    terms with it.  If it happens in the middle of a session, or the
    session is very short-term anyway, it could have a disturbing effect.

    Moreover, while it is conceivable that mobile users be well-disposed
    to configuring certificates into their mobile nodes, busy servers
    functioning as correspondent nodes might not be willing to check the
    mobile nodes' certificates depending on the service they provide.
    Besides, it might not be easy to coordinate address assignment with
    certificate issuing.  Typically, the entities responsible for these
    tasks are not the same.  And finally, the bigger a PKI grows, the
    more attractive it becomes as an attack target, endangering the
    Internet as a whole.
++++

> - 3.2goals and assumptions: the argument that authentication can not
> help against flooding attacks is wrong: authentication can help but
> at the condition the care-of address is covered. This is usually not
> the case but this is a different argument.

Do you think about care-of addresses that mobile nodes own, or reserve,
at different networks to where they might roam at some point in the
future?  Or do you have in mind an extension to SeND through which a
remote correspondent node could verify a mobile node's presence at the
care-of address?  Note that CGAs alone do not solve the issue because
the addresses can be configured at any place.

I'm not sure if I see your point.  Could you please clarify this?

> - 3.2goals and assumptions: I reviewed a research paper proposing 
> certificate-based authorization of care-of addresses so the
> discussion about this concluding it is not possible is wrong.

Ah, ok.  So you mean special care-of addresses, owned by a mobile node,
which are verifiable through certificates.  Or you allow the
mobile node to configure any care-of address---with certain prefixes or
without contraints at all---and have some entity vouch for the mobile
node's sincerity.  Draft-qiu-mip6-certificated-binding-update-03.txt
proposes something like this, too.

> - 3.2...: the decision about ingress filtering refers to
> routing-routability design *only*. The idea that ingress filtering
> can't help and care-of address test is necessary is the own opinion
> of authors.

Ok, see new sub-section 1.1 for this matter.

> - 4.2signaling optimizations: bps is not an ISO unit.

Should be understandable now. ;)

> - 5.1ip-address tests: I suggest to add correspondent-driven tests to
>  this section, cf draft-dupont-mipv6-rrcookie-00.txt)

Agreed.  I added this paragraph to section 5.1:

++++
A home-address test can most efficiently be initiated by the mobile node
itself, as the correspondent node can thus delay state creation until
the mobile node has authenticated.  Yet, conceptually, either the mobile
node or the correspondent node could start a care-of-address test.  RFC
3775 uses mobile-node-initiated IP-address tests, whereas
[draft-dupont-mipv6-rrcookie] proposes a way to have the correspondent
node send the first message.  [draft-ietf-hip-mm] follows this latter
approach as well.  The correspondent-node-driven approach has advantages
when authentication is done through other means than a home-address
test.  Since RFC 3775 does use the home-address test for authentication,
letting the mobile node initiate both IP-address test allows for more
efficient parallelization.
++++

> - 5.10: acess -> access

Thanks.

> I have a real concern about this document: its title is for a WG
> document, reflecting a consensus of the WG, when what I can find in
> it is mainly the own opinion of authors.

Well, this is why we do reviews. ;)

I think there are now some substantial changes to the document (see the
link at the top of this email).  Underlying assumption are more clearly
expressed now, additional techniques have been included, and some
imprecisenesses have been corrected.  With the new "Note on Source
Address Filtering" within the Introduction, readers will become aware
that there is an ongoing debate about this topic, and that
assumptions about it may change as technology evolves.

Once again, thanks for the review!

Kind regards,

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Francis Dupont wrote:
> Here are some notes taken when I received the call for review. I'll
> summarize in the list.
> 
> Some comments about draft-irtf-mobopts-ro-enhancements-00.txt: -
> abstract: IMHO the goals of improvements/alternatives are in the
> wrong order: signaling messages/latency/etc can be improved only
> because the security is better. (same about 4.x section order) -
> 1.introduction: to put HIP at the same level than Mobile IPv6 and 
> Mobile IP is a clear bias. - 1.introduction: IKE is only a standard
> way to dynamically establish security associations. (same comment
> about section 3) - 2.3flooding attacks: arguments about amplification
> are specious: the current real world threat is DDoS and the main
> defense against it, the ingress filtering (BCPs 38 and 84), i.e., we
> are either vulnerable or not vulnerable to both DDoS and RO
> reflection attacks (modulo the use of "real" alternate care-of
> addresses). So I consider the 2.3 section as delibarately incomplete.
>  - 3.1registration procedure: ESP (with non-null encryption and 
> authentication) support is mandatory for HAs and use is recommended 
> for mobile nodes. At least the word "optionally" before encrypted is
> wrong. - 3.2goals and assumptions: the discussion about the size of
> the PKI is misleading: first the number of certificates is the number
> of mobile nodes, not the number of possible home addresses, second
> X.509 PKIs are hierarchical and can handle very large numbers of end
> entities (I know examples of PKIs with millions of certificates). The
> only real issue is it seems a global PKI is not wanted by people (and
>  not for security reasons :-) so should not be considered as
> available in any time scale. - 3.2goals and assumptions: the argument
> that authentication can not help against flooding attacks is wrong:
> authentication can help but at the condition the care-of address is
> covered. This is usually not the case but this is a different
> argument. - 3.2goals and assumptions: I reviewed a research paper
> proposing certificate-based authorization of care-of addresses so the
> discussion about this concluding it is not possible is wrong. -
> 3.2...: the decision about ingress filtering refers to
routing-routability
> design *only*. The idea that ingress filtering can't help and care-of
>  address test is necessary is the own opinion of authors. -
> 4.2signaling optimizations: bps is not an ISO unit. - 5.1ip-address
> tests: I suggest to add correspondent-driven tests to this section,
> cf draft-dupont-mipv6-rrcookie-00.txt) - 5.10: acess -> access ...
> 
> I have a real concern about this document: its title is for a WG
> document, reflecting a consensus of the WG, when what I can find in
> it is mainly the own opinion of authors.
> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 09:53:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbfHg-0004EC-BW; Fri, 27 May 2005 09:53:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbfHe-0004Dp-Gc; Fri, 27 May 2005 09:53:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12230;
	Fri, 27 May 2005 09:53:52 -0400 (EDT)
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DbfaR-0003cF-37; Fri, 27 May 2005 10:13:21 -0400
Received: from eamrcnt751.exu.ericsson.se (eamrcnt751.exu.ericsson.se
	[138.85.133.52])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id j4RDsHIW007104;
	Fri, 27 May 2005 08:54:17 -0500
Received: by eamrcnt751.exu.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <L419CY0N>; Fri, 27 May 2005 08:53:40 -0500
Received: from [142.133.116.21] (Nautilus.dyn.lmc.ericsson.se
	[142.133.116.21]) by EAMMLEX034.lmc.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id K0LKHXJ4; Fri, 27 May 2005 09:53:37 -0400
In-Reply-To: <1B631E11D496D711BB2800065BFCB6A11B7A7084@il02exm13>
References: <1B631E11D496D711BB2800065BFCB6A11B7A7084@il02exm13>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7B8E46D8-8C86-4353-B416-D55D8772BB85@ericsson.com>
Content-Transfer-Encoding: 7bit
From: Wassim Haddad <Wassim.Haddad@ericsson.com>
Subject: Re: [Mip6] Review Comments and Questions on
	draft-irtf-mobopts-ro-enhancemen ts-00.txt
Date: Fri, 27 May 2005 09:56:48 -0400
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, mobopts@irtf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Vidya,

On 26-May-05, at 11:25 PM, Narayanan Vidya-CVN065 wrote:

> 3. One of the situations in which RO can be useful is when the RO  
> solution allows the MN and CN to continue communication during a  
> period of HA unavailability (failure, for e.g.). The current RR  
> solution does not achieve this, due to the necessity for short  
> lifetimes and hence the need for home address tests via the HA  
> every so often. It may be worthwhile adding this to the design  
> goals for the solution.

=> In OMIPv6, you need to do only *one* HoA test at the beginning.  
The shared secret, i.e., SKbm, lifetime is set to 24 hours so that  
you don't need to
exchange HoTI/HoT messages during this period.


Regards,

Wassim H.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 10:03:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbfQr-0008Pm-3h; Fri, 27 May 2005 10:03:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DbfQp-0008Ph-4N
	for mip6@megatron.ietf.org; Fri, 27 May 2005 10:03:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13276
	for <mip6@ietf.org>; Fri, 27 May 2005 10:03:21 -0400 (EDT)
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dbfjb-0003y6-N6
	for mip6@ietf.org; Fri, 27 May 2005 10:22:49 -0400
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se
	[138.85.133.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id j4RE37wh012164;
	Fri, 27 May 2005 09:03:07 -0500
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service
	(5.5.2656.59) id <L41ZGC5S>; Fri, 27 May 2005 08:58:32 -0500
Received: from [142.133.116.21] (Nautilus.dyn.lmc.ericsson.se
	[142.133.116.21]) by EAMMLEX034.lmc.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id K0LKHXMT; Fri, 27 May 2005 10:03:04 -0400
In-Reply-To: <4296CF83.1080000@tm.uka.de>
References: <4296CF83.1080000@tm.uka.de>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3B4E49F6-5C00-4F3E-84DF-B8154EDCD697@ericsson.com>
Content-Transfer-Encoding: 7bit
From: Wassim Haddad <Wassim.Haddad@ericsson.com>
Subject: Re: [Mip6] Francis' Review of draft-irtf-mobopts-ro-enhancements (was
	Re: FW: Please review draft-irtf-mobopts-ro-enhancements-00.txt)
Date: Fri, 27 May 2005 10:06:16 -0400
To: Christian Vogt <chvogt@tm.uka.de>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: MIP6 <mip6@ietf.org>, Basavaraj Patil <basavaraj.patil@nokia.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Jari Arkko <jari.arkko@kolumbus.fi>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Christian,

On 27-May-05, at 3:42 AM, Christian Vogt wrote:

> It seems that there is a common ground to at least not increase the  
> latency of standard Mobile IPv6.  In
> other words, many of the described proposals have merits in terms  
> of reduced latency, even if their
> primary goal is to increase security. (OMIPv6 is a good example.   
> If you combine it with Credit-Based
> Authorization, which is what we will do in Mipshop, you get both,  
> higher security and lower latency.)

=> IMHO, you also get lower latency with OMIPv6 alone, in addition to  
getting higher security, since you
don't need to do the HoTI/HoT exchange.


Regards,

Wassim H.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 10:13:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dbfb1-0001Xf-63; Fri, 27 May 2005 10:13:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dbfb0-0001X7-2K; Fri, 27 May 2005 10:13:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14644;
	Fri, 27 May 2005 10:13:52 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]
	ident=[U2FsdGVkX1+yFIdyZHnznu9Y3Q6u36UBAJc7JOuepK8=])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dbftn-0004B5-4c; Fri, 27 May 2005 10:33:20 -0400
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1Dbfar-0006lE-Rq; Fri, 27 May 2005 16:13:49 +0200
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by irams1.ira.uni-karlsruhe.de with esmtps 
	id 1Dbfao-00042g-N5; Fri, 27 May 2005 16:13:42 +0200
Message-ID: <42972B16.9000801@tm.uka.de>
Date: Fri, 27 May 2005 16:13:42 +0200
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Wassim Haddad <Wassim.Haddad@ericsson.com>
Subject: Re: [Mip6] Francis' Review of draft-irtf-mobopts-ro-enhancements
	(was Re: FW: Please review draft-irtf-mobopts-ro-enhancements-00.txt)
References: <4296CF83.1080000@tm.uka.de>
	<3B4E49F6-5C00-4F3E-84DF-B8154EDCD697@ericsson.com>
In-Reply-To: <3B4E49F6-5C00-4F3E-84DF-B8154EDCD697@ericsson.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -19.6 (-------------------)
X-Spam-Status: No
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: MIP6 <mip6@ietf.org>, tm-ro2@tm.uka.de,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>, MOBOPTS <mobopts@irtf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 > => IMHO, you also get lower latency with OMIPv6 alone, in addition to
 > getting higher security, since you
 > don't need to do the HoTI/HoT exchange.


Hi Wassim,

you are right.  The path through the HA is longer than the direct one in 
many, probably most, scenarios.

OMIPv6 without CBA reduces the overall latency by the difference between 
the HoA-test latency and the CoA-test latency.  OMIPv6 with CBA reduces 
it by the maximum of the HoA-test latency and the CoA-test latency.

Thanks for correcting this.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Wassim Haddad wrote:
> Hello Christian,
> 
> On 27-May-05, at 3:42 AM, Christian Vogt wrote:
> 
>> It seems that there is a common ground to at least not increase the  
>> latency of standard Mobile IPv6.  In
>> other words, many of the described proposals have merits in terms  of 
>> reduced latency, even if their
>> primary goal is to increase security. (OMIPv6 is a good example.   If 
>> you combine it with Credit-Based
>> Authorization, which is what we will do in Mipshop, you get both,  
>> higher security and lower latency.)
> 
> 
> => IMHO, you also get lower latency with OMIPv6 alone, in addition to  
> getting higher security, since you
> don't need to do the HoTI/HoT exchange.
> 
> 
> Regards,
> 
> Wassim H.


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 11:17:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dbgar-0006s2-IV; Fri, 27 May 2005 11:17:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dbgap-0006rm-MU
	for mip6@megatron.ietf.org; Fri, 27 May 2005 11:17:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20221
	for <mip6@ietf.org>; Fri, 27 May 2005 11:17:45 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dbgtd-0005aA-GU
	for mip6@ietf.org; Fri, 27 May 2005 11:37:14 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate7) with ESMTP id j4RFPZP7025352
	for <mip6@ietf.org>; Fri, 27 May 2005 08:25:35 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j4RFLc2O007209
	for <mip6@ietf.org>; Fri, 27 May 2005 10:21:38 -0500 (CDT)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <KPLC6MXZ>; Fri, 27 May 2005 10:17:39 -0500
Message-ID: <1B631E11D496D711BB2800065BFCB6A11B7A7086@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Wassim Haddad'" <Wassim.Haddad@ericsson.com>
Subject: RE: [Mip6] Review Comments and Questions on draft-irtf-mobopts-ro
	-enhancemen ts-00.txt
Date: Fri, 27 May 2005 10:17:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: mip6@ietf.org, mobopts@irtf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Wassim,
Yes, this seems to be the case. I did not see this point brought out in draft-irtf-mobopts-ro-enhancements. It might be good to add some text about this in the draft. 

Regards,
Vidya

> -----Original Message-----
> From: Wassim Haddad [mailto:Wassim.Haddad@ericsson.com] 
> Sent: Friday, May 27, 2005 8:57 AM
> To: Narayanan Vidya-CVN065
> Cc: mip6@ietf.org; mobopts@irtf.org
> Subject: Re: [Mip6] Review Comments and Questions on 
> draft-irtf-mobopts-ro-enhancemen ts-00.txt
> 
> 
> Hello Vidya,
> 
> On 26-May-05, at 11:25 PM, Narayanan Vidya-CVN065 wrote:
> 
> > 3. One of the situations in which RO can be useful is when the RO
> > solution allows the MN and CN to continue communication during a  
> > period of HA unavailability (failure, for e.g.). The current RR  
> > solution does not achieve this, due to the necessity for short  
> > lifetimes and hence the need for home address tests via the HA  
> > every so often. It may be worthwhile adding this to the design  
> > goals for the solution.
> 
> => In OMIPv6, you need to do only *one* HoA test at the beginning.  
> The shared secret, i.e., SKbm, lifetime is set to 24 hours so that  
> you don't need to
> exchange HoTI/HoT messages during this period.
> 
> 
> Regards,
> 
> Wassim H.
> 

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 11:58:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbhEE-0006vC-Ow; Fri, 27 May 2005 11:58:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbhEC-0006sN-2Y; Fri, 27 May 2005 11:58:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22441;
	Fri, 27 May 2005 11:58:25 -0400 (EDT)
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DbhX0-0006R1-1q; Fri, 27 May 2005 12:17:55 -0400
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se
	[138.85.133.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id j4RFwF9C018492;
	Fri, 27 May 2005 10:58:15 -0500
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service
	(5.5.2656.59) id <L41ZG1R6>; Fri, 27 May 2005 10:53:40 -0500
Received: from [142.133.116.21] (Nautilus.dyn.lmc.ericsson.se
	[142.133.116.21]) by EAMMLEX034.lmc.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id K0LKHYHR; Fri, 27 May 2005 11:58:13 -0400
In-Reply-To: <42972B16.9000801@tm.uka.de>
References: <4296CF83.1080000@tm.uka.de>
	<3B4E49F6-5C00-4F3E-84DF-B8154EDCD697@ericsson.com>
	<42972B16.9000801@tm.uka.de>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B3A7C4BF-1753-427C-B94C-03454EF1F69D@ericsson.com>
Content-Transfer-Encoding: 7bit
From: Wassim Haddad <Wassim.Haddad@ericsson.com>
Subject: Re: [Mip6] Francis' Review of draft-irtf-mobopts-ro-enhancements (was
	Re: FW: Please review draft-irtf-mobopts-ro-enhancements-00.txt)
Date: Fri, 27 May 2005 12:01:25 -0400
To: Christian Vogt <chvogt@tm.uka.de>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: MIP6 <mip6@ietf.org>, tm-ro2@tm.uka.de,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>, MOBOPTS <mobopts@irtf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

On 27-May-05, at 10:13 AM, Christian Vogt wrote:

> > => IMHO, you also get lower latency with OMIPv6 alone, in  
> addition to
> > getting higher security, since you
> > don't need to do the HoTI/HoT exchange.
>
>
> Hi Wassim,
>
> you are right.  The path through the HA is longer than the direct  
> one in many, probably most, scenarios.
>
> OMIPv6 without CBA reduces the overall latency by the difference  
> between the HoA-test latency and the CoA-test latency.  OMIPv6 with  
> CBA reduces it by the maximum of the HoA-test latency and the CoA- 
> test latency.
>
> Thanks for correcting this.

=> But if I understand correctly, the CBA does not behave equally in  
all type of applications. Right?


Regards,

Wassim H.



> Wassim Haddad wrote:
>
>> Hello Christian,
>> On 27-May-05, at 3:42 AM, Christian Vogt wrote:
>>
>>> It seems that there is a common ground to at least not increase  
>>> the  latency of standard Mobile IPv6.  In
>>> other words, many of the described proposals have merits in  
>>> terms  of reduced latency, even if their
>>> primary goal is to increase security. (OMIPv6 is a good  
>>> example.   If you combine it with Credit-Based
>>> Authorization, which is what we will do in Mipshop, you get  
>>> both,  higher security and lower latency.)
>>>
>> => IMHO, you also get lower latency with OMIPv6 alone, in addition  
>> to  getting higher security, since you
>> don't need to do the HoTI/HoT exchange.
>> Regards,
>> Wassim H.
>>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 27 15:46:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbkmW-0002zP-5M; Fri, 27 May 2005 15:46:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DbkmQ-0002wI-Ag; Fri, 27 May 2005 15:46:03 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20644;
	Fri, 27 May 2005 15:46:00 -0400 (EDT)
Message-Id: <200505271946.PAA20644@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 27 May 2005 15:46:00 -0400
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-ro-sec-03.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv6 Working Group of the IETF.

	Title		: Mobile IP version 6 Route Optimization Security
			  Design Background
	Author(s)	: P. Nikander, et al.
	Filename	: draft-ietf-mip6-ro-sec-03.txt
	Pages		: 41
	Date		: 2005-5-27
	
This document is an account of the rationale behind the Mobile IPv6
   (MIPv6) Route Optimization Security Design.  The purpose of this
   document is to present the thinking and to preserve the reasoning
   behind the Mobile IPv6 Security Design in 2001-2002.

   The document has two target audiences: (1) MIPv6 implementors so that
   they can better understand the design choices in MIPv6 security
   procedures; and (2) people dealing with mobility or multi-homing so
   that they can avoid a number of potential security pitfalls in their
   design.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-ro-sec-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mip6-ro-sec-03.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-ro-sec-03.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-mip6-ro-sec-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--NextPart--






From mip6-bounces@ietf.org Wed Jun 01 01:07:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdLRx-00089e-B1; Wed, 01 Jun 2005 01:07:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dd98y-0008E0-13; Tue, 31 May 2005 11:59:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20935;
	Tue, 31 May 2005 11:59:01 -0400 (EDT)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dd9Sa-0005VF-V9; Tue, 31 May 2005 12:19:22 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j4VFvVpF009435; 
	Tue, 31 May 2005 10:57:32 -0500 (CDT)
Received: from earth.dnrc.bell-labs.com (earth.dnrc.bell-labs.com
	[135.180.160.88]) by homail.ho.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2)
	id j4VFvOs16826; Tue, 31 May 2005 11:57:27 -0400 (EDT)
Date: Tue, 31 May 2005 11:57:24 -0400 (EDT)
From: Thyaga Nandagopal <thyaga@lucent.com>
X-X-Sender: thyaga@earth.dnrc.bell-labs.com
To: srajeev@in.ibm.com
Message-ID: <Pine.LNX.4.44.0505311144550.1088-100000@earth.dnrc.bell-labs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by hoemail1.lucent.com id
	j4VFvVpF009435
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 01 Jun 2005 01:07:27 -0400
Cc: 
Subject: [Mip6] Deadline approaching: CONSWARE 2006
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



        (Our apologies if you receive multiple copies of this document)

                           CALL FOR PAPERS
                           ***************
                   The First International Conference on=20
               Communication Systems Software and Middleware

                        http://www.comsware.org
                        -----------------------

                         January 8 - 12, 2006
                Taj Palace Hotel, New Delhi, India

        Technical Co-Sponsor : IEEE Communications Society=20
        In Co-operation with : ACM SIGMOBILE

        Sponsored by:          CreateNet (Italy), ICST (USA)

        Co-Sponsors:           IBM, Microsoft Research, NOKIA,=20
                               Lucent Technologies, Sasken
        University Co-Sponsor: Indian Institute of Technology, Delhi

                      Paper Submission: June 4, 2005 =20
                 (Instructions at http://www.comsware.org)

         (Proceedings to be published by IEEE and to appear in IEEE=20
Explore)

The convergence of the communications, information technologies and the=20
Internet
has ushered in a revolution in the way people communicate with each other=
.=20
The key
enabler for this convergence has been the advancement of software=20
technology in
various communication sectors, as evident by the high levels of activity=20
in the
industry, academia, and standards bodies, coupled with the increasing=20
dependence of
this convergence to sustain and improve growth rates in many countries=20
around the
world.

This new international conference will provide a forum to exchange ideas,=
=20
techniques,
and applications, discuss best practices and challenging issues, raise=20
awareness and
share experiences among researchers, practitioners, standard developers=20
and policy
makers in the field of software techniques in communications. The=20
conference will
bring leading researchers and practitioners in areas ranging from=20
communications
software and software engineering aspects of communications software, to=20
middleware
and networking protocols. The objective of the conference is to provide a=
=20
high
degree of collaboration, participation and discussions of the various=20
topics among
multi-national participants from the industrial, governmental and academi=
c=20
sectors.

COMSWARE will include a regular paper track and an industry track. The=20
paper track
will include a highly selective technical program. The conference solicit=
s=20
original,
previously unpublished research work, experimental efforts, and practical=
=20
experiences
for the technical program. COMSWARE will also feature panel discussions=20
from experts
in academia and industry, workshops and tutorials featuring the=20
state-of-the-art in
various communications software and related areas. There will be demos an=
d=20
exhibits
that will expose the delegates to exciting products and software solution=
s=20
from
industry and academia. Accepted papers will be published by IEEE Computer=
=20
Society.
The top papers accepted to the conference will be published in a reputed=20
journal.

Areas of interest include, but are not limited to:

=B7 Communications Software
=B7 Reconfigurable Software Stacks
=B7 Software Engineering Aspects of Communications Software
=B7 Context-Based and Implicit Computing
=B7 Telecommunications Services and QoS
=B7 Software for Billing and Pricing
=B7 User Interfaces and Interaction Models
=B7 Multi-Agent Systems
=B7 Client-Server Applications
=B7 Mobile and Intermittently Connected Applications
=B7 Mobile Data Management
=B7 Middleware Services and Agent Technologies
=B7 Middleware for Wireless Sensor Networks
=B7 Middleware for P2P Systems
=B7 Middleware for Future Communication Networks
=B7 Information Infrastructure and Security
=B7 Security and Privacy Issues of Pervasive Computing Systems=20
=B7 Network Operations and Management
=B7 Policy and Workflow-based Network Operations
=B7 Reliability Support Software
=B7 Resource Management in Pervasive Computing Platforms
=B7 Management Software for Optical Networks
=B7 Network Monitoring Software
=B7 Internet and IP based Services
=B7 Dynamic Service Composition and Deployment
=B7 Service Discovery Mechanisms
=B7 Wireless/Mobile Service Management and Delivery
=B7 Mobile / Wireless Computing Systems and Services
=B7 Performance Evaluation Techniques
=B7 Location Determination
=B7 Positioning and Tracking Technologies
=B7 Smart Devices and Smart Spaces
=B7 Enterprise Networking
=B7 Personal Area Networks
=B7 Integration of Wired and Wireless Networks
=B7 Next Generation Networks and Services


Deadlines
*********
Paper Submission: June 4, 2005  (Instructions at http://www.comsware.org)
Notification of Acceptance: August 15, 2005
Camera-ready due: September 26, 2005

Conference Organizing Committee
*******************************
General Chairs:         Victor Bahl, Microsoft Research, USA
                        Bijendra Nath Jain, IIT, Delhi, India
                        Henning Schulzrinne, Columbia University, USA
                        Alfred Spector, IBM Research, USA

Steering Committee:     Imrich Chlamtac, University of Trento, Italy =20
(Chair)
                        Rajeev Shorey, IBM Research, India           =20
(Co-Chair)
                        Prasant Mohapatra, University of California,=20
Davis, USA=20
                                                                     =20
(Co-Chair)   =20

Program Chairs:         Sanjoy Paul, Whenu, USA
                        G. Venkatesh, SASKEN Technologies, India
                        Jim Woodcock, University of York, UK

Tutorial Chair:         Archan Misra, IBM Research, USA

Workshop Chairs:        Ashwin Gumaste, Fujitsu Research, USA
                        Gaurav Sharma, University of Rochester, USA

Demos/Exhibit Chair:    Huzur Saran, IIT, Delhi, India
Demos/Exhibit Co-Chair: Jaijit Bhattacharya, Oracle, India

Publicity Chair:        Thyaga Nandagopal, Lucent Technologies, USA
Publicity Co-Chairs:    Sunghyun Choi, Seoul National University, Korea
                        Marco Conti, IIT, Pisa, Italy
                        Ben Lancini, LinLan, Brisbane, Australia
                        Prashant Pradhan, IBM Research, USA
                        Hemant Chaskar, Airtight Networks, India

Local Arrangement
Co-Chairs:              Sudipta Maitra, IBM, Delhi
                        Laurent Mignet, IBM Research, Delhi






_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



