From monami6-bounces@ietf.org Sat Apr 01 10:43:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FPiGC-0000m4-Kw; Sat, 01 Apr 2006 10:43:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FPiGB-0000lz-Mv
	for monami6@ietf.org; Sat, 01 Apr 2006 10:43:31 -0500
Received: from posti6.jyu.fi ([130.234.4.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPiGA-00052a-UV
	for monami6@ietf.org; Sat, 01 Apr 2006 10:43:31 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti6.jyu.fi (8.13.6/8.13.4) with ESMTP id k31FhSqW003978
	for <monami6@ietf.org>; Sat, 1 Apr 2006 18:43:28 +0300
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti6.jyu.fi (8.13.6/8.13.4) with ESMTP id k31FhDA0003934
	for <monami6@ietf.org>; Sat, 1 Apr 2006 18:43:15 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Changes needed to MCoA draft?
Date: Sat, 1 Apr 2006 18:41:17 +0300
User-Agent: KMail/1.9.1
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
In-Reply-To: <F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604011841.18102.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Ryuji,

On Tuesday 28 March 2006 19:00, Ryuji Wakikawa wrote:
> Hi Heikki again
> 
> On 2006/03/23, at 23:25, Heikki Mahkonen wrote:
> 
> > Hi Ryuji,
> >     What I think is that the MCoA draft is a good draft and it  
> > definitely should be monami6 WG draft as the monami6 charter also  
> > specifies. As I write this, I'm not awere of any decisions people  
> > have made in the monemi6 WG meeting held on tuesday about making  
> > this draft a WG draft. However, I also think that the MCoA draft  
> > needs some additional work to bring a optimal solution for the MCoA  
> > problem space.
> 
> We are waiting for the WG decision. I believe WG chairs should do  
> something now.
> 
> >     I think that the draft should solve two separate problem  
> > scenarios. First, it should enable MIPv6 MNs to bind more than one  
> > CoA to a single HoA. Second, it should specify a optimal way of  
> > delivering these bindings to HAs and CNs. Optimal way in this  
> > context meaning that the signaling overhead should be minimized (BU  
> > packet size and the number of BUs sent should be optimal).
> >
> > 1. Problems which the current draft solves:
> >
> >     The current version of the MCoA draft solves the problem of  
> > binding multiple CoAs to a single HoA for HAs and CNs by  
> > introducing a BID for the bindings. This is a good and optimal  
> > solution for the first problem scenario and I don't think this  
> > needs to be changed.
> >
> >     In addition the current draft specifies a BID option to deliver  
> > these BID's for the bindings in a BU message. This is also good  
> > solution when each CoA is sent in a single BU (either as source  
> > address or in a ACoA option). This BID option is in this case valid  
> > for HAs as well as any CNs.
> 
> OK so far.
> 
> > 2. Problems with the current draft:
> >
> >     The problems I can see with the current MCoA draft are with the  
> > second problem scenario which deals with a way of delivering the  
> > BIDs to other nodes from the MN. This should be done in a optimal  
> > way and I think that sending one BU for each CoA to HAs and CNs is  
> > not an optimal way. My opinion is that the MCoA draft should offer  
> > a way of piggy baging more than one CoA into a BU message destined  
> > to HAs and CNs. As I see it, the current mechanism defined in the  
> > MCoA draft does not enable MNs to send multiple CoAs in a single BU  
> > at least not to CNs. My opinion is that a new mechanism should be  
> > defined which is used to deliver multiple CoAs in single BU  
> > message. This new mechanism is defined in addition to the mechanism  
> > defined in the current MCoA draft which now enables delivering of  
> > CoAs one by one to HAs and CNs. So if the MN chooses to use one or  
> > the other solution it is up to the implementation to decide which  
> > is the better mechanism in any situation.
> 
> Again, as i said in previous mail, bulk registration is realistic  
> only for the initial BUs. When a MN first register its binding to CNs.
> Simultaneous CoAs changes are not so often occurred.
> 
> Anyway, I agree that the current draft is not complete solution for  
> bulk registartion to CN.
> 
> >
> >     In addition, I think that both of the mechanisms (the current  
> > and the new mechanism) should also work with legacy MIPv6 nodes  
> > which do not support the MCoA funtionality. This means that there  
> > might be constraints when sending a BU with multiple ACoA options  
> > which is the way specified in the draft now.
> 
> well, i can agree and disagree. For CN registration, CN will not  
> reply BA. Therefore, MN cannot know whether CN register multiple CoAs  
> or just single CoA.
> You may set Ack bit for MCoA registration all the time to check this.

True, if there is no BA the MN won't be able to know whether the bulk
registration succeeded or not, but it's the case with pure rfc3775 too,
or not? If there is no BA the MN does not know about the success or
failure of a BU regardless it was bulk or not bulk, MCoA BU or RFC3775 BU.
I see no difference here. What is your point?

> 
> >     Also, when sending a BU message which includes more than one  
> > CoA which the MN whishes to register (with a HA or CN), the binding  
> > lifetime  for each CoA must be delivered for each CoA in the BU  
> > message. This is not currently done in the MCoA draft.
> 
> no specification for bulk registartion.

Hmm... What about the last paragraph of Section 5.2 of the latest (05)
MCoA draft? Is not that about bulk registration?

> 
> > 3. Solutions to the problem of delivering multiple BIDs and CoAs in  
> > a ingle BU message:
> >
> >     There are two solutions for the second problem scenario. First  
> > solution is to define a variable length BID option. Second solution  
> > is to define three (two new) BID option types.
> >
> >     It should be defined that MN must always adds one CoA to the BU  
> > message as a source address or in the ACoA option and it is used in  
> > the normal RFC 3775 way. For this CoA the MN includes a BID option  
> > which is formatted as specified in the current MCoA draft. This is  
> > a valid way of delivering one of the CoAs to HAs and when the BU is  
> > sent to the CN a normal BAD option is used to authorize this CoA.  
> > In addition the binding lifetime for this CoA comes from the  
> > lifetime field in the BU option header. This enables a binding with  
> > a legacy MIPv6 nodes (which simply ignore the unknown options in  
> > the BU) as well.
> >
> >     When a MN is sending multiple CoAs to a HA in a single BU  
> > message, it will add the other CoAs (other than the one in the  
> > source address field or in the ACoA option) into a new variable  
> > length BID option. Each CoA is added into one BID option. Now this  
> > option would have the same fields currently defined in the MCoA  
> > option and in addition a field for the valid binding lifetime and a  
> > field for the CoA itself. The second solution is to add the binding  
> > lifetime and other CoAs into a new BID otion which looks like the  
> > BID option in the first case but would have different type code.
> >
> >     When a MN is sending multiple CoAs to a CN in a single BU  
> > message, it will add the other CoAs (other than the one in the  
> > source address field or in the ACoA option) into a new variable  
> > length BID option. Each CoA is added into one BID option. Now this  
> > option would have the same fields currently defined in the MCoA  
> > option and in addition a field for the valid binding lifetime, a  
> > field for the CoA itself, and fields for the nonces and binding  
> > authorization data. The second solution also in this case is to add  
> > the lifetime, the other CoAs, and the nonce and authorization data  
> > into a new BID otion which looks like the BID option in the first  
> > case but would have different type code.
> >
> > Any thoughts?
> 
> You solution can be possible. However, in Monami6 WG at dallas, the  
> base specification should be simple.
> The optimization is always good, but complication is not.

I think the proposal of Martti is quite simple even for implementers
and as shown in
http://www1.ietf.org/mail-archive/web/monami6/current/msg00498.html
its logic is quite clear (which means it is easy for implementers ;)).
What's more, it would make the whole draft more simple to
understand than the current draft-wakikawa-mobileip-multiplecoa-05.txt.
Questions like e.g. "so does bulk registration mean multiple ACoAs?"
are solved.
And it seems to work also with RFC3775 only CN/HA without any
implementation specific "hmmm, i wonder if the CN will choose the last or
first ACoA..." issues.
I like it :)

> 
> I think Hesham gave comments that we can initially support bulk  
> registartion for HA and not for CN.
> you can check the minutes of Monami6 WG meeting.

Do you mean the 2nd WG meeting in Dallas?
Could you please point me at the place where it is accessible?

Thank You,
Gabor Fekete

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 06 00:53:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRMUn-0002sZ-ME; Thu, 06 Apr 2006 00:53:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRMUl-0002s5-Q4
	for monami6@ietf.org; Thu, 06 Apr 2006 00:53:23 -0400
Received: from f.csce.kyushu-u.ac.jp ([133.5.33.1])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FRMUg-0006rr-JD
	for monami6@ietf.org; Thu, 06 Apr 2006 00:53:23 -0400
Received: (qmail 9138 invoked from network); 6 Apr 2006 04:53:16 -0000
Received: from unknown (HELO ?172.17.3.211?) (192.168.77.254)
	by 192.168.77.101 with SMTP; 6 Apr 2006 04:53:16 -0000
Date: Thu, 06 Apr 2006 13:53:16 +0900
From: Teruaki Kitasuka <kitasuka@f.csce.kyushu-u.ac.jp>
To: manet@ietf.org, mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org,
	monami6@ietf.org, nemo@ietf.org
Message-Id: <20060406135026.5228.KITASUKA@f.csce.kyushu-u.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: 
Subject: [Monami6] CfP - 3rd Int. Conf. on Mobile Computing and Ubiquitous
	Networking (ICMU2006) at London, UK
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

(Apologies if you receive multiple copies of this message)
2 weeks left for submission.

========================================================================
                     C A L L   F O R   P A P E R S 
========================================================================

The Third International Conference on
Mobile Computing and Ubiquitous Networking (ICMU2006)

October 11-13, 2006
BCS London Office, London, UK
http://www.icmu.org/icmu2006/

Sponsored by:
  IPSJ SIG-MBL (Information Processing Society of Japan,
  Special Interest Group of Mobile Computing and Ubiquitous Networking)
Technically co-sponsored by:
  BCS (British Computer Society),
  IEE (Institution of Electrical Engineers), and
  IEEE ITS Society, Technical Committee on Mobile Commuications &
  Applications
Supported by:
  ICF (International Communications Foundation)


SCOPE:

Mobile computing aims at ubiquitous user access to computer application.
To make it possible, networking technology
which enables Internet access anytime and everywhere,
i.e. ubiquitous networking is necessary. It is obvious that with the
accelerating trends towards mobile networks, ad-hoc networks,
and wireless networks, mobile computing and ubiquitous
networking will play an important role in future network.
This conference is aimed at providing researchers and practitioners
in this hot research area a forum for discussion and collaboration.
Authors are invited to submit papers addressing, but not
limited to, the following topics:

- Network management for ubiquitous networking 
- Data management for mobile computing
- Mobile device management 
- Performance evaluation for mobile computing and
 ubiquitous networking systems 
- Broadcast communications 
- Network architectures, protocols, or service models
 for ubiquitous networking 
- Security in mobile computing and ubiquitous networking 
- Mobile OS
- Wireless and mobile communications
- 4G wireless communications
- Mobile Internetworking 
- Ad-hoc networks
- Network mobility
- Mesh networks
- Sensor networks 
- Location-based services 

SUBMISSION INSTRUCTIONS:

Papers are solicited as full papers of no more than 8 pages,
each of which will be subject to a full review process.
Submission should already follow the author guidelines as specified
in the web site below.
An electronic, PDF-based submission of papers is mandatory.

Please check the web site of the conference
http://www.icmu.org/icmu2006/
for further submission instructions.

After the conference, a selected number of papers will be published
as special issues in IPSJ journal and IPSJ Digital Courier.
Please check the web site of IPSJ
http://www.ipsj.or.jp/08editt/dc/index.html
for the details of IPSJ Digital Coulier.


IMPORTANT DATES:

##########################################################
#        Deadline for submissions: April 22, 2006        #
#        Notification of acceptance: July 8, 2006        #
#        Camera ready due: July 31, 2006                 #
##########################################################


ORGANIZING COMMITTEE:

General Chair:
  Chai-Keong Toh (Queen Mary University of London, UK)
 
Technical Program Committee Co-Chairs:
  Susumu Ishihara (Shizuoka University, Japan)
  Eiji Kamioka (National Institute of Informatics, Japan)
 
Publication Co-Chairs:
  Gen Kitagata (Tohoku University, Japan)
  Yang Yang (University College London, UK)
 
Publicity Co-Chairs:
  Teruaki Kitasuka (Kyushu University, Japan)
  Kun Yang (University of Essex, UK)
 
Local Arrangement Chair:
  David Martland (Kingston University London, UK)
 
Treasurers:
  David Martland (Kingston University London, UK)
  Tomohiko Yagyu (NEC, Japan)
 
Registration Co-Chairs:
  Jindong Hou (France Telecom, UK)
  Homare Murakami (NICT, Japan)

ICMU STEERING COMMITTEE:

  Tadanori Mizuno (Shizuoka University, Japan)
  Osamu Takahashi (Future University-Hakodate, Japan)
  Takashi Watanabe (Shizuoka University, Japan)
  Miki Yamamoto (Kansai University, Japan)


TECHNICAL PROGRAM COMMITTEE:

Mohammed Atiquzzaman (University of Oklahoma, USA)
Xiuzhen Cheng (George Washington University, USA)
We Duke Cho (Ajou University, Korea)
John Gardiner (Bradford University, UK)
Teruo Higashino (Osaka University, Japan)
Choong Seon Hong (Kyung Hee University, Korea)
Russell Hsing (Telcordia Technologies, USA)
Chung Ming Huang (National Cheng Kung University, Taiwan)
Joseph Hui (Arizona State University, USA)
Masugi Inoue (NICT, Japan)
Masahiro Ishiyama (Toshiba Corporation, Japan)
Holger Karl (University of Paderborn, Germany)
Hughes Kester (Qinetiq Ltd, UK)
Dongkyun Kim (Kyungpook National University, Korea)
Peter Langendoerfer (IHP Microelectronics, Germany)
Madjid Merabti (Liverpool John Moores University, UK)
Isabelle Moreau (Mitsubishi Electric ITE, France)
Hiroyuki Morikawa (University of Tokyo, Japan)
Yasuto Nakanishi (Keio University, Japan)
Ken Ohta (NTT DoCoMo, Japan)
Ryouji Ono (Mitsubishi Electric, Japan)
Mohamed Ould-Khaoua (University of Glasgow, UK)
Antonio Pescape (University of Napoli, Italy)
Petar Popovski (Aalborg University, Denmark)
Jeremy Randles (British Telecom, UK)
Ichiro Satoh (National Institute of Informatics, Japan)
Winston Seah (Institute for Infocomm Research, Singapore)
Hiroshi Shigeno (Keio University, Japan)
Biplab Sikdar (Rensselaer Polytechnic Institute, USA)
David Simplot-Ryl (University of Lille 1, France)
Tatsuya Suda (University of California Irvine, USA)
Shinta Sugimoto (Nippon Ericsson, Japan)
Keisuke Suwa (Musashi Institute of Technology, Japan)
Kevin W. Tsai (University of California, Irvine, USA)
Xin Wang (Fudan University, China)
Neil Williams (ERA Technology Ltd, UK)
Nik Van den Wingaert (University of Antwerp, Belgium)
Hirozumi Yamaguchi (Osaka University, Japan)
Kun Yang (Essex University, UK)
Yang Yang (University College London, UK)
Masashi Yano (Hitachi Ltd, Japan)
Hidetoshi Yokota (KDDI R&D Laboratories, Japan)
Ekio Yoneki (Cambridge University, UK)
Qing-An Zeng (University of Cincinnati, USA)
========================================================================


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 07 04:56:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRmlW-00081V-2j; Fri, 07 Apr 2006 04:56:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRmlU-00081P-Us
	for monami6@ietf.org; Fri, 07 Apr 2006 04:56:24 -0400
Received: from jens246.inetcore.com ([202.33.8.246] helo=chappy.inetcore.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRmlT-0004O6-BG
	for monami6@ietf.org; Fri, 07 Apr 2006 04:56:24 -0400
Received: from nagami-T42.wide.ad.jp (nt-23 [172.16.2.1])
	by chappy.inetcore.com (8.13.3/8.13.3) with ESMTP id k378uHH6012354;
	Fri, 7 Apr 2006 17:56:18 +0900 (JST)
	(envelope-from nagami@wide.ad.jp)
Message-Id: <6.2.3.4.2.20060407133704.0a6b9d60@inc.inetcore.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2J rev4.2
Date: Fri, 07 Apr 2006 17:56:12 +0900
To: Monami6 WG <monami6@ietf.org>, Monami6 WG <monami6@ietf.org>
From: Ken Nagami <nagami@wide.ad.jp>
Subject: Re: [Monami6] Problem with MCoA draft?!
In-Reply-To: <442A4191.90504@nomadiclab.com>
References: <4422AC28.6020000@nomadiclab.com>
	<254DFE31-8067-4429-A23F-9A1E494E5BA8@sfc.wide.ad.jp>
	<442A4191.90504@nomadiclab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki,


>>The important aspect of bulk BU is that the address changes must be
>>happened at the same time. Otherwise, the MN shouldn't send BUs for
>>multiple CoAs.
>
>==> OK! I originally meant that the CoA1 and CoA2 are CoAs from the 
>same interface. So let me clarify my example. You have one HoA, 
>three CoAs and two interfaces. Two of the CoAs are from the same 
>interface. So even  when the CN or HA does not know based on the 
>CoAs or BIDs which address is from which MNs interface the BC would 
>look like this.
>
>BID1, HoA, CoA1 (WLAN)
>BID2, HoA, CoA2 (WLAN)
>BID3, HoA, CoA3 (EVDO)
>
>So now when your WLAN interface makes a handover from a link with 
>two prefixes to a link with only one prefix the CoA1 and CoA2 needs 
>to be "updated" to CoA4 which is now the new CoA of the WLAN 
>interface. In this case you can only reuse one of the BIDs (either 
>BID1 or BID2) for the CoA4 and you have to do something else to 
>remove the binding with the leftover BID. So this is why I make such 
>a fuss about this what if you have this many CoAs and they are 
>changed to this many CoAs. =) But OK, if you only want to support 
>one CoA per interface then this is no problem at all.

CoA of BID1 or BID2 needs to remove. MN sends BU with lifetime 0 and BID-option.
In this case, I think it does not have a problem.
MN needs to send bulk BU with reused BID and removed BID separately 
in the current draft.

BID1, HoA, CoA1  -> CoA4
BID2, HoA, CoA2  -> remove
BID3, HoQ, CoA3

Regards,
Ken Nagami 


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Apr 10 04:06:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FSrPy-0007GD-A8; Mon, 10 Apr 2006 04:06:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FSrPv-0007Ee-TU
	for monami6@ietf.org; Mon, 10 Apr 2006 04:06:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSrJa-0004ak-Ds
	for monami6@ietf.org; Mon, 10 Apr 2006 04:00:02 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FSrJX-0008I6-9M
	for monami6@ietf.org; Mon, 10 Apr 2006 04:00:02 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Apr 2006 09:59:35 +0200
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
Subject: RE: [Monami6] Accept
	draft-wakikawa-mobileip-multiplecoa-04.txtas	Monami6 WG Document
Date: Mon, 10 Apr 2006 09:59:34 +0200
Message-ID: <BBBE5BAA3B351C488C415EA662EA8840031FEEA5@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Accept
	draft-wakikawa-mobileip-multiplecoa-04.txtas	Monami6 WG Document
Thread-Index: AcXePCCV9ulnldUnTzC1l7daHamCkx+N9Rkg
From: "KLAMM Frederic RD-CORE-CAE" <frederic.klamm@francetelecom.com>
To: "Ryuji Wakikawa" <ryuji@sfc.wide.ad.jp>
X-OriginalArrivalTime: 10 Apr 2006 07:59:35.0748 (UTC)
	FILETIME=[B57D3040:01C65C74]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Ryuji,
I understand that having only one CoA per interface is an implementation =
choice, and that the MCoA draft is to allow several CoA per interface.
Therefore, wouldn't it be worth enlarging formally the scope of the spec =
by adding in 5.1 :
=20
"  There are two cases when a mobile node has several Care-of Addresses:

   1.  A mobile node uses several physical network interfaces and
       acquires a Care-of Address on each of its interfaces.

   2.  A mobile node uses a single physical network interface, but
       multiple prefixes are announced on the link the interface is
       attached to.  Several global addresses are configured on this
       interface for each of the announced prefixes.	"

A third case, combination of the 2 previous cases, something like :
  =20
   3.  A mobile node uses several physical network interfaces and=20
	several global adresses are configured on at least one of these =
interfaces.	"

Fred=20

> -----Message d'origine-----
> De : monami6-bounces@ietf.org=20
> [mailto:monami6-bounces@ietf.org] De la part de Nicolas Montavont
> Envoy=E9 : lundi 31 octobre 2005 17:54
> =C0 : Ryuji Wakikawa
> Cc : Monami6 WG
> Objet : Re: [Monami6] Accept=20
> draft-wakikawa-mobileip-multiplecoa-04.txtas Monami6 WG Document
>=20
> Ryuji,
>=20
> On 31 oct. 05, at 16:08, Ryuji Wakikawa wrote:
>=20
> > Hi NIcolas
> >
> > On 2005/10/31, at 19:15, Nicolas Montavont wrote:
> >
> >
> >> Hi Ryuji,
> >>
> >> ...
> >>
> >>
> >>
> >>>> 3. I dont understand the need for a BID. the draft says
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>          The BID is an identification number used to distinguish
> >>>>>          multiple bindings registered by the mobile node.  =20
> >>>>> Assignment of
> >>>>>          distinct BID allows a mobile node to register=20
> multiple =20
> >>>>> binding
> >>>>>          cache entries for a given home address.
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> doesnt the HoA/CoA pair uniquely identify a binding?
> >>>> do you want a unique identifier for a particular
> >>>> binding even when the CoA changes? in that case why
> >>>> not associate the interface with a particular binding?
> >>>> maybe I am missing something.
> >>>>
> >>>>
> >>>>
> >>>
> >>> How do you express interface in MIP6 stack? Do you suggest the =20
> >>> use of
> >>> name like "en0"?:-)
> >>> BID can be an interface index which most of=20
> implementation uses for
> >>> interface management.  That's why we use 16bits length for
> >>> BID. (interface index is mostly 16bits)
> >>>
> >>> In our system, we bind BID with network interface. We define
> >>> well-known BID which express intereface like wifi,=20
> ethernet, Ev-Do,
> >>> etc. (This is not in the draft though).
> >>>
> >>>
> >>
> >> I am not sure I follow you here. Do you mean that you consider to =20
> >> have only one binding HoA/CoA per interface?
> >>
> >
> > Do you consider the case when multiple CoAs are assigned to an =20
> > interface?
> > Sure. That's possible with the current MCOA draft.
>=20
> Yes, that's what I meant.
>=20
> >
> > The above example is just example of our system.
> > In our system, the interface only has one CoA per interface.
>=20
> Ok if it's an implementation choice.
> However, I think we should allow several CoAs per interface=20
> in the spec.
>=20
> Nicolas
>=20
> >
> > ryuji
> >
> >
> >> Thanks,
> >>
> >> Nicolas
> >>
> >>
> >>
> >>>
> >>>
> >>> ryuji
> >>>
> >>> _______________________________________________
> >>> Monami6 mailing list
> >>> Monami6@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/monami6
> >>>
> >>>
> >>>
> >>
> >>
> >
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Apr 10 08:22:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FSvPa-0000K7-NP; Mon, 10 Apr 2006 08:22:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FSvPZ-0000Hk-J1
	for monami6@ietf.org; Mon, 10 Apr 2006 08:22:29 -0400
Received: from 33.106-14-84.ripe.coltfrance.com ([84.14.106.33]
	helo=proxy.6wind.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FSvPZ-0007Ts-1X
	for monami6@ietf.org; Mon, 10 Apr 2006 08:22:29 -0400
Received: from [10.16.0.239] (unknown [10.16.0.239])
	by proxy.6wind.com (Postfix) with ESMTP id 92189525F8E;
	Mon, 10 Apr 2006 14:22:27 +0200 (CEST)
Message-ID: <443A4E03.2070105@6wind.com>
Date: Mon, 10 Apr 2006 14:22:27 +0200
From: Vincent Jardin <Vincent.Jardin@6wind.com>
Organization: http://www.6WIND.com/
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Accept	draft-wakikawa-mobileip-multiplecoa-04.txtas
	Monami6 WG Document
References: <BBBE5BAA3B351C488C415EA662EA8840031FEEA5@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <BBBE5BAA3B351C488C415EA662EA8840031FEEA5@FTRDMEL2.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

When you have many addresses (prefixes) on the same interface, you need=20
to define an heuristic to select the source address of the packets.

Regards,
   Vincent

KLAMM Frederic RD-CORE-CAE wrote:
> Hi Ryuji,
> I understand that having only one CoA per interface is an implementatio=
n choice, and that the MCoA draft is to allow several CoA per interface.
> Therefore, wouldn't it be worth enlarging formally the scope of the spe=
c by adding in 5.1 :
> =20
> "  There are two cases when a mobile node has several Care-of Addresses=
:
>=20
>    1.  A mobile node uses several physical network interfaces and
>        acquires a Care-of Address on each of its interfaces.
>=20
>    2.  A mobile node uses a single physical network interface, but
>        multiple prefixes are announced on the link the interface is
>        attached to.  Several global addresses are configured on this
>        interface for each of the announced prefixes.	"
>=20
> A third case, combination of the 2 previous cases, something like :
>   =20
>    3.  A mobile node uses several physical network interfaces and=20
> 	several global adresses are configured on at least one of these interf=
aces.	"
>=20
> Fred=20
>=20
>=20
>>-----Message d'origine-----
>>De : monami6-bounces@ietf.org=20
>>[mailto:monami6-bounces@ietf.org] De la part de Nicolas Montavont
>>Envoy=E9 : lundi 31 octobre 2005 17:54
>>=C0 : Ryuji Wakikawa
>>Cc : Monami6 WG
>>Objet : Re: [Monami6] Accept=20
>>draft-wakikawa-mobileip-multiplecoa-04.txtas Monami6 WG Document
>>
>>Ryuji,
>>
>>On 31 oct. 05, at 16:08, Ryuji Wakikawa wrote:
>>
>>
>>>Hi NIcolas
>>>
>>>On 2005/10/31, at 19:15, Nicolas Montavont wrote:
>>>
>>>
>>>
>>>>Hi Ryuji,
>>>>
>>>>...
>>>>
>>>>
>>>>
>>>>
>>>>>>3. I dont understand the need for a BID. the draft says
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>         The BID is an identification number used to distinguish
>>>>>>>         multiple bindings registered by the mobile node.  =20
>>>>>>>Assignment of
>>>>>>>         distinct BID allows a mobile node to register=20
>>
>>multiple =20
>>
>>>>>>>binding
>>>>>>>         cache entries for a given home address.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>doesnt the HoA/CoA pair uniquely identify a binding?
>>>>>>do you want a unique identifier for a particular
>>>>>>binding even when the CoA changes? in that case why
>>>>>>not associate the interface with a particular binding?
>>>>>>maybe I am missing something.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>How do you express interface in MIP6 stack? Do you suggest the =20
>>>>>use of
>>>>>name like "en0"?:-)
>>>>>BID can be an interface index which most of=20
>>
>>implementation uses for
>>
>>>>>interface management.  That's why we use 16bits length for
>>>>>BID. (interface index is mostly 16bits)
>>>>>
>>>>>In our system, we bind BID with network interface. We define
>>>>>well-known BID which express intereface like wifi,=20
>>
>>ethernet, Ev-Do,
>>
>>>>>etc. (This is not in the draft though).
>>>>>
>>>>>
>>>>
>>>>I am not sure I follow you here. Do you mean that you consider to =20
>>>>have only one binding HoA/CoA per interface?
>>>>
>>>
>>>Do you consider the case when multiple CoAs are assigned to an =20
>>>interface?
>>>Sure. That's possible with the current MCOA draft.
>>
>>Yes, that's what I meant.
>>
>>
>>>The above example is just example of our system.
>>>In our system, the interface only has one CoA per interface.
>>
>>Ok if it's an implementation choice.
>>However, I think we should allow several CoAs per interface=20
>>in the spec.
>>
>>Nicolas
>>
>>
>>>ryuji
>>>
>>>
>>>
>>>>Thanks,
>>>>
>>>>Nicolas
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>ryuji
>>>>>
>>>>>_______________________________________________
>>>>>Monami6 mailing list
>>>>>Monami6@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/monami6
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>
>>_______________________________________________
>>Monami6 mailing list
>>Monami6@ietf.org
>>https://www1.ietf.org/mailman/listinfo/monami6
>>
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Apr 10 10:48:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FSxgz-0004tR-Ar; Mon, 10 Apr 2006 10:48:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FSxgy-0004tM-RZ
	for monami6@ietf.org; Mon, 10 Apr 2006 10:48:36 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSxgy-0004UW-9r
	for monami6@ietf.org; Mon, 10 Apr 2006 10:48:36 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Apr 2006 16:48:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Monami6] Accept
	draft-wakikawa-mobileip-multiplecoa-04.txtasMonami6 WG Document
Date: Mon, 10 Apr 2006 16:48:32 +0200
Message-ID: <BBBE5BAA3B351C488C415EA662EA8840031FF284@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Accept
	draft-wakikawa-mobileip-multiplecoa-04.txtasMonami6 WG Document
Thread-Index: AcZcmXHiUrnUjlMHQTWDbdWWwffM9AAE7Y7g
From: "KLAMM Frederic RD-CORE-CAE" <frederic.klamm@francetelecom.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 10 Apr 2006 14:48:34.0185 (UTC)
	FILETIME=[D7898790:01C65CAD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1684963765=="
Errors-To: monami6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1684963765==
Content-class: urn:content-classes:message
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=SHA1; boundary="----=_NextPart_000_0072_01C65CBE.99B69820"

This is a multi-part message in MIME format.

------=_NextPart_000_0072_01C65CBE.99B69820
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Wasn't this already true for case 2 ?=20

Regards

> -----Message d'origine-----
> De : Vincent Jardin [mailto:Vincent.Jardin@6wind.com]=20
> Envoy=E9 : lundi 10 avril 2006 14:22
> =C0 : Monami6 WG
> Objet : Re: [Monami6] Accept=20
> draft-wakikawa-mobileip-multiplecoa-04.txtasMonami6 WG Document
>=20
> Hi,
>=20
> When you have many addresses (prefixes) on the same=20
> interface, you need to define an heuristic to select the=20
> source address of the packets.
>=20
> Regards,
>    Vincent
>=20
> KLAMM Frederic RD-CORE-CAE wrote:
> > Hi Ryuji,
> > I understand that having only one CoA per interface is an=20
> implementation choice, and that the MCoA draft is to allow=20
> several CoA per interface.
> > Therefore, wouldn't it be worth enlarging formally the=20
> scope of the spec by adding in 5.1 :
> > =20
> > "  There are two cases when a mobile node has several=20
> Care-of Addresses:
> >=20
> >    1.  A mobile node uses several physical network interfaces and
> >        acquires a Care-of Address on each of its interfaces.
> >=20
> >    2.  A mobile node uses a single physical network interface, but
> >        multiple prefixes are announced on the link the interface is
> >        attached to.  Several global addresses are configured on this
> >        interface for each of the announced prefixes.	"
> >=20
> > A third case, combination of the 2 previous cases, something like :
> >   =20
> >    3.  A mobile node uses several physical network interfaces and=20
> > 	several global adresses are configured on at least one=20
> of these interfaces.	"
> >=20
> > Fred
> >=20
> >=20
> >>-----Message d'origine-----
> >>De : monami6-bounces@ietf.org
> >>[mailto:monami6-bounces@ietf.org] De la part de Nicolas Montavont=20
> >>Envoy=E9 : lundi 31 octobre 2005 17:54 =C0 : Ryuji Wakikawa Cc=20
> : Monami6=20
> >>WG Objet : Re: [Monami6] Accept=20
> >>draft-wakikawa-mobileip-multiplecoa-04.txtas Monami6 WG Document
> >>
> >>Ryuji,
> >>
> >>On 31 oct. 05, at 16:08, Ryuji Wakikawa wrote:
> >>
> >>
> >>>Hi NIcolas
> >>>
> >>>On 2005/10/31, at 19:15, Nicolas Montavont wrote:
> >>>
> >>>
> >>>
> >>>>Hi Ryuji,
> >>>>
> >>>>...
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>3. I dont understand the need for a BID. the draft says
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>         The BID is an identification number used to=20
> distinguish
> >>>>>>>         multiple bindings registered by the mobile node.  =20
> >>>>>>>Assignment of
> >>>>>>>         distinct BID allows a mobile node to register
> >>
> >>multiple
> >>
> >>>>>>>binding
> >>>>>>>         cache entries for a given home address.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>doesnt the HoA/CoA pair uniquely identify a binding?
> >>>>>>do you want a unique identifier for a particular=20
> binding even when=20
> >>>>>>the CoA changes? in that case why not associate the=20
> interface with=20
> >>>>>>a particular binding?
> >>>>>>maybe I am missing something.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>How do you express interface in MIP6 stack? Do you=20
> suggest the use=20
> >>>>>of name like "en0"?:-) BID can be an interface index=20
> which most of
> >>
> >>implementation uses for
> >>
> >>>>>interface management.  That's why we use 16bits length for BID.=20
> >>>>>(interface index is mostly 16bits)
> >>>>>
> >>>>>In our system, we bind BID with network interface. We define=20
> >>>>>well-known BID which express intereface like wifi,
> >>
> >>ethernet, Ev-Do,
> >>
> >>>>>etc. (This is not in the draft though).
> >>>>>
> >>>>>
> >>>>
> >>>>I am not sure I follow you here. Do you mean that you consider to=20
> >>>>have only one binding HoA/CoA per interface?
> >>>>
> >>>
> >>>Do you consider the case when multiple CoAs are assigned to an=20
> >>>interface?
> >>>Sure. That's possible with the current MCOA draft.
> >>
> >>Yes, that's what I meant.
> >>
> >>
> >>>The above example is just example of our system.
> >>>In our system, the interface only has one CoA per interface.
> >>
> >>Ok if it's an implementation choice.
> >>However, I think we should allow several CoAs per interface in the=20
> >>spec.
> >>
> >>Nicolas
> >>
> >>
> >>>ryuji
> >>>
> >>>
> >>>
> >>>>Thanks,
> >>>>
> >>>>Nicolas
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>ryuji
> >>>>>
> >>>>>_______________________________________________
> >>>>>Monami6 mailing list
> >>>>>Monami6@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/monami6
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>
> >>_______________________________________________
> >>Monami6 mailing list
> >>Monami6@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/monami6
> >>
> >=20
> >=20
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >=20
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

------=_NextPart_000_0072_01C65CBE.99B69820
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIISOzCCBHIw
ggNaoAMCAQICAhJzMA0GCSqGSIb3DQEBBQUAMFwxCzAJBgNVBAYTAkZSMRcwFQYDVQQKEw5GcmFu
Y2UgVGVsZWNvbTETMBEGA1UECxMKRlRSRC1Bc3BpYzEfMB0GA1UEAxMWRlRSRCBBQyBvcGVyYXRp
b25uZWxsZTAeFw0wNDAxMjYxNTQ4MDhaFw0wNzAxMjUxNTQ4MDhaMIGfMQswCQYDVQQGEwJGUjEX
MBUGA1UEChMORnJhbmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQVNQSUMxFzAVBgNVBAMTDkZy
ZWRlcmljIEtMQU1NMRgwFgYKCZImiZPyLGQBARMIRllZSzYzMDIxLzAtBgkqhkiG9w0BCQEWIGZy
ZWRlcmljLmtsYW1tQGZyYW5jZXRlbGVjb20uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKB
gQDTBrw4zUSsV75pAW/KeOmbRugTGct9YxBmMpr+lmtRPsQ5q5hEi7ddMb8yfnHb09+QkD6AixB1
9cpgRzS4zaAOzjHO4oyHNL+cJeAtRd2pq4Eg6MbV8WcacUOSC1w/3SY8zedDYHWNldFPDzqwVTq6
uvOENZbRk+TQVtU3UigHbQIDAQABo4IBfDCCAXgwHQYDVR0OBBYEFPyjFJk9wodUOkY0gtA755e/
slKHMB8GA1UdIwQYMBaAFKeHuNCL9G/jwcDa7Y604KcQKfzYMIGSBgNVHR8EgYowgYcwR6BFoEOG
QWh0dHA6Ly9sdWNpZmVyLnJkLmZyYW5jZXRlbGVjb20uZnIvcmV2b3F1ZXMvY3Jsb3BlcmF0aW9u
bmVsbGUuY3JsMDygOqA4hjZodHRwOi8vcGtpLWwucmQuZnJhbmNldGVsZWNvbS5mci9jcmxvcGVy
YXRpb25uZWxsZS5jcmwwDgYDVR0PAQH/BAQDAgQwMBMGA1UdJQQMMAoGCCsGAQUFBwMEMBEGCWCG
SAGG+EIBAQQEAwIFIDArBgNVHREEJDAigSBmcmVkZXJpYy5rbGFtbUBmcmFuY2V0ZWxlY29tLmNv
bTA8BglghkgBhvhCAQ0ELxYtQ2VydGlmaWNhdCBkZSBDaGlmZnJlbWVudCBwb3VyIEZyZWRlcmlj
IEtMQU1NMA0GCSqGSIb3DQEBBQUAA4IBAQAUIg+A4lU/g1wBnsa2QVA+w+tGrfEdurwiD1k/eM1H
thCaZ+u6lsrBvBjLSnmj2R7X5Mc8BbDWnfJgUK8iFMPc6DSfi9dSAhBxaq0gHdJb7Fa3/0/KCzW6
Nmuu4dZ0SnnHOStKiQLOenLTiy0fwjZS+NpCeAaVOBbWo6Fgk77whtf6OlJNkr1gT/2hhHkLVDie
bjA7vtrJU24qLL8mU4zjPS9J+3aJ+7vMEZ6oEYdjKWLVAmu1kEmBAso7prp+QfTWNn0U8GH6dHx9
5cyKWQXIVVMBv+psdVc9riEBY2vDvkmPcXOOZcun8u2ZbDukQUKGgNC3nat621q13Jt6SPIAMIIE
gDCCA2igAwIBAgIBADANBgkqhkiG9w0BAQUFADBUMQswCQYDVQQGEwJGUjEXMBUGA1UEChMORnJh
bmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQXNwaWMxFzAVBgNVBAMTDkZUUkQgQUMgUmFjaW5l
MB4XDTAyMTAwMzA3MDc1OFoXDTEyMTAwMjA3MDc1OFowVDELMAkGA1UEBhMCRlIxFzAVBgNVBAoT
DkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFzcGljMRcwFQYDVQQDEw5GVFJEIEFDIFJh
Y2luZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAN81v0NOnfyYxmzODVMnAd441zKV
C749cLug6OmEhid7QdBAdRJeMoMonu9uWdOQCuyvdG67VCsA686aSbDPyTTozTeFwZnRj3byhZrc
obqJ2Sx0rA2PjQmpZukgSS3l8Cw0OnZO5lpQZSBfOJ4F0ORje7IWrQb8QbpPt/cbCPie7ZjhUilr
3js2TSWPAUrhZJKp0NNSHxk5V+loB+xSLqVrKdYWloiq4RrjEpXL8792NMwR6URm9rwAOJu0LwYU
07q6iLKOI106qTvKejLVxAL5+sT5YWK/ubi8hdLhW8u9CxOTmSfJ9pY8A1FiqPyWcJ3gHSz2ItRv
H2mJq1c/IuMCAwEAAaOCAVswggFXMBIGA1UdEwEB/wQIMAYBAf8CAQEwHQYDVR0OBBYEFLdJ7pNB
In/ZqJeVJz5kZp6uGD8DMHwGA1UdIwR1MHOAFLdJ7pNBIn/ZqJeVJz5kZp6uGD8DoVikVjBUMQsw
CQYDVQQGEwJGUjEXMBUGA1UEChMORnJhbmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQXNwaWMx
FzAVBgNVBAMTDkZUUkQgQUMgUmFjaW5lggEAMA4GA1UdDwEB/wQEAwIBBjCBgAYDVR0fBHkwdzA/
oD2gO4Y5aHR0cDovL2x1Y2lmZXIucmQuZnJhbmNldGVsZWNvbS5mci9yZXZvcXVlcy9jcmxyYWNp
bmUuY3JsMDSgMqAwhi5odHRwOi8vcGtpLWwucmQuZnJhbmNldGVsZWNvbS5mci9jcmxyYWNpbmUu
Y3JsMBEGCWCGSAGG+EIBAQQEAwIABzANBgkqhkiG9w0BAQUFAAOCAQEAaLy9uyUJDjvHSevW9lda
ZsG+zl7Q1J+PnMPOCffYHdKHI6/rtzp0S+rUGMWEdF82FxGnGaIT0/gc6p+2gPv+/3YxGWgb0aBK
5xEjxIefmhA7rGKxpurGq4PmEj4b6Ye/Z9hTBFlFI2Ixu51zk4hEvHoky8oFdQdzb29q541pFBsP
7qbidxi62zlqxE7S4Zx+3KzkegDJIJ6k4XXK307jUYJBbnC7aBodST6P2I8qTXclG7qTkKf/wzy1
y8DSyRqNABoX6XLeQyM9omGrKARhdCgsMULoPNRAMI1N1n3DlDCKfWjJl7WVaaywyKGVmiSKInbY
tM5XB2hoaErJ1ZEk3TCCBIgwggNwoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMC
RlIxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFzcGljMRcwFQYDVQQD
Ew5GVFJEIEFDIFJhY2luZTAeFw0wMjEwMDMwNzE1MjBaFw0xMjEwMDIwNzE1MjBaMFwxCzAJBgNV
BAYTAkZSMRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTETMBEGA1UECxMKRlRSRC1Bc3BpYzEfMB0G
A1UEAxMWRlRSRCBBQyBvcGVyYXRpb25uZWxsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBAPKErrcyQf+tgRGBsiBQKGGnvheMF+E74XARkkDrNnL/oA5w6e96Nj5eF7TdoiE7AIQRvOUr
JkI9xP74szDUP/CPBPVxxL0855pyoH/qBcgdVCVWBDKGGroc9A5OeXsKCietb1y4+PV5JeQVw3e4
1vqJ06Ut81QYPkZ84uJSIiRNoaZG+dBYBOfP8pL3Gj2jnX53eslfdiXjslMk7icbvcvAuBlzHU/L
kLNHZV/iEJGGfj3X8kOMF0e3v1OlAX+TXEYlvA46wnffqVMIgiiFbAHPOBMIqOMOVQXx2SdokRcp
AsHtb8LcaLrSseDf/bmzvhkufp6qYoUoNC9s4g48J9ECAwEAAaOCAVswggFXMBIGA1UdEwEB/wQI
MAYBAf8CAQAwHQYDVR0OBBYEFKeHuNCL9G/jwcDa7Y604KcQKfzYMHwGA1UdIwR1MHOAFLdJ7pNB
In/ZqJeVJz5kZp6uGD8DoVikVjBUMQswCQYDVQQGEwJGUjEXMBUGA1UEChMORnJhbmNlIFRlbGVj
b20xEzARBgNVBAsTCkZUUkQtQXNwaWMxFzAVBgNVBAMTDkZUUkQgQUMgUmFjaW5lggEAMA4GA1Ud
DwEB/wQEAwIBBjCBgAYDVR0fBHkwdzA/oD2gO4Y5aHR0cDovL2x1Y2lmZXIucmQuZnJhbmNldGVs
ZWNvbS5mci9yZXZvcXVlcy9jcmxyYWNpbmUuY3JsMDSgMqAwhi5odHRwOi8vcGtpLWwucmQuZnJh
bmNldGVsZWNvbS5mci9jcmxyYWNpbmUuY3JsMBEGCWCGSAGG+EIBAQQEAwIABzANBgkqhkiG9w0B
AQUFAAOCAQEAto0WYTNPzNN/XrdT255IwPKbYLZD/YRfQwwcbB4Ff6F9Km+J69KLpZZZx0Z/8rTs
jVFc3A2QHTMy4OB2vJ1qPMUO+JlahqhHbun4GHxM0xl9qzGAaveo5xvIMqHYUnnRZ6s8LadQVbkc
Hxgw4oPkwRGbKoGyT6WEdFhWmn4BOBuwURN/JL4LynTkwHEklDbheEyAVTOrJIbZ88rWAKOoSzDh
D+Wu/ZVvbcYuYNevqafJceD1g6rQhaz7O4HnGdmiau3/ayV7ZNDqxnm0Sfli4r4ltTi6GkxmEoT7
X1JdKuH0na0ZdYRoqxRopM8uLsFMOHc46GT7HwsNcqXctRpORDCCBLEwggOZoAMCAQICAhJyMA0G
CSqGSIb3DQEBBQUAMFwxCzAJBgNVBAYTAkZSMRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTETMBEG
A1UECxMKRlRSRC1Bc3BpYzEfMB0GA1UEAxMWRlRSRCBBQyBvcGVyYXRpb25uZWxsZTAeFw0wNDAx
MjYxNTQ4MDZaFw0wNzAxMjUxNTQ4MDZaMIGfMQswCQYDVQQGEwJGUjEXMBUGA1UEChMORnJhbmNl
IFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQVNQSUMxFzAVBgNVBAMTDkZyZWRlcmljIEtMQU1NMRgw
FgYKCZImiZPyLGQBARMIRllZSzYzMDIxLzAtBgkqhkiG9w0BCQEWIGZyZWRlcmljLmtsYW1tQGZy
YW5jZXRlbGVjb20uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC3B0gQecE85angjBZM
0t7xdp6WS6E/ytxMaQbie6NwAiNkAW9l0Fu6vT7jx3GLS4cfTCbU5SAndYc60UygxW/FY6JGeuGp
O2a0XqU+5XxgCBAmGvLPeotcYIV0PJ9sC5r5PVkVhnt6hQbQUXg/hRPRSrIAAYmK2H2vAhMRa2h8
cwIDAQABo4IBuzCCAbcwHQYDVR0OBBYEFFdpAJ5uxtUVDKoxYKgSNRS5LrZ5MB8GA1UdIwQYMBaA
FKeHuNCL9G/jwcDa7Y604KcQKfzYMIGSBgNVHR8EgYowgYcwR6BFoEOGQWh0dHA6Ly9sdWNpZmVy
LnJkLmZyYW5jZXRlbGVjb20uZnIvcmV2b3F1ZXMvY3Jsb3BlcmF0aW9ubmVsbGUuY3JsMDygOqA4
hjZodHRwOi8vcGtpLWwucmQuZnJhbmNldGVsZWNvbS5mci9jcmxvcGVyYXRpb25uZWxsZS5jcmww
DgYDVR0PAQH/BAQDAgbAMCkGA1UdJQQiMCAGCCsGAQUFBwMEBggrBgEFBQcDAgYKKwYBBAGCNxQC
AjARBglghkgBhvhCAQEEBAMCBaAwVgYDVR0RBE8wTaApBgorBgEEAYI3FAIDoBsMGWtsYW1tQHJk
LmZyYW5jZXRlbGVjb20uZnKBIGZyZWRlcmljLmtsYW1tQGZyYW5jZXRlbGVjb20uY29tMDoGCWCG
SAGG+EIBDQQtFitDZXJ0aWZpY2F0IGRlIFNpZ25hdHVyZSBwb3VyIEZyZWRlcmljIEtMQU1NMA0G
CSqGSIb3DQEBBQUAA4IBAQDvO3tde8iQP3opWmQCebHAFN1W6NWVXxlaZAWRcbZ+UbndCNyB+B8W
wipIctPzH+SGqZzgMH7XnLwhIcBsBKTwzq3SoIdB2lCvIwEyNjYE9zEUgaE/MgWJqz0KAHm1aYxS
X1JWYxkVfuqQxvZRTGmNX1pq8vksXQPKmcRcU2vBK9wQkGhmcivb7EBnK+JgNM1ir6H1tJ9GKN6Z
UOWH1t3fcxQibPtLOamxprhWfjlVA0FTFT3BIcHxp2UMwpyFVH0Hz/6PGlUP+NAOaqC6RYoZBAP8
a8IZcx1Vf7DdV1o48sfH5dj7PRFGyXXn1PLR9ZqaKjrfo/huZi3fWoCwUdhYMYICujCCArYCAQEw
YjBcMQswCQYDVQQGEwJGUjEXMBUGA1UEChMORnJhbmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQt
QXNwaWMxHzAdBgNVBAMTFkZUUkQgQUMgb3BlcmF0aW9ubmVsbGUCAhJyMAkGBSsOAwIaBQCgggGu
MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MDQxMDE0NDgzMVow
IwYJKoZIhvcNAQkEMRYEFNxIhH6NscY8JYWSwzIU7X9h+QyuMGcGCSqGSIb3DQEJDzFaMFgwCgYI
KoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMHEGCSsGAQQBgjcQBDFkMGIwXDELMAkGA1UEBhMC
RlIxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFzcGljMR8wHQYDVQQD
ExZGVFJEIEFDIG9wZXJhdGlvbm5lbGxlAgISczBzBgsqhkiG9w0BCRACCzFkoGIwXDELMAkGA1UE
BhMCRlIxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFzcGljMR8wHQYD
VQQDExZGVFJEIEFDIG9wZXJhdGlvbm5lbGxlAgISczANBgkqhkiG9w0BAQEFAASBgLK+9OzA98tt
YmugqbJzGdFO/pq91flipKWi5vDORecsXgumFK0RO7k26SYQrYnSckD4xC4M9ABEo0BqSFfep45P
Q/S7Oj+VH+X1UEJjRnWJw4Jh/IDKnmpHLs+LloYCuHgPDm6idipcPNsSVc0xDCstlxCZrcgZ77Wd
nFqSohDbAAAAAAAA

------=_NextPart_000_0072_01C65CBE.99B69820--


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

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6

--===============1684963765==--




From monami6-bounces@ietf.org Tue Apr 11 05:17:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTF0D-0006dj-Qi; Tue, 11 Apr 2006 05:17:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTF0C-0006dd-ND
	for monami6@ietf.org; Tue, 11 Apr 2006 05:17:36 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTF0C-0000aD-7Z
	for monami6@ietf.org; Tue, 11 Apr 2006 05:17:36 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B079D4F0003
	for <monami6@ietf.org>; Tue, 11 Apr 2006 11:17:35 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Apr 2006 11:17:34 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Apr 2006 11:17:34 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 3463E238E;
	Tue, 11 Apr 2006 12:17:34 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 0145B95C6A;
	Tue, 11 Apr 2006 12:17:34 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A130B95C4A;
	Tue, 11 Apr 2006 12:17:33 +0300 (EEST)
Message-ID: <443B7426.3010408@ericsson.com>
Date: Tue, 11 Apr 2006 12:17:26 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Changes needed to MCoA draft?
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
In-Reply-To: <F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 11 Apr 2006 09:17:34.0470 (UTC)
	FILETIME=[C4A34260:01C65D48]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


> 
> One idea is that we can separate bulk registration into separate document.
> I can remove the texts and move to the new document which will contain 
> your inputs, too.
> 
> However, before doing that, the draft must be WG document.
> This draft is still individual draft and not WG one.
> 
> I want to solicit the comments from WG chairs  first !!!
> 
> ryuji

Hello,

I think that the best way forward would be to split the current draft 
into two drafts. This first would be the current draft without the bulk 
option and the second a bulk extension to the first draft. Although it 
makes a lot of sense to support a bulk registration, because it saves a 
lot of bytes and more importantly signaling bytes, but it is still in 
essence just an optimization to the basic idea of inserting the BID option.

The current way of including the bulk possibility produces a lot of 
questions that the MCoA draft fails to answer clear enough. Moreover, 
the current draft's bulk registration works only with HAs and not with 
CNs, which is a situation that should be avoided. In my opinion the 
mechanism should work coherently among the target nodes. Being a 
separate draft, bulk registration issues would be easier to work on 
without needlessly stalling the MCoA draft.

-- 
Tero Kauppinen                                 Tel: +358 9 299 3057
Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
Oy L M Ericsson Ab
mailto:tero.kauppinen@ericsson.com

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 07:07:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTGia-0005jh-Oy; Tue, 11 Apr 2006 07:07:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTGiZ-0005i9-1g
	for monami6@ietf.org; Tue, 11 Apr 2006 07:07:31 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTGiY-0004gX-HD
	for monami6@ietf.org; Tue, 11 Apr 2006 07:07:31 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5B470212C63
	for <monami6@ietf.org>; Tue, 11 Apr 2006 14:07:29 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id E1398212C5F
	for <monami6@ietf.org>; Tue, 11 Apr 2006 14:07:28 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id 75E32BDC40
	for <monami6@ietf.org>; Tue, 11 Apr 2006 14:07:28 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id 420F1BDC38
	for <monami6@ietf.org>; Tue, 11 Apr 2006 14:07:28 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <443B7426.3010408@ericsson.com>
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
	<443B7426.3010408@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <910da3595853477a839bb5fbd7e79538@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
Date: Tue, 11 Apr 2006 14:07:28 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi all,


El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:

>
>> One idea is that we can separate bulk registration into separate=20
>> document.
>> I can remove the texts and move to the new document which will=20
>> contain your inputs, too.
>> However, before doing that, the draft must be WG document.
>> This draft is still individual draft and not WG one.
>> I want to solicit the comments from WG chairs  first !!!
>> ryuji
>
> Hello,
>
> I think that the best way forward would be to split the current draft=20=

> into two drafts. This first would be the current draft without the=20
> bulk option and the second a bulk extension to the first draft.=20
> Although it makes a lot of sense to support a bulk registration,=20
> because it saves a lot of bytes and more importantly signaling bytes,=20=

> but it is still in essence just an optimization to the basic idea of=20=

> inserting the BID option.
>
> The current way of including the bulk possibility produces a lot of=20
> questions that the MCoA draft fails to answer clear enough. Moreover,=20=

> the current draft's bulk registration works only with HAs and not with=20=

> CNs, which is a situation that should be avoided. In my opinion the=20
> mechanism should work coherently among the target nodes. Being a=20
> separate draft, bulk registration issues would be easier to work on=20
> without needlessly stalling the MCoA draft.
>


i am sorry but i fail to see the logic behind this line of reasoning.

I mean, whether we think that bulk registration is important or we don't

if we don't think it is important, we just drop it

if we think it is important, i guess we need to do it from day one. I=20
mean, i don't see the point in doing one spec that is incomplete and=20
lacks and important feature and 6 months later do a new spec with the=20
additional feature. I think that we need to do it once and do it right=20=

with all the important features. I mean, i guess we don't want to have=20=

to write first implementations with mcoa support version one (without=20
bulk registration) and then another implementation of mcoa version 2=20
(with bulk registration) and make the version 2 with bulk registration=20=

compatible with the mcoa version 1 (without bulk implementation)

This is even more critical in the case that you point out that the=20
current mcoa draft doens't seems to cleanly support the bulk=20
registration and the additional stuff will be needed for bulk=20
registration with CN. Do we know that the future bulk extensions can be=20=

created starting from the current mcoa draft that lacks of bulk=20
registration? or we may end up with two different mechanisms one=20
without bullk and another for bulk registration?

I think we need to make just one mechanism that provides all the=20
features that are needed and do it right in the first time

In addition, we are only chartered to do one MCOA docuemnts, not a=20
basic support and then MCOAs support optimizations, so i guess that we=20=

would need to recharter in order to this MCOA optimization support=20
draft, right?

So, my suggestion is to first figure out if bulk registration is needed=20=

or not.
If it is needed, produce a single spec (and a single implementation)=20
that supports all the desired features.

regards, marcelo



> --=20
> Tero Kauppinen                                 Tel: +358 9 299 3057
> Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> Ericsson Research, Corporate Unit.             Mobile: +358 40 590 =
7560
> Oy L M Ericsson Ab
> mailto:tero.kauppinen@ericsson.com
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 08:21:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTHru-0008MS-AQ; Tue, 11 Apr 2006 08:21:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTHrs-0008MN-Ml
	for monami6@ietf.org; Tue, 11 Apr 2006 08:21:12 -0400
Received: from posti6.jyu.fi ([130.234.4.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTHrs-0007Ne-0Z
	for monami6@ietf.org; Tue, 11 Apr 2006 08:21:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3BCLAE9020085
	for <monami6@ietf.org>; Tue, 11 Apr 2006 15:21:10 +0300
Received: from posti6.jyu.fi ([127.0.0.1])
	by localhost (posti6.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 19940-09 for <monami6@ietf.org>;
	Tue, 11 Apr 2006 15:21:07 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3BCL3EM020032
	for <monami6@ietf.org>; Tue, 11 Apr 2006 15:21:05 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
Date: Tue, 11 Apr 2006 15:20:57 +0300
User-Agent: KMail/1.9.1
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
In-Reply-To: <910da3595853477a839bb5fbd7e79538@it.uc3m.es>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200604111520.58537.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Marcelo and list,

On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
> Hi all,
>=20
>=20
> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
>=20
> >
> >> One idea is that we can separate bulk registration into separate=20
> >> document.
> >> I can remove the texts and move to the new document which will=20
> >> contain your inputs, too.
> >> However, before doing that, the draft must be WG document.
> >> This draft is still individual draft and not WG one.
> >> I want to solicit the comments from WG chairs  first !!!
> >> ryuji
> >
> > Hello,
> >
> > I think that the best way forward would be to split the current draft=20
> > into two drafts. This first would be the current draft without the=20
> > bulk option and the second a bulk extension to the first draft.=20
> > Although it makes a lot of sense to support a bulk registration,=20
> > because it saves a lot of bytes and more importantly signaling bytes,=20
> > but it is still in essence just an optimization to the basic idea of=20
> > inserting the BID option.
> >
> > The current way of including the bulk possibility produces a lot of=20
> > questions that the MCoA draft fails to answer clear enough. Moreover,=20
> > the current draft's bulk registration works only with HAs and not with=
=20
> > CNs, which is a situation that should be avoided. In my opinion the=20
> > mechanism should work coherently among the target nodes. Being a=20
> > separate draft, bulk registration issues would be easier to work on=20
> > without needlessly stalling the MCoA draft.
> >
>=20
>=20
> i am sorry but i fail to see the logic behind this line of reasoning.
>=20
> I mean, whether we think that bulk registration is important or we don't
>=20
> if we don't think it is important, we just drop it
>=20
> if we think it is important, i guess we need to do it from day one. I=20
> mean, i don't see the point in doing one spec that is incomplete and=20
> lacks and important feature and 6 months later do a new spec with the=20
> additional feature. I think that we need to do it once and do it right=20

I don't think Tero meant creating a "new spec". I guess it'd be more
like an addition. At least I hope.

I don't think it is a problem to have two separate drafts (they are
only drafts anyway). In that case, the basic MCoA draft should drop all
the "bulk registration" related text.

But I would suggest someone taking the MCoA draft and rewrite it with
bulk in mind from scratch and just see how it shapes up. I don't think
it would hurt. E.g. Martti Kuparinen had quite nice ideas...

> with all the important features. I mean, i guess we don't want to have=20
> to write first implementations with mcoa support version one (without=20
> bulk registration) and then another implementation of mcoa version 2=20
> (with bulk registration) and make the version 2 with bulk registration=20
> compatible with the mcoa version 1 (without bulk implementation)

If bulk-reg is an add-on draft then I think it is no problem.
By add-on I mean that mcoa can be easily extended to support bulk-reg.
In this case I see one complication in the error handling, e.g.
"What if a bulk-mcoa MN talks to a non-bulk-mcoa implementer CN?"

>=20
> This is even more critical in the case that you point out that the=20
> current mcoa draft doens't seems to cleanly support the bulk=20
> registration and the additional stuff will be needed for bulk=20
> registration with CN. Do we know that the future bulk extensions can be=20
> created starting from the current mcoa draft that lacks of bulk=20
> registration? or we may end up with two different mechanisms one=20
> without bullk and another for bulk registration?
>=20
> I think we need to make just one mechanism that provides all the=20
> features that are needed and do it right in the first time
>=20
> In addition, we are only chartered to do one MCOA docuemnts, not a=20
> basic support and then MCOAs support optimizations, so i guess that we=20
> would need to recharter in order to this MCOA optimization support=20
> draft, right?
>=20
> So, my suggestion is to first figure out if bulk registration is needed=20
> or not.

IMO, bulk-reg reduces signaling overhead. The problem is currently
there are no services (at least I am not aware) deployed using mipv6
and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot up
and if you have multiple CoAs on a single interface. But in the latter case
will it be common in the future to have ipv6 subnets with multiple network
prefixes? So for me it's a bit like planning blind and whether we need it
or not may not be that clear at this point. Or am I saying bull?

I say, just create a draft for bulk (either rewrite mcoa or create a=20
separate draft and drop bulk-reg from mcoa) and
see if the result is over-complicated or simple and clean.

> If it is needed, produce a single spec (and a single implementation)=20
> that supports all the desired features.
>=20
> regards, marcelo
>=20
>=20
>=20
> > --=20
> > Tero Kauppinen                                 Tel: +358 9 299 3057
> > Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> > Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
> > Oy L M Ericsson Ab
> > mailto:tero.kauppinen@ericsson.com
> >
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 08:41:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTIBH-0005La-5s; Tue, 11 Apr 2006 08:41:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTIBG-0005LV-3i
	for monami6@ietf.org; Tue, 11 Apr 2006 08:41:14 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTIBF-0008G7-B3
	for monami6@ietf.org; Tue, 11 Apr 2006 08:41:14 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1A721DB4
	for <monami6@ietf.org>; Tue, 11 Apr 2006 14:41:12 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Apr 2006 14:41:11 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Apr 2006 14:41:11 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0EA17238E;
	Tue, 11 Apr 2006 15:41:11 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id D286C95C6A;
	Tue, 11 Apr 2006 15:41:10 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 6F35395C4A;
	Tue, 11 Apr 2006 15:41:10 +0300 (EEST)
Message-ID: <443BA3DE.1070404@ericsson.com>
Date: Tue, 11 Apr 2006 15:41:02 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
References: <4422AFBF.7080603@nomadiclab.com>
	<443B7426.3010408@ericsson.com>	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
In-Reply-To: <200604111520.58537.feketgai@index.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: ClamAV using ClamSMTP
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 11 Apr 2006 12:41:11.0264 (UTC)
	FILETIME=[366A1600:01C65D65]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

G=E1bor Fekete wrote:
> Hi Marcelo and list,
>=20
> On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
>> Hi all,
>>
>>
>> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
>>
>>...
>>
>> i am sorry but i fail to see the logic behind this line of reasoning.
>>
>> I mean, whether we think that bulk registration is important or we don=
't
>>
>> if we don't think it is important, we just drop it
>>
>> if we think it is important, i guess we need to do it from day one. I=20
>> mean, i don't see the point in doing one spec that is incomplete and=20

IMO, it is an optimization because the protocol works without it. I=20
would not say that the spec would be "incomplete and lack an important=20
feature", but that is just my opinion.

>> lacks and important feature and 6 months later do a new spec with the=20
>> additional feature. I think that we need to do it once and do it right=
=20
>=20
> I don't think Tero meant creating a "new spec". I guess it'd be more
> like an addition. At least I hope.
>=20

You got my point.

>=20
> IMO, bulk-reg reduces signaling overhead. The problem is currently
> there are no services (at least I am not aware) deployed using mipv6
> and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot =
up
> and if you have multiple CoAs on a single interface. But in the latter =
case
> will it be common in the future to have ipv6 subnets with multiple netw=
ork
> prefixes? So for me it's a bit like planning blind and whether we need =
it
> or not may not be that clear at this point. Or am I saying bull?

I don't think you're "saying bull". It is a good question that I have=20
also tried to find an answer for ... not succeeding that much, though. I=20
would say that reducing signaling overhead is a pretty strong argument=20
that justifies the existence of bulk-reg.

Regz,
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 09:07:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTIaH-0007Et-4b; Tue, 11 Apr 2006 09:07:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTIaF-0007Eo-OX
	for monami6@ietf.org; Tue, 11 Apr 2006 09:07:03 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTIaE-0000oJ-UQ
	for monami6@ietf.org; Tue, 11 Apr 2006 09:07:03 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 295DE212C65
	for <monami6@ietf.org>; Tue, 11 Apr 2006 16:07:01 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id E5D34212C64
	for <monami6@ietf.org>; Tue, 11 Apr 2006 16:07:00 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id 6F31CBDC40
	for <monami6@ietf.org>; Tue, 11 Apr 2006 16:07:00 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id 35103BDC38
	for <monami6@ietf.org>; Tue, 11 Apr 2006 16:07:00 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <200604111520.58537.feketgai@index.hu>
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <6780888f55d5ce9cbde5632b3473a5ce@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
Date: Tue, 11 Apr 2006 16:06:59 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1f9797ba297220533cb8c3f4bc709a8
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

El 11/04/2006, a las 15:20, G=E1bor Fekete escribi=F3:

> Hi Marcelo and list,
>
> On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
>> Hi all,
>>
>>
>> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
>>
>>>
>>>> One idea is that we can separate bulk registration into separate
>>>> document.
>>>> I can remove the texts and move to the new document which will
>>>> contain your inputs, too.
>>>> However, before doing that, the draft must be WG document.
>>>> This draft is still individual draft and not WG one.
>>>> I want to solicit the comments from WG chairs  first !!!
>>>> ryuji
>>>
>>> Hello,
>>>
>>> I think that the best way forward would be to split the current =
draft
>>> into two drafts. This first would be the current draft without the
>>> bulk option and the second a bulk extension to the first draft.
>>> Although it makes a lot of sense to support a bulk registration,
>>> because it saves a lot of bytes and more importantly signaling =
bytes,
>>> but it is still in essence just an optimization to the basic idea of
>>> inserting the BID option.
>>>
>>> The current way of including the bulk possibility produces a lot of
>>> questions that the MCoA draft fails to answer clear enough. =
Moreover,
>>> the current draft's bulk registration works only with HAs and not=20
>>> with
>>> CNs, which is a situation that should be avoided. In my opinion the
>>> mechanism should work coherently among the target nodes. Being a
>>> separate draft, bulk registration issues would be easier to work on
>>> without needlessly stalling the MCoA draft.
>>>
>>
>>
>> i am sorry but i fail to see the logic behind this line of reasoning.
>>
>> I mean, whether we think that bulk registration is important or we=20
>> don't
>>
>> if we don't think it is important, we just drop it
>>
>> if we think it is important, i guess we need to do it from day one. I
>> mean, i don't see the point in doing one spec that is incomplete and
>> lacks and important feature and 6 months later do a new spec with the
>> additional feature. I think that we need to do it once and do it =
right
>
> I don't think Tero meant creating a "new spec". I guess it'd be more
> like an addition. At least I hope.
>

but we don't know if the addition would fit in the existent MCOA draft,=20=

don't we? I mean, there seems to be several issues with adding bulk=20
registration support to the mcoa draft right? if this is so, it is not=20=

clear to me at this point that it would be straightforward to extend=20
the current mcoa draft to support bulk registration and solve all the=20
issues.

Moreover, i don't think it is a good strategy. I mean, if we know now=20
that bulk registration is an important feature, then why to first adopt=20=

a mcoa draft that has not bulk registration and later figure out if we=20=

can fit in this draft the bulk registration stuff.... it doesn't make=20
sense to me... If we are designing the mcoa support now and we consider=20=

that bulk registration is needed, we better design the mcoa support=20
with this in mind and make sure that the basic mcoa support provides=20
the features that we need.... I mean i understand making hacks in=20
implementaions and specs when unforseen requirements appear, but this=20
is already here and we haven't defined the solution yet, so i don't=20
think that the best approach would be to ignore future features and see=20=

how they fit in later...

> I don't think it is a problem to have two separate drafts (they are
> only drafts anyway). In that case, the basic MCoA draft should drop =
all
> the "bulk registration" related text.
>

but what is the point in having two draft?

my point is that we need to figure out how this bulk registration stuff=20=

fits in the mcoa support anyway in order to do it right so, i guess we=20=

can do it once and for all

> But I would suggest someone taking the MCoA draft and rewrite it with
> bulk in mind from scratch and just see how it shapes up. I don't think
> it would hurt. E.g. Martti Kuparinen had quite nice ideas...
>

yes, this is the approach that i would suggest, try to figure out how a=20=

mechanism to support mcoa registration and bulk registration would look=20=

like

>> with all the important features. I mean, i guess we don't want to =
have
>> to write first implementations with mcoa support version one (without
>> bulk registration) and then another implementation of mcoa version 2
>> (with bulk registration) and make the version 2 with bulk =
registration
>> compatible with the mcoa version 1 (without bulk implementation)
>
> If bulk-reg is an add-on draft then I think it is no problem.
> By add-on I mean that mcoa can be easily extended to support bulk-reg.

but we don't know that at this point, since we haven't figured out how=20=

to address the issues that were brought up about bulk registration in=20
the current mcoa draft right?

so maybe we accept this mcoa draft as the first solution and then we=20
need to do nasty hacks to include the bulk registration stuff... this=20
doesn't seems to me a good strategy for protocol design. we need to=20
figure out the big picture and define a solutions that are extensible=20
to deal with all the features that we consider important

so, if we know now that we want this, then we should do it since the=20
begining...

> In this case I see one complication in the error handling, e.g.
> "What if a bulk-mcoa MN talks to a non-bulk-mcoa implementer CN?"
>

this is just one of the issues that may appear....
i mean since day one we will have multiple vrsions of the mcoa=20
registration support.... i don't think this is the best approach


>>
>> This is even more critical in the case that you point out that the
>> current mcoa draft doens't seems to cleanly support the bulk
>> registration and the additional stuff will be needed for bulk
>> registration with CN. Do we know that the future bulk extensions can=20=

>> be
>> created starting from the current mcoa draft that lacks of bulk
>> registration? or we may end up with two different mechanisms one
>> without bullk and another for bulk registration?
>>
>> I think we need to make just one mechanism that provides all the
>> features that are needed and do it right in the first time
>>
>> In addition, we are only chartered to do one MCOA docuemnts, not a
>> basic support and then MCOAs support optimizations, so i guess that =
we
>> would need to recharter in order to this MCOA optimization support
>> draft, right?
>>
>> So, my suggestion is to first figure out if bulk registration is=20
>> needed
>> or not.
>
> IMO, bulk-reg reduces signaling overhead. The problem is currently
> there are no services (at least I am not aware) deployed using mipv6
> and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot=20=

> up
> and if you have multiple CoAs on a single interface.

Do you think that bulk registration will only be usefull for multiple=20
coas in a single interface? why is that?

>  But in the latter case
> will it be common in the future to have ipv6 subnets with multiple=20
> network
> prefixes?

well, multihomed networks are expected to have multiple prefixes (at=20
least in several cases) so i guess this may be pretty common (just=20
guessing of course)

>  So for me it's a bit like planning blind and whether we need it
> or not may not be that clear at this point. Or am I saying bull?
>

> I say, just create a draft for bulk (either rewrite mcoa or create a
> separate draft and drop bulk-reg from mcoa) and
> see if the result is over-complicated or simple and clean.
>

fully agree, but this is needed before taking on the work in the=20
current mcoa draft in the wg, so that we can figure out if a mcoa=20
mechanism that supports bulk registration is compatible or not with the=20=

current mcoa draft... agree?

regards, marcelo



>> If it is needed, produce a single spec (and a single implementation)
>> that supports all the desired features.
>>
>> regards, marcelo
>>
>>
>>
>>> --=20
>>> Tero Kauppinen                                 Tel: +358 9 299 3057
>>> Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
>>> Ericsson Research, Corporate Unit.             Mobile: +358 40 590=20=

>>> 7560
>>> Oy L M Ericsson Ab
>>> mailto:tero.kauppinen@ericsson.com
>>>
>>> _______________________________________________
>>> Monami6 mailing list
>>> Monami6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/monami6
>>>
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 10:50:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTKC3-0004qw-9M; Tue, 11 Apr 2006 10:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTKC1-0004qn-Ov
	for monami6@ietf.org; Tue, 11 Apr 2006 10:50:09 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTKC1-0004Su-7Y
	for monami6@ietf.org; Tue, 11 Apr 2006 10:50:09 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3BEo8UO026470
	for <monami6@ietf.org>; Tue, 11 Apr 2006 17:50:08 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 26433-03 for <monami6@ietf.org>;
	Tue, 11 Apr 2006 17:50:08 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3BEo7Ra026466
	for <monami6@ietf.org>; Tue, 11 Apr 2006 17:50:08 +0300
Content-Disposition: inline
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
Date: Tue, 11 Apr 2006 17:50:02 +0300
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200604111750.02292.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Marcelo and Tero and list,

On Tuesday 11 April 2006 16:06, marcelo bagnulo braun wrote:
> ...
> 
> > I don't think it is a problem to have two separate drafts (they are
> > only drafts anyway). In that case, the basic MCoA draft should drop all
> > the "bulk registration" related text.
> >
> 
> but what is the point in having two draft?

to keep everyone happy :) well, i am not thinking about drafts written in
stone. ok, i don't really know how it goes, but my idea is to create drafts
and then just pick the one that's the best; or mix and match and create
the One True Draft. and if it means there won't be an MCOA WG draft by "next week"
then be it. yes, actually, is there any hard deadline?

> 
> my point is that we need to figure out how this bulk registration stuff 
> fits in the mcoa support anyway in order to do it right so, i guess we 
> can do it once and for all
> 
> > But I would suggest someone taking the MCoA draft and rewrite it with
> > bulk in mind from scratch and just see how it shapes up. I don't think
> > it would hurt. E.g. Martti Kuparinen had quite nice ideas...
> >
> 
> yes, this is the approach that i would suggest, try to figure out how a 
> mechanism to support mcoa registration and bulk registration would look 
> like
> 
> ...
>
> > In this case I see one complication in the error handling, e.g.
> > "What if a bulk-mcoa MN talks to a non-bulk-mcoa implementer CN?"
> >
> 
> this is just one of the issues that may appear....
> i mean since day one we will have multiple vrsions of the mcoa 
> registration support.... i don't think this is the best approach

there would not be multiple versions, i think people here are smarter than
that ;) but yes, i get your point.

> >
> > IMO, bulk-reg reduces signaling overhead. The problem is currently
> > there are no services (at least I am not aware) deployed using mipv6
> > and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot 
> > up
> > and if you have multiple CoAs on a single interface.
> 
> Do you think that bulk registration will only be usefull for multiple 
> coas in a single interface? why is that?

i did not say "only", i said "e.g." on purpose :)
but ok. let's take a MN with 3 interfaces (I think the one-iface
scenario is obvious, we need bulk-reg if we have multi-coa on that iface).
I assume that one BU can tell the story of only one HoA, is it right? 
then, suppose the MN is booted and already has multi-coa bindings
with CN for the 3 ifaces. and also suppose that there is one CoA per
iface. So CN's bcache has an entry like:

     +- CoA1 - BID1
     | 
HoA -+- CoA2 - BID2
     |
     +- CoA3 - BID3    

You need to send bulk-reg to CN if you want to change multiple BIDs at CN, but
otherwise you are fine with non-bulk. Now, each CoA belongs to a different
iface. Therefore, the event that causes you to send a bulk-reg to CN is
actually a combination of events happening "at the same time" w.r.t different
interfaces. This assumes an MN implementation that is intelligent enough
to aggregate events and send bulk-reg whenever possible.
so, yes, in this scenario a MN may use bulk-reg if it is smart enough.
errrr... well, so my point is, yes, in this scenario bulk-reg is a nice
feature but may be used by less implementations than the boot-up and
multi-prefix cases.

> 
> >  But in the latter case
> > will it be common in the future to have ipv6 subnets with multiple 
> > network
> > prefixes?
> 
> well, multihomed networks are expected to have multiple prefixes (at 
> least in several cases) so i guess this may be pretty common (just 
> guessing of course)

ok. i guess there may be many multihomed sites...

> 
> >  So for me it's a bit like planning blind and whether we need it
> > or not may not be that clear at this point. Or am I saying bull?
> >
> 
> > I say, just create a draft for bulk (either rewrite mcoa or create a
> > separate draft and drop bulk-reg from mcoa) and
> > see if the result is over-complicated or simple and clean.
> >
> 
> fully agree, but this is needed before taking on the work in the 
> current mcoa draft in the wg, so that we can figure out if a mcoa 
> mechanism that supports bulk registration is compatible or not with the 
> current mcoa draft... agree?

yes. so, again. I suggest to
1) make a non-bulk mcoa and make an add-on bulk-reg draft.
   I wonder if Ryuji already started this work.

and

2) make a bulk-reg mcoa draft from scratch?

That's all. And yes, maybe Tero (and others) already has ideas about
the add-on bulk-reg draft that is why he's suggesting the 2-draft scenario.
Or am I wrong?

I think that Ryuji wants to keep the mcoa draft as simple as possible and
he may be afraid that a full-featured bulk-reg text would overcomplicate it.
If it's not the case then neither I see point in having a non-bulk and
a bulk drafts parallel. And probably there is a WG deadline for the MCoA
draft...

But i may say no more since I just blabla and not writing the drafts :)

thanks,
gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 11:14:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTKZl-0006gH-EK; Tue, 11 Apr 2006 11:14:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTKZk-0006gC-I5
	for monami6@ietf.org; Tue, 11 Apr 2006 11:14:40 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTKZj-0005h6-4q
	for monami6@ietf.org; Tue, 11 Apr 2006 11:14:40 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3BFEbuJ001182; Tue, 11 Apr 2006 17:14:37 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3BFEZDd001172; Tue, 11 Apr 2006 17:14:35 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3BFEXTv018927
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 11 Apr 2006 17:14:35 +0200
Message-ID: <443BC71A.3020401@enst-bretagne.fr>
Date: Tue, 11 Apr 2006 17:11:22 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
Subject: [Monami6] MCoA draft
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Folks,

According to the discussion at Vancounver and Dallas, we think that we
reached a rough consensus to accept

Multiple Care-of addresses registration
draft-wakikawa-mobileip-multiplecoa-05

as a WG document for the 3rd deliverable:

   - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
Support (RFC 3963) to support the registration of multiple Care-of
Addresses at a given Home Agent address [Standard Track].

The document has been improved between the 2 IETF meetings in a way that 
we think meets the request of the WG members as expressed at Vancouver. 
The document will therefore be forwarded to the IETF secretariat.

In the meantime, do not hesitate to (continue to) comment on the draft.

Nicolas & Thierry.


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 11 11:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTKcf-0008Cl-AO; Tue, 11 Apr 2006 11:17:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTKce-0008CV-DO
	for monami6@ietf.org; Tue, 11 Apr 2006 11:17:40 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTKce-0005nh-0b
	for monami6@ietf.org; Tue, 11 Apr 2006 11:17:40 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3BFHdkH001373
	for <monami6@ietf.org>; Tue, 11 Apr 2006 17:17:39 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3BFHZcA001368
	for <monami6@ietf.org>; Tue, 11 Apr 2006 17:17:35 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3BFHX19018940
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <monami6@ietf.org>; Tue, 11 Apr 2006 17:17:35 +0200
Message-ID: <443BC7CE.5080600@enst-bretagne.fr>
Date: Tue, 11 Apr 2006 17:14:22 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
References: <200604111750.02292.feketgai@index.hu>
In-Reply-To: <200604111750.02292.feketgai@index.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	laposte.rennes.enst-bretagne.fr id k3BFHdkH001373
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Gabor,

G=E1bor Fekete wrote:

>Hi Marcelo and Tero and list,
>
>On Tuesday 11 April 2006 16:06, marcelo bagnulo braun wrote:
> =20
>
>>...
>>
>>   =20
>>
>>>I don't think it is a problem to have two separate drafts (they are
>>>only drafts anyway). In that case, the basic MCoA draft should drop al=
l
>>>the "bulk registration" related text.
>>>
>>>     =20
>>>
>>but what is the point in having two draft?
>>   =20
>>
>
>to keep everyone happy :) well, i am not thinking about drafts written i=
n
>stone. ok, i don't really know how it goes, but my idea is to create dra=
fts
>and then just pick the one that's the best; or mix and match and create
>the One True Draft. and if it means there won't be an MCOA WG draft by "=
next week"
>then be it. yes, actually, is there any hard deadline?
> =20
>
Yes there is (from the charter at=20
http://ietf.org/html.charters/monami6-charter.html) :

Jun 2005  Submit Multiple CoA Registration to IESG

Regards,

Nicolas

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 01:29:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTXuU-00036l-TH; Wed, 12 Apr 2006 01:28:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTXuO-00036f-MR
	for monami6@ietf.org; Wed, 12 Apr 2006 01:28:52 -0400
Received: from smtp.mei.co.jp ([133.183.129.25] helo=smtp1.mei.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTXuF-0006jo-0T
	for monami6@ietf.org; Wed, 12 Apr 2006 01:28:52 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp1.mei.co.jp (8.12.11.20060308/3.7W/jazz) with ESMTP id
	k3C5SenH021442
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:28:40 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	k3C5Se512521
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:28:40 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with ESMTP id
	k3C5SeG17534
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:28:40 +0900 (JST)
Received: from bach.sg.panasonic.com ([10.81.113.99]) by pslexc01.psl.local
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 13:27:11 +0800
Received: by bach.sg.panasonic.com (Postfix, from userid 1000)
	id 499C2D54BE; Wed, 12 Apr 2006 13:36:35 +0800 (SGT)
Subject: Re: [Monami6] MCoA draft
From: Chan-Wah Ng <chanwah.ng@sg.panasonic.com>
To: Monami6 WG <monami6@ietf.org>
In-Reply-To: <443BC71A.3020401@enst-bretagne.fr>
References: <443BC71A.3020401@enst-bretagne.fr>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 12 Apr 2006 13:36:34 +0800
Message-Id: <1144820195.24464.16.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
X-OriginalArrivalTime: 12 Apr 2006 05:27:11.0187 (UTC)
	FILETIME=[BFBB6A30:01C65DF1]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
> Folks,
> 
> According to the discussion at Vancounver and Dallas, we think that we
> reached a rough consensus to accept

Really?  Unless you call a ratio of less than 3 (for) : 1 (against) a
"rough consensus" (which was what I counted in Dallas).

> 
> Multiple Care-of addresses registration
> draft-wakikawa-mobileip-multiplecoa-05
> 
> as a WG document for the 3rd deliverable:
> 
>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
> Support (RFC 3963) to support the registration of multiple Care-of
> Addresses at a given Home Agent address [Standard Track].
> 
> The document has been improved between the 2 IETF meetings in a way that 
> we think meets the request of the WG members as expressed at Vancouver. 

Again, as mentioned in ML: I see at least two unresolved issues:

- Bulk Registrations.
- Simultaneously at home and foreign.


Having said all that, I am not against moving the draft to WG draft.  In
fact, changing it to WG draft would force us to maintain an issue list,
then we will truly know how many issues there are.  I just wanted to
keep the fact rights.

/rgds
/cwng

> The document will therefore be forwarded to the IETF secretariat.
> 
> In the meantime, do not hesitate to (continue to) comment on the draft.
> 
> Nicolas & Thierry.
> 
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 02:09:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTYXg-0005Pn-VD; Wed, 12 Apr 2006 02:09:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTYXf-0005Om-1v
	for monami6@ietf.org; Wed, 12 Apr 2006 02:09:27 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTYXb-0007mv-Ix
	for monami6@ietf.org; Wed, 12 Apr 2006 02:09:27 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3C69Mss010585
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:09:22 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3C69KSJ010581
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:09:21 +0200
Received: from [82.240.205.125] (sud35-3-82-240-205-125.fbx.proxad.net
	[82.240.205.125]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3C69JQJ020251
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:09:20 +0200
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <1144820195.24464.16.camel@localhost>
References: <443BC71A.3020401@enst-bretagne.fr>
	<1144820195.24464.16.camel@localhost>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <60BE7F1C-66BE-4F47-8B2C-ABE84A665769@enst-bretagne.fr>
Content-Transfer-Encoding: 7bit
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Subject: Re: [Monami6] MCoA draft
Date: Wed, 12 Apr 2006 08:05:09 +0200
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.749.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

On Apr 12, 2006, at 7:36 AM, Chan-Wah Ng wrote:

> On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
>> Folks,
>>
>> According to the discussion at Vancounver and Dallas, we think  
>> that we
>> reached a rough consensus to accept
>
> Really?  Unless you call a ratio of less than 3 (for) : 1 (against) a
> "rough consensus" (which was what I counted in Dallas).

Most of people were for the adoption of the document as a WG  
document, including AD and chair of other WG.

The few people who were against failed to show major concerns (some  
issues are still unresolved of course, but this can be dealt while  
the document is a WG document.

>
>>
>> Multiple Care-of addresses registration
>> draft-wakikawa-mobileip-multiplecoa-05
>>
>> as a WG document for the 3rd deliverable:
>>
>>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
>> Support (RFC 3963) to support the registration of multiple Care-of
>> Addresses at a given Home Agent address [Standard Track].
>>
>> The document has been improved between the 2 IETF meetings in a  
>> way that
>> we think meets the request of the WG members as expressed at  
>> Vancouver.
>
> Again, as mentioned in ML: I see at least two unresolved issues:
>
> - Bulk Registrations.
> - Simultaneously at home and foreign.

Sure, but we didn't say that the document is ready for the IESG.

>
>
> Having said all that, I am not against moving the draft to WG  
> draft.  In
> fact, changing it to WG draft would force us to maintain an issue  
> list,
> then we will truly know how many issues there are.

That's exactly our point, we believe that it is the best way to work  
on the document.

Nicolas

> I just wanted to
> keep the fact rights.
>
> /rgds
> /cwng
>
>> The document will therefore be forwarded to the IETF secretariat.
>>
>> In the meantime, do not hesitate to (continue to) comment on the  
>> draft.
>>
>> Nicolas & Thierry.
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 04:30:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTakR-0002Ne-Kg; Wed, 12 Apr 2006 04:30:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTakQ-0002NZ-TS
	for monami6@ietf.org; Wed, 12 Apr 2006 04:30:46 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTakQ-0004fR-CE
	for monami6@ietf.org; Wed, 12 Apr 2006 04:30:46 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 7999A212C63
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:30:44 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id 1936D212C5F
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:30:44 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id A4A22BDC40
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:30:43 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id 71CF0BDC38
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:30:43 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <60BE7F1C-66BE-4F47-8B2C-ABE84A665769@enst-bretagne.fr>
References: <443BC71A.3020401@enst-bretagne.fr>
	<1144820195.24464.16.camel@localhost>
	<60BE7F1C-66BE-4F47-8B2C-ABE84A665769@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <7c33e94a3484445558456f4277735bc5@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [Monami6] MCoA draft
Date: Wed, 12 Apr 2006 11:30:42 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

I must say that i fully agree with Chan-Wah here...

El 12/04/2006, a las 9:05, Nicolas Montavont escribi=F3:

> Hi,
>
> On Apr 12, 2006, at 7:36 AM, Chan-Wah Ng wrote:
>
>> On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
>>> Folks,
>>>
>>> According to the discussion at Vancounver and Dallas, we think that=20=

>>> we
>>> reached a rough consensus to accept
>>
>> Really?  Unless you call a ratio of less than 3 (for) : 1 (against) a
>> "rough consensus" (which was what I counted in Dallas).
>
> Most of people were for the adoption of the document as a WG document,=20=

> including AD and chair of other WG.
>
> The few people who were against failed to show major concerns (some=20
> issues are still unresolved of course, but this can be dealt while the=20=

> document is a WG document.
>

that is not what i recall from the meeting.

imho there was not clear rough consensus in the dallas meeting


however, the decision must be taken on the list i guess

>>
>>>
>>> Multiple Care-of addresses registration
>>> draft-wakikawa-mobileip-multiplecoa-05
>>>
>>> as a WG document for the 3rd deliverable:
>>>
>>>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
>>> Support (RFC 3963) to support the registration of multiple Care-of
>>> Addresses at a given Home Agent address [Standard Track].
>>>
>>> The document has been improved between the 2 IETF meetings in a way=20=

>>> that
>>> we think meets the request of the WG members as expressed at=20
>>> Vancouver.
>>
>> Again, as mentioned in ML: I see at least two unresolved issues:
>>
>> - Bulk Registrations.
>> - Simultaneously at home and foreign.
>
> Sure, but we didn't say that the document is ready for the IESG.
>

but there was a consensus call in the ml sent by Thierry and people=20
brought up those issues as problems in order to accept this  draft as=20
wg item (not in order to sent it to the IESG).

this, as i understand it, means that there is no consensus to accept=20
this document as a wg item until there is not a clear agreement in=20
these issues


in particular, i am concerned about the bulk registration issue. imho=20
this is a major issue, because it is not obvious to me that the current=20=

draft can be extended to support bulk registration cleanly. I would=20
like to understand if we think that bulk registration is needed, and if=20=

it is, how can be fitted into the mcoa draft neatly, without being=20
caught in a draft that doesn't naturally includes such feature. That is=20=

why i think more analysis is needed in this point.

>>
>>
>> Having said all that, I am not against moving the draft to WG draft. =20=

>> In
>> fact, changing it to WG draft would force us to maintain an issue=20
>> list,
>> then we will truly know how many issues there are.
>
> That's exactly our point, we believe that it is the best way to work=20=

> on the document.
>

probably, but the point is that there is no consensus to work on this=20
document yet since there is no consensus to accept it as a wg item=20
(yet)

regards, marcelo


> Nicolas
>
>> I just wanted to
>> keep the fact rights.
>>
>> /rgds
>> /cwng
>>
>>> The document will therefore be forwarded to the IETF secretariat.
>>>
>>> In the meantime, do not hesitate to (continue to) comment on the=20
>>> draft.
>>>
>>> Nicolas & Thierry.
>>>
>>>
>>> _______________________________________________
>>> Monami6 mailing list
>>> Monami6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/monami6
>>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 04:47:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTb0o-0001Kr-Qy; Wed, 12 Apr 2006 04:47:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTb0n-0001Km-2a
	for monami6@ietf.org; Wed, 12 Apr 2006 04:47:41 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTb0m-0004vE-Jj
	for monami6@ietf.org; Wed, 12 Apr 2006 04:47:41 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id AD5ED212C63
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:47:39 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id 76EB2212C5F
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:47:39 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id 39328BDC40
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:47:39 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id 0618BBDC38
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:47:39 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <443BC7CE.5080600@enst-bretagne.fr>
References: <200604111750.02292.feketgai@index.hu>
	<443BC7CE.5080600@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <0aaf038e01e0fe11a36ff4073c5e329d@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
Date: Wed, 12 Apr 2006 11:47:38 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


El 11/04/2006, a las 18:14, Nicolas Montavont escribi=F3:

> Gabor,
>
> G=E1bor Fekete wrote:
>
>> Hi Marcelo and Tero and list,
>>
>> On Tuesday 11 April 2006 16:06, marcelo bagnulo braun wrote:
>>
>>> ...
>>>
>>>
>>>> I don't think it is a problem to have two separate drafts (they are
>>>> only drafts anyway). In that case, the basic MCoA draft should drop=20=

>>>> all
>>>> the "bulk registration" related text.
>>>>
>>>>
>>> but what is the point in having two draft?
>>>
>>
>> to keep everyone happy :) well, i am not thinking about drafts=20
>> written in
>> stone. ok, i don't really know how it goes, but my idea is to create=20=

>> drafts
>> and then just pick the one that's the best; or mix and match and=20
>> create
>> the One True Draft. and if it means there won't be an MCOA WG draft=20=

>> by "next week"
>> then be it. yes, actually, is there any hard deadline?
>>
> Yes there is (from the charter at=20
> http://ietf.org/html.charters/monami6-charter.html) :
>
> Jun 2005  Submit Multiple CoA Registration to IESG
>

you are right, this is what the web page states but this is really=20
strange... the monami6 working group was formed in the 30 september of=20=

2005, which makes me wonder how would it be possible to be on schedule=20=

and submit documents to the IESG  3 months before the group was ever=20
created....


so i don't think this is hard deadline, since it has always been=20
impossible to make it....

i really think we need to update the charter to include more realistic=20=

dates on it, like ones that do not require traveling in time in order=20
to be able to accomplish them... :-)


> Regards,
>
> Nicolas
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 04:56:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTb8y-0004sS-DF; Wed, 12 Apr 2006 04:56:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTb8x-0004pV-7p
	for monami6@ietf.org; Wed, 12 Apr 2006 04:56:07 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTb8w-00053x-Pl
	for monami6@ietf.org; Wed, 12 Apr 2006 04:56:07 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id D34BE212C63
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:56:05 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id 9289E212C5F
	for <monami6@ietf.org>; Wed, 12 Apr 2006 11:56:05 +0300 (EEST)
Message-ID: <443CC0B2.9020004@nomadiclab.com>
Date: Wed, 12 Apr 2006 11:56:18 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Problem with MCoA draft?!
References: <4422AC28.6020000@nomadiclab.com>	<254DFE31-8067-4429-A23F-9A1E494E5BA8@sfc.wide.ad.jp>	<442A4191.90504@nomadiclab.com>
	<6.2.3.4.2.20060407133704.0a6b9d60@inc.inetcore.com>
In-Reply-To: <6.2.3.4.2.20060407133704.0a6b9d60@inc.inetcore.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Ken,

Ken Nagami wrote:
> 
> CoA of BID1 or BID2 needs to remove. MN sends BU with lifetime 0 and 
> BID-option.
> In this case, I think it does not have a problem.
> MN needs to send bulk BU with reused BID and removed BID separately in 
> the current draft.
> 
> BID1, HoA, CoA1  -> CoA4
> BID2, HoA, CoA2  -> remove
> BID3, HoQ, CoA3
> 
==> Yes I know that the current draft supports this option that you send 
BU with lifetime 0 for the BIDs you want to remove. However, my original 
point was that it cannot be done with bulk BU! I mean you cannot say in 
this case that it is a bulk BU if you send atleast two BUs. Ok, you can 
say that its a bulk update BU (multiple CoAs/BIDs updated) and bulk 
remove BU (multiple CoAs/BIDs removed) but it is not bulk BU to update 
all the invalid CoAs and BIDs.

So the difference here is that I'm talking about bulk BU which means 
that what ever kind of handover happens the MN only needs to send one BU 
to do all the updates and removals of BIDs (CoAs). Do you understand 
what I mean?

Thats why I was talking about adding the lifetime field to the new BID 
option! If the MN would add the lifetime to the new BID option, it would 
get bindings for all ats CoAs as described in the RFC 3775 and could 
send just one bulk BU to update/remove all the CoAs. I understand if you 
have made a decision that the MCoA does not have to support bindings 
(binding lifetiemes) as described in the RFC 3775 but can you describe 
why this is? If the lifetime is out of the question you could add flag 
to the BID option which says that remove this BID.

OK! So I am talking about real bulk BU registration/update meaning that 
the MN only sends on BU nad this BU can be answered with one BA. I think 
you still have not clearly thought what this bulk BU means. It does not 
mean anything like what is right now specified in the MCoA draft!!

BR,

Heikki Mahkoenen

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 06:02:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTcAp-00079D-5u; Wed, 12 Apr 2006 06:02:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTcAn-0006zp-ES
	for monami6@ietf.org; Wed, 12 Apr 2006 06:02:05 -0400
Received: from smtp.mei.co.jp ([133.183.129.25] helo=smtp1.mei.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTcAm-0006tg-PH
	for monami6@ietf.org; Wed, 12 Apr 2006 06:02:05 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp1.mei.co.jp (8.12.11.20060308/3.7W/jazz) with ESMTP id
	k3CA21cJ018882
	for <monami6@ietf.org>; Wed, 12 Apr 2006 19:02:01 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx1) with ESMTP id
	k3CA23i21238
	for <monami6@ietf.org>; Wed, 12 Apr 2006 19:02:03 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with ESMTP id
	k3CA24G19398
	for <monami6@ietf.org>; Wed, 12 Apr 2006 19:02:04 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.11.6p2/3.7W/soml22) id k3CA23D18562
	for monami6@ietf.org; Wed, 12 Apr 2006 19:02:03 +0900 (JST)
Received: from [10.68.136.24]
	by soml22.jp.panasonic.com (8.11.6p2/3.7W) with ESMTP id k3CA22A18550
	for <monami6@ietf.org>; Wed, 12 Apr 2006 19:02:02 +0900 (JST)
Date: Wed, 12 Apr 2006 19:02:03 +0900
From: Keigo Aso <asou.keigo@jp.panasonic.com>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] MCoA draft
In-Reply-To: <7c33e94a3484445558456f4277735bc5@it.uc3m.es>
References: <60BE7F1C-66BE-4F47-8B2C-ABE84A665769@enst-bretagne.fr>
	<7c33e94a3484445558456f4277735bc5@it.uc3m.es>
Message-Id: <20060412174812.132B.ASOU.KEIGO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hello,

On Wed, 12 Apr 2006 11:30:42 +0300
marcelo bagnulo braun <marcelo@it.uc3m.es> wrote:

> Hi,
> 
> I must say that i fully agree with Chan-Wah here...
> 
> El 12/04/2006, a las 9:05, Nicolas Montavont escribis:
> 
> > Hi,
> >
> > On Apr 12, 2006, at 7:36 AM, Chan-Wah Ng wrote:
> >
> >> On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
> >>> Folks,
> >>>
> >>> According to the discussion at Vancounver and Dallas, we think that 
> >>> we
> >>> reached a rough consensus to accept
> >>
> >> Really?  Unless you call a ratio of less than 3 (for) : 1 (against) a
> >> "rough consensus" (which was what I counted in Dallas).
> >
> > Most of people were for the adoption of the document as a WG document, 
> > including AD and chair of other WG.
> >
> > The few people who were against failed to show major concerns (some 
> > issues are still unresolved of course, but this can be dealt while the 
> > document is a WG document.
> >
> 
> that is not what i recall from the meeting.
> 
> imho there was not clear rough consensus in the dallas meeting
> 
> 
> however, the decision must be taken on the list i guess
> 
> >>
> >>>
> >>> Multiple Care-of addresses registration
> >>> draft-wakikawa-mobileip-multiplecoa-05
> >>>
> >>> as a WG document for the 3rd deliverable:
> >>>
> >>>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
> >>> Support (RFC 3963) to support the registration of multiple Care-of
> >>> Addresses at a given Home Agent address [Standard Track].
> >>>
> >>> The document has been improved between the 2 IETF meetings in a way 
> >>> that
> >>> we think meets the request of the WG members as expressed at 
> >>> Vancouver.
> >>
> >> Again, as mentioned in ML: I see at least two unresolved issues:
> >>
> >> - Bulk Registrations.
> >> - Simultaneously at home and foreign.
> >
> > Sure, but we didn't say that the document is ready for the IESG.
> >
> 
> but there was a consensus call in the ml sent by Thierry and people 
> brought up those issues as problems in order to accept this  draft as 
> wg item (not in order to sent it to the IESG).
> 
> this, as i understand it, means that there is no consensus to accept 
> this document as a wg item until there is not a clear agreement in 
> these issues
> 
> 
> in particular, i am concerned about the bulk registration issue. imho 
> this is a major issue, because it is not obvious to me that the current 
> draft can be extended to support bulk registration cleanly. I would 
> like to understand if we think that bulk registration is needed, and if 
> it is, how can be fitted into the mcoa draft neatly, without being 
> caught in a draft that doesn't naturally includes such feature. That is 
> why i think more analysis is needed in this point.
I agree with what was mentioned above as one of people who brought up
one of these issues.
As for simultaneously at home and foreign, the support for this issue 
should be a part of mcoa draft because this is indeed beneficial for MN
and HA. So, my thinking is that a discussion and agreement on this are
needed before accepting mcoa draft as WG item.


Regards,
Keigo


> 
> >>
> >>
> >> Having said all that, I am not against moving the draft to WG draft.  
> >> In
> >> fact, changing it to WG draft would force us to maintain an issue 
> >> list,
> >> then we will truly know how many issues there are.
> >
> > That's exactly our point, we believe that it is the best way to work 
> > on the document.
> >
> 
> probably, but the point is that there is no consensus to work on this 
> document yet since there is no consensus to accept it as a wg item 
> (yet)
> 
> regards, marcelo
> 
> 
> > Nicolas
> >
> >> I just wanted to
> >> keep the fact rights.
> >>
> >> /rgds
> >> /cwng
> >>
> >>> The document will therefore be forwarded to the IETF secretariat.
> >>>
> >>> In the meantime, do not hesitate to (continue to) comment on the 
> >>> draft.
> >>>
> >>> Nicolas & Thierry.
> >>>
> >>>
> >>> _______________________________________________
> >>> Monami6 mailing list
> >>> Monami6@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/monami6
> >>>
> >>
> >> _______________________________________________
> >> Monami6 mailing list
> >> Monami6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/monami6
> >
> >
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >
> 
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 06:41:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTcmb-0007ak-Mb; Wed, 12 Apr 2006 06:41:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTcma-0007Xw-A9
	for monami6@ietf.org; Wed, 12 Apr 2006 06:41:08 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTcmX-0000Dj-Bc
	for monami6@ietf.org; Wed, 12 Apr 2006 06:41:08 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7470A4F0028
	for <monami6@ietf.org>; Wed, 12 Apr 2006 12:41:04 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 12:41:03 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 12:41:03 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id AA32E238E;
	Wed, 12 Apr 2006 13:41:03 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 777B995C6A;
	Wed, 12 Apr 2006 13:41:03 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 2495E95C4A;
	Wed, 12 Apr 2006 13:41:03 +0300 (EEST)
Message-ID: <443CD92F.4080806@ericsson.com>
Date: Wed, 12 Apr 2006 13:40:47 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 12 Apr 2006 10:41:03.0416 (UTC)
	FILETIME=[989D8380:01C65E1D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

I started reading the draft and got all the way to page 6. :)

I agree that it is important to save bytes, but IMO not at the cost of 
making the format non-extendable.

At minimum the described format should follow the alignment rules which 
is not true here. If all fields are present, there are more than one 
alignment errors: Flow Label, the SPI field, and the C.S. field which 
doesn't even fall into natural 32-bit word boundaries. I realize that 
one or more fields can be missing in which case the layout is different, 
but still alignment rules should be obeyed in all cases.

-- 
Tero Kauppinen                                 Tel: +358 9 299 3057
Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
Oy L M Ericsson Ab
mailto:tero.kauppinen@ericsson.com

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 07:03:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTd7z-0008Rg-KF; Wed, 12 Apr 2006 07:03:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTd7y-0008R1-2T
	for monami6@ietf.org; Wed, 12 Apr 2006 07:03:14 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTd7w-0000dB-KZ
	for monami6@ietf.org; Wed, 12 Apr 2006 07:03:14 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 329CC212C64
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:03:11 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id F1937212C5F
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:03:10 +0300 (EEST)
Message-ID: <443CDE7B.2090501@nomadiclab.com>
Date: Wed, 12 Apr 2006 14:03:23 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>
In-Reply-To: <443CD92F.4080806@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Hesham,

I have also read this draft and I think that the Binding Update List 
(BUL) and Binding Cache (BC) are not the right place to hold the 
policy/flow binding information. If you use these data structures for 
this information and the MN returns home you loose all the policies as 
the  entries in BUL and BC are removed. Or if it is decided that these 
data structures are best place to hold this information, shouldn't there 
be some way to keep the "policy"/"flow binding" entries there while the 
MN is at home?

In addition there should be machanism to use multiple 
addresses/interfaces for one flow. I think the packet format as it is 
right now does not offer a way to extend support for using multiple 
addresses per flow, right?

Best regards,

Heikki Mahkonen

Tero Kauppinen (JO/LMF) wrote:
> I started reading the draft and got all the way to page 6. :)
> 
> I agree that it is important to save bytes, but IMO not at the cost of 
> making the format non-extendable.
> 
> At minimum the described format should follow the alignment rules which 
> is not true here. If all fields are present, there are more than one 
> alignment errors: Flow Label, the SPI field, and the C.S. field which 
> doesn't even fall into natural 32-bit word boundaries. I realize that 
> one or more fields can be missing in which case the layout is different, 
> but still alignment rules should be obeyed in all cases.
> 


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 07:23:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTdRv-00087T-Do; Wed, 12 Apr 2006 07:23:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTdRu-00087O-Cs
	for monami6@ietf.org; Wed, 12 Apr 2006 07:23:50 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTdRt-0001Il-N5
	for monami6@ietf.org; Wed, 12 Apr 2006 07:23:50 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E98B04F0001
	for <monami6@ietf.org>; Wed, 12 Apr 2006 13:23:48 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 13:23:47 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 13:23:47 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 7C036238E;
	Wed, 12 Apr 2006 14:23:47 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4AE1195C6A;
	Wed, 12 Apr 2006 14:23:47 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E8B7495C4A;
	Wed, 12 Apr 2006 14:23:46 +0300 (EEST)
Message-ID: <443CE332.2030201@ericsson.com>
Date: Wed, 12 Apr 2006 14:23:30 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
In-Reply-To: <443CDE7B.2090501@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 12 Apr 2006 11:23:47.0277 (UTC)
	FILETIME=[90CBA7D0:01C65E23]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Heikki Mahkonen wrote:
> Hi Hesham,
> 
> I have also read this draft and I think that the Binding Update List 
> (BUL) and Binding Cache (BC) are not the right place to hold the 
> policy/flow binding information. If you use these data structures for 
> this information and the MN returns home you loose all the policies as 
> the  entries in BUL and BC are removed. Or if it is decided that these 
> data structures are best place to hold this information, shouldn't there 
> be some way to keep the "policy"/"flow binding" entries there while the 
> MN is at home?

I don't also think that flow bindings should be kept in BC (and BUL), 
because this would lead to the situation that BC contains entries that 
are not actually BC entries but flow binding entries, i.e. when 
processing entries in BC it would be required to differentiate between 
two types of entires as well as perform different actions basing on the 
type. What I'm aim at, IMO it is not wise to put all information to just 
one database because they happen to share something in common (the 
care-of address) but they still on the functional level are used to 
different purposes.

Tero Kauppinen                                 Tel: +358 9 299 3057
Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
Oy L M Ericsson Ab
mailto:tero.kauppinen@ericsson.com

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 08:16:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTeGZ-0005rB-QU; Wed, 12 Apr 2006 08:16:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTeGB-00052X-2j
	for monami6@ietf.org; Wed, 12 Apr 2006 08:15:47 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTe3E-0002Xt-AD
	for monami6@ietf.org; Wed, 12 Apr 2006 08:02:24 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3CC2Nm9026663
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:02:23 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3CC2KT2026659
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:02:20 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3CC2IDR020892
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:02:20 +0200
Message-ID: <443CEB83.7060404@enst-bretagne.fr>
Date: Wed, 12 Apr 2006 13:58:59 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>
In-Reply-To: <443CD92F.4080806@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Tero,

You are right, and we failed (up to now) to find out a format that 
respect the alignment. We are working on that...

Nicolas

Tero Kauppinen (JO/LMF) wrote:

> I started reading the draft and got all the way to page 6. :)
>
> I agree that it is important to save bytes, but IMO not at the cost of 
> making the format non-extendable.
>
> At minimum the described format should follow the alignment rules 
> which is not true here. If all fields are present, there are more than 
> one alignment errors: Flow Label, the SPI field, and the C.S. field 
> which doesn't even fall into natural 32-bit word boundaries. I realize 
> that one or more fields can be missing in which case the layout is 
> different, but still alignment rules should be obeyed in all cases.
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 08:16:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTeGZ-0005qw-Ju; Wed, 12 Apr 2006 08:16:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTeGB-00054H-3b
	for monami6@ietf.org; Wed, 12 Apr 2006 08:15:47 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTe2I-0002Ua-Cj
	for monami6@ietf.org; Wed, 12 Apr 2006 08:01:26 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3CC1PIh026624
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:01:25 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3CC1KPQ026620
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:01:21 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3CC1JIt020887
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 14:01:20 +0200
Message-ID: <443CEB48.3000202@enst-bretagne.fr>
Date: Wed, 12 Apr 2006 13:58:00 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
	<443CE332.2030201@ericsson.com>
In-Reply-To: <443CE332.2030201@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

First of all, thank you for reading the draft.

The BC and BUL are not the place where policies are stored. These 
structures are used to store current bindings between HoA, flows and CoAs.
General policies (that indicate which flow should be mapped to which 
CoA) is out of scope of the draft, and the storage of these policies is 
not defined (up to the implementors).

Nicolas

Tero Kauppinen (JO/LMF) wrote:

> Heikki Mahkonen wrote:
>
>> Hi Hesham,
>>
>> I have also read this draft and I think that the Binding Update List 
>> (BUL) and Binding Cache (BC) are not the right place to hold the 
>> policy/flow binding information. If you use these data structures for 
>> this information and the MN returns home you loose all the policies 
>> as the  entries in BUL and BC are removed. Or if it is decided that 
>> these data structures are best place to hold this information, 
>> shouldn't there be some way to keep the "policy"/"flow binding" 
>> entries there while the MN is at home?
>
>
> I don't also think that flow bindings should be kept in BC (and BUL), 
> because this would lead to the situation that BC contains entries that 
> are not actually BC entries but flow binding entries, i.e. when 
> processing entries in BC it would be required to differentiate between 
> two types of entires as well as perform different actions basing on 
> the type. What I'm aim at, IMO it is not wise to put all information 
> to just one database because they happen to share something in common 
> (the care-of address) but they still on the functional level are used 
> to different purposes.
>
> Tero Kauppinen                                 Tel: +358 9 299 3057
> Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
> Oy L M Ericsson Ab
> mailto:tero.kauppinen@ericsson.com
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 08:44:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTehu-0001Ud-2s; Wed, 12 Apr 2006 08:44:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTehs-0001UY-Bp
	for monami6@ietf.org; Wed, 12 Apr 2006 08:44:24 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTehr-0004PB-1p
	for monami6@ietf.org; Wed, 12 Apr 2006 08:44:24 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 4018A212C63
	for <monami6@ietf.org>; Wed, 12 Apr 2006 15:44:22 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id C8836212C5F
	for <monami6@ietf.org>; Wed, 12 Apr 2006 15:44:21 +0300 (EEST)
Message-ID: <443CF632.5020909@nomadiclab.com>
Date: Wed, 12 Apr 2006 15:44:34 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>
	<443CDE7B.2090501@nomadiclab.com>	<443CE332.2030201@ericsson.com>
	<443CEB48.3000202@enst-bretagne.fr>
In-Reply-To: <443CEB48.3000202@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Nicolas,

Couple of questions.

Does the FID in this draft mean the same thing as BID in the MCoA draft? 
What is the correlation between these two identifiers? Is this an 
optional solution also for the MCoA draft?

Why should the BC and BUL include more information than just the FID 
(sec: 5.2 & 6.1)?

What is the difference in result between action "discard" (2) and 
"remove" (255)?

By the way in the draft the FID field is drawn as a 8 bit field and it 
is said to be 16 bit unsigned field. I quess its just a typo?

BR,

Heikki Mahkonen

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 09:01:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTey5-000146-IH; Wed, 12 Apr 2006 09:01:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTey4-000141-JN
	for monami6@ietf.org; Wed, 12 Apr 2006 09:01:08 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTey4-0004im-68
	for monami6@ietf.org; Wed, 12 Apr 2006 09:01:08 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3CD17et031347
	for <monami6@ietf.org>; Wed, 12 Apr 2006 15:01:07 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3CD16ke031343
	for <monami6@ietf.org>; Wed, 12 Apr 2006 15:01:06 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3CD16hC021030
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 15:01:06 +0200
Message-ID: <443CF94B.6070903@enst-bretagne.fr>
Date: Wed, 12 Apr 2006 14:57:47 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>	<443CDE7B.2090501@nomadiclab.com>	<443CE332.2030201@ericsson.com>	<443CEB48.3000202@enst-bretagne.fr>
	<443CF632.5020909@nomadiclab.com>
In-Reply-To: <443CF632.5020909@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki,

Heikki Mahkonen wrote:

> Hi Nicolas,
>
> Couple of questions.
>
> Does the FID in this draft mean the same thing as BID in the MCoA 
> draft? What is the correlation between these two identifiers? Is this 
> an optional solution also for the MCoA draft?

The FID is mandatory in our draft.
The FID uniquely identifies a flow binding, and really helps when you 
want to cancel an existing flow binding.

We couldn't use the BID, because one BID is linked to one CoA, while in 
our case, we may need several identifiers for a single CoA. Therefore, 
an identifier must be linked to a flow binding, not only to a CoA.

>
> Why should the BC and BUL include more information than just the FID 
> (sec: 5.2 & 6.1)?

Because when a node has to forward a packet (CN or HA) to the MN, it 
should be able to check if the flow maps an existing binding. For 
example, assume a MN that has registered CoA1 for destination port 1000. 
When the CN has to send a packet of this flow (port number = 1000), it 
needs to look into its BC to select the appropriate CoA.

Does it make sense to you?

>
> What is the difference in result between action "discard" (2) and 
> "remove" (255)?

This is not very well explained yet in the document, I agree with you :(
Let start with the easiest: "remove" means that the MN requests the node 
to delete an existing flow binding.

The idea of the "discard" action was to allow a MN to request its HA not 
to forward a specific flow. Assume a MN that goes from 802.11 to a GPRS 
connection. The MN may request its HA to stop forwarding video packets 
while it uses the GPRS interface.

>
> By the way in the draft the FID field is drawn as a 8 bit field and it 
> is said to be 16 bit unsigned field. I quess its just a typo?

Yes it is, thanks.

Nicolas

>
> BR,
>
> Heikki Mahkonen
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 11:11:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTh0X-0002Iu-J0; Wed, 12 Apr 2006 11:11:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTh0W-0002Ip-TB
	for monami6@ietf.org; Wed, 12 Apr 2006 11:11:48 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTh0W-00016C-DO
	for monami6@ietf.org; Wed, 12 Apr 2006 11:11:48 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3CFBkts015035
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:11:47 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k3CFBjH7012893
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:11:46 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 08:11:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Wed, 12 Apr 2006 08:07:15 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF029FA08@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZeHaKy74gTUOkoT0a3UPFMaRo2XQAJSYK2
References: <443CD92F.4080806@ericsson.com>
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>, "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 12 Apr 2006 15:11:45.0465 (UTC)
	FILETIME=[69A18290:01C65E43]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0277029318=="
Errors-To: monami6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0277029318==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C65E43.69970AD2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C65E43.69970AD2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I started reading the draft and got all the way to page 6. :)

=3D> Good start :)

I agree that it is important to save bytes, but IMO not at the cost of=20
making the format non-extendable.

=3D> I'm not sure about that. The format can be extensible in several
ways:=20
  - We can define sub-options
  - We can add a version field that allows for new versions of the=20
    same option.=20
Can you elaborate on how you would like it to be extensible and how the=20
current format stops you from doing that?

  At minimum the described format should follow the alignment rules =
which=20
  is not true here. If all fields are present, there are more than one=20
  alignment errors: Flow Label, the SPI field, and the C.S. field which=20
  doesn't even fall into natural 32-bit word boundaries.=20

=3D> What is the alignment rule? :) This option is defined so that it =
does=20
*not* have static alignment. I know this is different from the way we =
define
options in IPv6, but I'd like to hear why this is really bad and whether =

having a fixed option is a lot better given the huge waste we will have
(more than 100% overhead in many cases).

Hesham


I realize that=20
  one or more fields can be missing in which case the layout is =
different,=20
  but still alignment rules should be obeyed in all cases.

--=20
Tero Kauppinen                                 Tel: +358 9 299 3057
Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
Oy L M Ericsson Ab
mailto:tero.kauppinen@ericsson.com

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7233.29">
<TITLE>RE: [Monami6] Packet format: =
draft-soliman-monami6-flow-binding-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>I started reading the draft and got all the way to =
page 6. :)<BR>
<BR>
=3D&gt; Good start :)<BR>
<BR>
I agree that it is important to save bytes, but IMO not at the cost =
of<BR>
making the format non-extendable.<BR>
<BR>
=3D&gt; I'm not sure about that. The format can be extensible in =
several<BR>
ways:<BR>
&nbsp; - We can define sub-options<BR>
&nbsp; - We can add a version field that allows for new versions of =
the<BR>
&nbsp;&nbsp;&nbsp; same option.<BR>
Can you elaborate on how you would like it to be extensible and how =
the<BR>
current format stops you from doing that?<BR>
<BR>
&nbsp; At minimum the described format should follow the alignment rules =
which<BR>
&nbsp; is not true here. If all fields are present, there are more than =
one<BR>
&nbsp; alignment errors: Flow Label, the SPI field, and the C.S. field =
which<BR>
&nbsp; doesn't even fall into natural 32-bit word boundaries.<BR>
<BR>
=3D&gt; What is the alignment rule? :) This option is defined so that it =
does<BR>
*not* have static alignment. I know this is different from the way we =
define<BR>
options in IPv6, but I'd like to hear why this is really bad and =
whether<BR>
having a fixed option is a lot better given the huge waste we will =
have<BR>
(more than 100% overhead in many cases).<BR>
<BR>
Hesham<BR>
<BR>
<BR>
I realize that<BR>
&nbsp; one or more fields can be missing in which case the layout is =
different,<BR>
&nbsp; but still alignment rules should be obeyed in all cases.<BR>
<BR>
--<BR>
Tero =
Kauppinen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tel: +358 9 299 =
3057<BR>
Research Scientist, NomadicLab, IP Networks,&nbsp;&nbsp; Fax: +358 9 299 =
5055<BR>
Ericsson Research, Corporate =
Unit.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile: +358 40 590 7560<BR>
Oy L M Ericsson Ab<BR>
<A =
HREF=3D"mailto:tero.kauppinen@ericsson.com">mailto:tero.kauppinen@ericsso=
n.com</A><BR>
<BR>
_______________________________________________<BR>
Monami6 mailing list<BR>
Monami6@ietf.org<BR>
<A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/monami6">https://www1.ietf=
.org/mailman/listinfo/monami6</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C65E43.69970AD2--


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

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6

--===============0277029318==--




From monami6-bounces@ietf.org Wed Apr 12 11:18:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTh6i-0004Kn-DN; Wed, 12 Apr 2006 11:18:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTh6g-0004Ki-LO
	for monami6@ietf.org; Wed, 12 Apr 2006 11:18:10 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTh6f-0001dB-Q4
	for monami6@ietf.org; Wed, 12 Apr 2006 11:18:10 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3CFI8rt015688
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:18:09 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3CFI8HD025109
	for <monami6@ietf.org>; Wed, 12 Apr 2006 08:18:08 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 08:18:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Wed, 12 Apr 2006 08:18:06 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZeIMDXBDYb/L6RQ5qN/ULASxcc/AAIrdMw
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>, "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 12 Apr 2006 15:18:07.0302 (UTC)
	FILETIME=[4D393660:01C65E44]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0082291893=="
Errors-To: monami6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0082291893==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C65E44.4D073E54"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C65E44.4D073E54
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable




  I have also read this draft and I think that the Binding Update List=20
  (BUL) and Binding Cache (BC) are not the right place to hold the=20
  policy/flow binding information. If you use these data structures for=20
  this information and the MN returns home you loose all the policies as =

  the  entries in BUL and BC are removed.

=3D> This draft describes flow binding for the cases where the mobile =
node
has either:=20
  1. more than one CoA
  2. a HoA and a CoA (i.e. the MN is at home and a foreign network at =
the same
     time).=20
If the MN is only at home then of course the BC entries are removed and =
the use
of MIP is not appropriate to split flows. I don't understand your =
concern here
about deleting policies. If you want to route flows differently while =
you're=20
at home (i.e. between 2 different HoAs) then MIP is not a good tool for =
doing that.
But I don't see much benefit in that scenario.=20

  Or if it is decided that these=20
  data structures are best place to hold this information, shouldn't =
there=20
  be some way to keep the "policy"/"flow binding" entries there while =
the=20
  MN is at home?

=3D> What for? Could please show a scenario?

  In addition there should be machanism to use multiple=20
  addresses/interfaces for one flow. I think the packet format as it is=20
  right now does not offer a way to extend support for using multiple=20
  addresses per flow, right?

=3D> That's right. Splitting the same flow to two different interfaces=20
is not a good thing to do because:
  - It can cause packets to arrive out of order
  - It can break security if the packets are protected.=20
So I don't think this is something we want to do.=20

Hesham

Best regards,

Heikki Mahkonen

Tero Kauppinen (JO/LMF) wrote:
> I started reading the draft and got all the way to page 6. :)
>=20
> I agree that it is important to save bytes, but IMO not at the cost of =

> making the format non-extendable.
>=20
> At minimum the described format should follow the alignment rules =
which=20
> is not true here. If all fields are present, there are more than one=20
> alignment errors: Flow Label, the SPI field, and the C.S. field which=20
> doesn't even fall into natural 32-bit word boundaries. I realize that=20
> one or more fields can be missing in which case the layout is =
different,=20
> but still alignment rules should be obeyed in all cases.
>=20


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7233.29">
<TITLE>RE: [Monami6] Packet format: =
draft-soliman-monami6-flow-binding-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp; I have also read this draft and I think that =
the Binding Update List<BR>
&nbsp; (BUL) and Binding Cache (BC) are not the right place to hold =
the<BR>
&nbsp; policy/flow binding information. If you use these data structures =
for<BR>
&nbsp; this information and the MN returns home you loose all the =
policies as<BR>
&nbsp; the&nbsp; entries in BUL and BC are removed.<BR>
<BR>
=3D&gt; This draft describes flow binding for the cases where the mobile =
node<BR>
has either:<BR>
&nbsp; 1. more than one CoA<BR>
&nbsp; 2. a HoA and a CoA (i.e. the MN is at home and a foreign network =
at the same<BR>
&nbsp;&nbsp;&nbsp;&nbsp; time).<BR>
If the MN is only at home then of course the BC entries are removed and =
the use<BR>
of MIP is not appropriate to split flows. I don't understand your =
concern here<BR>
about deleting policies. If you want to route flows differently while =
you're<BR>
at home (i.e. between 2 different HoAs) then MIP is not a good tool for =
doing that.<BR>
But I don't see much benefit in that scenario.<BR>
<BR>
&nbsp; Or if it is decided that these<BR>
&nbsp; data structures are best place to hold this information, =
shouldn't there<BR>
&nbsp; be some way to keep the &quot;policy&quot;/&quot;flow =
binding&quot; entries there while the<BR>
&nbsp; MN is at home?<BR>
<BR>
=3D&gt; What for? Could please show a scenario?<BR>
<BR>
&nbsp; In addition there should be machanism to use multiple<BR>
&nbsp; addresses/interfaces for one flow. I think the packet format as =
it is<BR>
&nbsp; right now does not offer a way to extend support for using =
multiple<BR>
&nbsp; addresses per flow, right?<BR>
<BR>
=3D&gt; That's right. Splitting the same flow to two different =
interfaces<BR>
is not a good thing to do because:<BR>
&nbsp; - It can cause packets to arrive out of order<BR>
&nbsp; - It can break security if the packets are protected.<BR>
So I don't think this is something we want to do.<BR>
<BR>
Hesham<BR>
<BR>
Best regards,<BR>
<BR>
Heikki Mahkonen<BR>
<BR>
Tero Kauppinen (JO/LMF) wrote:<BR>
&gt; I started reading the draft and got all the way to page 6. :)<BR>
&gt;<BR>
&gt; I agree that it is important to save bytes, but IMO not at the cost =
of<BR>
&gt; making the format non-extendable.<BR>
&gt;<BR>
&gt; At minimum the described format should follow the alignment rules =
which<BR>
&gt; is not true here. If all fields are present, there are more than =
one<BR>
&gt; alignment errors: Flow Label, the SPI field, and the C.S. field =
which<BR>
&gt; doesn't even fall into natural 32-bit word boundaries. I realize =
that<BR>
&gt; one or more fields can be missing in which case the layout is =
different,<BR>
&gt; but still alignment rules should be obeyed in all cases.<BR>
&gt;<BR>
<BR>
<BR>
_______________________________________________<BR>
Monami6 mailing list<BR>
Monami6@ietf.org<BR>
<A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/monami6">https://www1.ietf=
.org/mailman/listinfo/monami6</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C65E44.4D073E54--


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

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6

--===============0082291893==--




From monami6-bounces@ietf.org Wed Apr 12 23:12:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTsGM-0007Y3-RB; Wed, 12 Apr 2006 23:12:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTsGL-0007Xv-7e
	for monami6@ietf.org; Wed, 12 Apr 2006 23:12:53 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTsGJ-0002sV-ME
	for monami6@ietf.org; Wed, 12 Apr 2006 23:12:53 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D3ClUl025810; Thu, 13 Apr 2006 12:12:49 +0900
Date: Thu, 13 Apr 2006 12:12:39 +0900
Message-ID: <m2acaqkw2g.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Keigo Aso <asou.keigo@jp.panasonic.com>
In-Reply-To: <20060330103647.9CF7.ASOU.KEIGO@jp.panasonic.com>
References: <20060330103647.9CF7.ASOU.KEIGO@jp.panasonic.com>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Monami6 WG <monami6@ietf.org>
Subject: [Monami6] Re: Returning Home in MCoA draft
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi Keigo

Sorry for my long silence.

If MN creates a CoA at home and HA keeps intercepting packets, it does not mean that MN returns home.
IMO, your explanation here sounds like MN just returns to a subnet where HA operates. 
So, no protocol modification is necessary. what do you think?

ryuji


At Thu, 30 Mar 2006 11:28:50 +0900,
Keigo Aso wrote:
> 
> Hi Ryuji and all,
> 
> Thank you for your comments at Dallas.
> I would like to start subsequent discussion about returning home issue
> on ML. What we wanted to mention in our presentation is the need of
> creating CoA in home network. This enables HA to switch forwarding
> destination even if MN is connected to home.
> 
> According to current MCoA draft, there are two options which MN could
> select. The first situation is "a mobile node wants to return home",
> which basically means "a mobile node wants to use the home attached
> interface". The second situation is "a mobile node does not want to
> return home", which basically means "a mobile node wants to use 
> the foreign attached interface". 
> About these options, I think MCoA draft should include another option 
> as the third situation, which is "a mobile node wants to use both
> interfaces".
> This option is useful for enabling HA to do flow control.
> Moreover, MCoA draft said that "The decision whether a mobile node
> returns home or not is up to implementors.". 
> This could be applied to also the third situation.
> What do you think on this ?
> 
> Regards,
> Keigo
> 

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 23:36:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTsdN-0003dN-Ll; Wed, 12 Apr 2006 23:36:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTsdL-0003dF-Ms
	for monami6@ietf.org; Wed, 12 Apr 2006 23:36:39 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTsdL-0003fx-0k
	for monami6@ietf.org; Wed, 12 Apr 2006 23:36:39 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D3aaUl028261; Thu, 13 Apr 2006 12:36:37 +0900
Date: Thu, 13 Apr 2006 12:36:31 +0900
Message-ID: <m28xqakuyo.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <910da3595853477a839bb5fbd7e79538@it.uc3m.es>
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
	<443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Marcelo

At Tue, 11 Apr 2006 14:07:28 +0300,
marcelo bagnulo braun wrote:
>=20
> Hi all,
>=20
>=20
> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
>=20
> >
> >> One idea is that we can separate bulk registration into separate=20
> >> document.
> >> I can remove the texts and move to the new document which will=20
> >> contain your inputs, too.
> >> However, before doing that, the draft must be WG document.
> >> This draft is still individual draft and not WG one.
> >> I want to solicit the comments from WG chairs  first !!!
> >> ryuji
> >
> > Hello,
> >
> > I think that the best way forward would be to split the current draft=20
> > into two drafts. This first would be the current draft without the=20
> > bulk option and the second a bulk extension to the first draft.=20
> > Although it makes a lot of sense to support a bulk registration,=20
> > because it saves a lot of bytes and more importantly signaling bytes,=20
> > but it is still in essence just an optimization to the basic idea of=20
> > inserting the BID option.
> >
> > The current way of including the bulk possibility produces a lot of=20
> > questions that the MCoA draft fails to answer clear enough. Moreover,=20
> > the current draft's bulk registration works only with HAs and not with =

> > CNs, which is a situation that should be avoided. In my opinion the=20
> > mechanism should work coherently among the target nodes. Being a=20
> > separate draft, bulk registration issues would be easier to work on=20
> > without needlessly stalling the MCoA draft.
> >
>=20
>=20
> i am sorry but i fail to see the logic behind this line of reasoning.
>=20
> I mean, whether we think that bulk registration is important or we don't
>=20
> if we don't think it is important, we just drop it
>=20
> if we think it is important, i guess we need to do it from day one. I=20
> mean, i don't see the point in doing one spec that is incomplete and=20
> lacks and important feature and 6 months later do a new spec with the=20
> additional feature. I think that we need to do it once and do it right=20
> with all the important features. I mean, i guess we don't want to have=20
> to write first implementations with mcoa support version one (without=20
> bulk registration) and then another implementation of mcoa version 2=20
> (with bulk registration) and make the version 2 with bulk registration=20
> compatible with the mcoa version 1 (without bulk implementation)

diagree. MIP6/NEMO base specs are also updated. If we try to support
complete feature of MIP6/NEMO, we can not start anything. (because
base feature is not completed!)

BTW, we've implemented MCoA in several times and I knew several groups did =
also.
Our implementation also confirms interoperability with different implemenat=
tion, too.

> This is even more critical in the case that you point out that the=20
> current mcoa draft doens't seems to cleanly support the bulk=20
> registration and the additional stuff will be needed for bulk=20
> registration with CN. Do we know that the future bulk extensions can be=20
> created starting from the current mcoa draft that lacks of bulk=20
> registration? or we may end up with two different mechanisms one=20
> without bullk and another for bulk registration?

The current situation is that MCoA does support bulk registration for HA, b=
ut not for CN.
Some proposal are introduced in ML, but most are based on RR.=20
Then, how many operators will use RR? There is another way to do RO which i=
s CN IPsec.
So, bulk registration for CN needs more discussion whether it's really need=
.=20
If yes, which RO mechanism we should support?=20


> I think we need to make just one mechanism that provides all the=20
> features that are needed and do it right in the first time

diagree, again. see above.

> In addition, we are only chartered to do one MCOA docuemnts, not a=20
> basic support and then MCOAs support optimizations, so i guess that we=20
> would need to recharter in order to this MCOA optimization support=20
> draft, right?

if we separate document,  yes.

> So, my suggestion is to first figure out if bulk registration is needed=20
> or not.
> If it is needed, produce a single spec (and a single implementation)=20
> that supports all the desired features.

I would like to support bulk registration to HA, but not to CN at this poin=
t.
RO mechanism is not completed yet, except for RR. If we exclude bulk regist=
ation to CN,=20
we can produce signle document

regards
ryuji

> regards, marcelo
>=20
>=20
>=20
> > --=20
> > Tero Kauppinen                                 Tel: +358 9 299 3057
> > Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> > Ericsson Research, Corporate Unit.             Mobile: +358 40 590 7560
> > Oy L M Ericsson Ab
> > mailto:tero.kauppinen@ericsson.com
> >
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 23:43:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTsjm-0006OX-7g; Wed, 12 Apr 2006 23:43:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTsjl-0006OP-8e
	for monami6@ietf.org; Wed, 12 Apr 2006 23:43:17 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTsjk-0003m2-Ho
	for monami6@ietf.org; Wed, 12 Apr 2006 23:43:17 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D3hEUl028943; Thu, 13 Apr 2006 12:43:14 +0900
Date: Thu, 13 Apr 2006 12:43:08 +0900
Message-ID: <m27j5ukunn.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: =?ISO-8859-1?Q?G=E1bor?= Fekete <feketgai@index.hu>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <200604111520.58537.feketgai@index.hu>
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi G=E1bor

At Tue, 11 Apr 2006 15:20:57 +0300,
G=E1bor Fekete wrote:
>=20
> Hi Marcelo and list,
>=20
> On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
> > Hi all,
> >=20
> >=20
> > El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
> >=20
> > >
> > >> One idea is that we can separate bulk registration into separate=20
> > >> document.
> > >> I can remove the texts and move to the new document which will=20
> > >> contain your inputs, too.
> > >> However, before doing that, the draft must be WG document.
> > >> This draft is still individual draft and not WG one.
> > >> I want to solicit the comments from WG chairs  first !!!
> > >> ryuji
> > >
> > > Hello,
> > >
> > > I think that the best way forward would be to split the current draft=
=20
> > > into two drafts. This first would be the current draft without the=20
> > > bulk option and the second a bulk extension to the first draft.=20
> > > Although it makes a lot of sense to support a bulk registration,=20
> > > because it saves a lot of bytes and more importantly signaling bytes,=
=20
> > > but it is still in essence just an optimization to the basic idea of =

> > > inserting the BID option.
> > >
> > > The current way of including the bulk possibility produces a lot of=20
> > > questions that the MCoA draft fails to answer clear enough. Moreover,=
=20
> > > the current draft's bulk registration works only with HAs and not wit=
h=20
> > > CNs, which is a situation that should be avoided. In my opinion the=20
> > > mechanism should work coherently among the target nodes. Being a=20
> > > separate draft, bulk registration issues would be easier to work on=20
> > > without needlessly stalling the MCoA draft.
> > >
> >=20
> >=20
> > i am sorry but i fail to see the logic behind this line of reasoning.
> >=20
> > I mean, whether we think that bulk registration is important or we don't
> >=20
> > if we don't think it is important, we just drop it
> >=20
> > if we think it is important, i guess we need to do it from day one. I=20
> > mean, i don't see the point in doing one spec that is incomplete and=20
> > lacks and important feature and 6 months later do a new spec with the=20
> > additional feature. I think that we need to do it once and do it right =

>=20
> I don't think Tero meant creating a "new spec". I guess it'd be more
> like an addition. At least I hope.
>=20
> I don't think it is a problem to have two separate drafts (they are
> only drafts anyway). In that case, the basic MCoA draft should drop all
> the "bulk registration" related text.
>=20
> But I would suggest someone taking the MCoA draft and rewrite it with
> bulk in mind from scratch and just see how it shapes up. I don't think
> it would hurt. E.g. Martti Kuparinen had quite nice ideas...
>=20
> > with all the important features. I mean, i guess we don't want to have =

> > to write first implementations with mcoa support version one (without=20
> > bulk registration) and then another implementation of mcoa version 2=20
> > (with bulk registration) and make the version 2 with bulk registration =

> > compatible with the mcoa version 1 (without bulk implementation)
>=20
> If bulk-reg is an add-on draft then I think it is no problem.
> By add-on I mean that mcoa can be easily extended to support bulk-reg.
> In this case I see one complication in the error handling, e.g.
> "What if a bulk-mcoa MN talks to a non-bulk-mcoa implementer CN?"
>=20
> >=20
> > This is even more critical in the case that you point out that the=20
> > current mcoa draft doens't seems to cleanly support the bulk=20
> > registration and the additional stuff will be needed for bulk=20
> > registration with CN. Do we know that the future bulk extensions can be=
=20
> > created starting from the current mcoa draft that lacks of bulk=20
> > registration? or we may end up with two different mechanisms one=20
> > without bullk and another for bulk registration?
> >=20
> > I think we need to make just one mechanism that provides all the=20
> > features that are needed and do it right in the first time
> >=20
> > In addition, we are only chartered to do one MCOA docuemnts, not a=20
> > basic support and then MCOAs support optimizations, so i guess that we =

> > would need to recharter in order to this MCOA optimization support=20
> > draft, right?
> >=20
> > So, my suggestion is to first figure out if bulk registration is needed=
=20
> > or not.
>=20
> IMO, bulk-reg reduces signaling overhead. The problem is currently
> there are no services (at least I am not aware) deployed using mipv6
> and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot up
> and if you have multiple CoAs on a single interface. But in the latter ca=
se
> will it be common in the future to have ipv6 subnets with multiple network
> prefixes? So for me it's a bit like planning blind and whether we need it
> or not may not be that clear at this point. Or am I saying bull?

I mostly agree.=20

For home registartion, MN must update all CoAs to keep the lifetime
update.  Therefore, bulk registration may be useful.  MN can update
all binding lifetimes periodically at the same time, regardless of
lifetime expiration timing.

However, MN does not need to send all CoAs to CN. It just sends CoA
which needs to use for communication with the CN. And binding
registration to CN is continued only while MN is communicating.  So, I
am not so positive to support bulk registartion to CN, which requires
additional protocol modification to RR. And I also want to see how many
operators want to use RR, too.

regards
ryuji


> I say, just create a draft for bulk (either rewrite mcoa or create a=20
> separate draft and drop bulk-reg from mcoa) and
> see if the result is over-complicated or simple and clean.
>=20
> > If it is needed, produce a single spec (and a single implementation)=20
> > that supports all the desired features.
> >=20
> > regards, marcelo
> >=20
> >=20
> >=20
> > > --=20
> > > Tero Kauppinen                                 Tel: +358 9 299 3057
> > > Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> > > Ericsson Research, Corporate Unit.             Mobile: +358 40 590 75=
60
> > > Oy L M Ericsson Ab
> > > mailto:tero.kauppinen@ericsson.com
> > >
> > > _______________________________________________
> > > Monami6 mailing list
> > > Monami6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/monami6
> > >
> >=20
> >=20
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 12 23:48:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTspA-0008Ag-QX; Wed, 12 Apr 2006 23:48:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTsp9-0008Aa-GU
	for monami6@ietf.org; Wed, 12 Apr 2006 23:48:51 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTsp8-0003pY-UD
	for monami6@ietf.org; Wed, 12 Apr 2006 23:48:51 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D3mhUl029514; Thu, 13 Apr 2006 12:48:44 +0900
Date: Thu, 13 Apr 2006 12:48:38 +0900
Message-ID: <m264lekueh.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <443BA3DE.1070404@ericsson.com>
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
	<443BA3DE.1070404@ericsson.com>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi Tero

At Tue, 11 Apr 2006 15:41:02 +0300,
Tero Kauppinen (JO/LMF) wrote:
>=20
> G=E1bor Fekete wrote:
> > Hi Marcelo and list,
> >=20
> > On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
> >> Hi all,
> >>
> >>
> >> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
> >>
> >>...
> >>
> >> i am sorry but i fail to see the logic behind this line of reasoning.
> >>
> >> I mean, whether we think that bulk registration is important or we don=
't
> >>
> >> if we don't think it is important, we just drop it
> >>
> >> if we think it is important, i guess we need to do it from day one. I =

> >> mean, i don't see the point in doing one spec that is incomplete and=20
>=20
> IMO, it is an optimization because the protocol works without it. I=20
> would not say that the spec would be "incomplete and lack an important=20
> feature", but that is just my opinion.
>=20
> >> lacks and important feature and 6 months later do a new spec with the =

> >> additional feature. I think that we need to do it once and do it right=
=20
> >=20
> > I don't think Tero meant creating a "new spec". I guess it'd be more
> > like an addition. At least I hope.
> >=20
>=20
> You got my point.
>=20
> >=20
> > IMO, bulk-reg reduces signaling overhead. The problem is currently
> > there are no services (at least I am not aware) deployed using mipv6
> > and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot =
up
> > and if you have multiple CoAs on a single interface. But in the latter =
case
> > will it be common in the future to have ipv6 subnets with multiple netw=
ork
> > prefixes? So for me it's a bit like planning blind and whether we need =
it
> > or not may not be that clear at this point. Or am I saying bull?
>=20
> I don't think you're "saying bull". It is a good question that I have=20
> also tried to find an answer for ... not succeeding that much, though. I =

> would say that reducing signaling overhead is a pretty strong argument=20
> that justifies the existence of bulk-reg.

I agree that reducing signaling is quite important.
But, RR brings certain signaling overhead.=20
Reducing the number of BUs doesn't mean much if we assume RR.

ryuji




> Regz,
> Tero
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 00:06:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTt6W-00027a-GE; Thu, 13 Apr 2006 00:06:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTt6V-00027V-6b
	for monami6@ietf.org; Thu, 13 Apr 2006 00:06:47 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTt6U-0004Cb-8X
	for monami6@ietf.org; Thu, 13 Apr 2006 00:06:47 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D46hUl031404; Thu, 13 Apr 2006 13:06:44 +0900
Date: Thu, 13 Apr 2006 13:06:38 +0900
Message-ID: <m24q0yktkh.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <6780888f55d5ce9cbde5632b3473a5ce@it.uc3m.es>
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
	<6780888f55d5ce9cbde5632b3473a5ce@it.uc3m.es>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi Marcelo

At Tue, 11 Apr 2006 16:06:59 +0300,
marcelo bagnulo braun wrote:
>=20
> Hi,
>=20
> El 11/04/2006, a las 15:20, G=E1bor Fekete escribi=F3:
>=20
> > Hi Marcelo and list,
> >
> > On Tuesday 11 April 2006 14:07, marcelo bagnulo braun wrote:
> >> Hi all,
> >>
> >>
> >> El 11/04/2006, a las 12:17, Tero Kauppinen (JO/LMF) escribi=F3:
> >>
> >>>
> >>>> One idea is that we can separate bulk registration into separate
> >>>> document.
> >>>> I can remove the texts and move to the new document which will
> >>>> contain your inputs, too.
> >>>> However, before doing that, the draft must be WG document.
> >>>> This draft is still individual draft and not WG one.
> >>>> I want to solicit the comments from WG chairs  first !!!
> >>>> ryuji
> >>>
> >>> Hello,
> >>>
> >>> I think that the best way forward would be to split the current draft
> >>> into two drafts. This first would be the current draft without the
> >>> bulk option and the second a bulk extension to the first draft.
> >>> Although it makes a lot of sense to support a bulk registration,
> >>> because it saves a lot of bytes and more importantly signaling bytes,
> >>> but it is still in essence just an optimization to the basic idea of
> >>> inserting the BID option.
> >>>
> >>> The current way of including the bulk possibility produces a lot of
> >>> questions that the MCoA draft fails to answer clear enough. Moreover,
> >>> the current draft's bulk registration works only with HAs and not=20
> >>> with
> >>> CNs, which is a situation that should be avoided. In my opinion the
> >>> mechanism should work coherently among the target nodes. Being a
> >>> separate draft, bulk registration issues would be easier to work on
> >>> without needlessly stalling the MCoA draft.
> >>>
> >>
> >>
> >> i am sorry but i fail to see the logic behind this line of reasoning.
> >>
> >> I mean, whether we think that bulk registration is important or we=20
> >> don't
> >>
> >> if we don't think it is important, we just drop it
> >>
> >> if we think it is important, i guess we need to do it from day one. I
> >> mean, i don't see the point in doing one spec that is incomplete and
> >> lacks and important feature and 6 months later do a new spec with the
> >> additional feature. I think that we need to do it once and do it right
> >
> > I don't think Tero meant creating a "new spec". I guess it'd be more
> > like an addition. At least I hope.
> >
>=20
> but we don't know if the addition would fit in the existent MCOA draft,=20
> don't we? I mean, there seems to be several issues with adding bulk=20
> registration support to the mcoa draft right?=20

Can you list up the several issues of MCoA?? I only catch the issue of
CoA authentication for bulk registartion to CN.

> if this is so, it is not=20
> clear to me at this point that it would be straightforward to extend=20
> the current mcoa draft to support bulk registration and solve all the=20
> issues.
>=20
> Moreover, i don't think it is a good strategy. I mean, if we know now=20
> that bulk registration is an important feature, then why to first adopt=20
> a mcoa draft that has not bulk registration and later figure out if we=20
> can fit in this draft the bulk registration stuff.... it doesn't make=20
> sense to me... If we are designing the mcoa support now and we consider=20
> that bulk registration is needed, we better design the mcoa support=20
> with this in mind and make sure that the basic mcoa support provides=20
> the features that we need.... I mean i understand making hacks in=20
> implementaions and specs when unforseen requirements appear, but this=20
> is already here and we haven't defined the solution yet, so i don't=20
> think that the best approach would be to ignore future features and see=20
> how they fit in later...

I don't understand your statement here. There are several ideas to solve th=
e issue on ML.
The discusson here is whether we merge the idea into the base spec, or spli=
t into two documents.

> > I don't think it is a problem to have two separate drafts (they are
> > only drafts anyway). In that case, the basic MCoA draft should drop all
> > the "bulk registration" related text.
> >
>=20
> but what is the point in having two draft?

Since most of MCoA spec is mature, we can continue to discuss RO case in pr=
allel.

> my point is that we need to figure out how this bulk registration stuff=20
> fits in the mcoa support anyway in order to do it right so, i guess we=20
> can do it once and for all
>=20
> > But I would suggest someone taking the MCoA draft and rewrite it with
> > bulk in mind from scratch and just see how it shapes up. I don't think
> > it would hurt. E.g. Martti Kuparinen had quite nice ideas...
> >
>=20
> yes, this is the approach that i would suggest, try to figure out how a=20
> mechanism to support mcoa registration and bulk registration would look=20
> like
>=20
> >> with all the important features. I mean, i guess we don't want to have
> >> to write first implementations with mcoa support version one (without
> >> bulk registration) and then another implementation of mcoa version 2
> >> (with bulk registration) and make the version 2 with bulk registration
> >> compatible with the mcoa version 1 (without bulk implementation)
> >
> > If bulk-reg is an add-on draft then I think it is no problem.
> > By add-on I mean that mcoa can be easily extended to support bulk-reg.
>=20
> but we don't know that at this point, since we haven't figured out how=20
> to address the issues that were brought up about bulk registration in=20
> the current mcoa draft right?

Why? We have had discussions on ML? Why we need to re-start the discussion =
again??

> so maybe we accept this mcoa draft as the first solution and then we=20
> need to do nasty hacks to include the bulk registration stuff... this=20
> doesn't seems to me a good strategy for protocol design. we need to=20
> figure out the big picture and define a solutions that are extensible=20
> to deal with all the features that we consider important

So, your problem is that proposed idea to support bulk registartion to
CN is nasty extension??

> so, if we know now that we want this, then we should do it since the=20
> begining...
>=20
> > In this case I see one complication in the error handling, e.g.
> > "What if a bulk-mcoa MN talks to a non-bulk-mcoa implementer CN?"
> >
>=20
> this is just one of the issues that may appear....
> i mean since day one we will have multiple vrsions of the mcoa=20
> registration support.... i don't think this is the best approach

This shouldn't happend.

>=20
> >>
> >> This is even more critical in the case that you point out that the
> >> current mcoa draft doens't seems to cleanly support the bulk
> >> registration and the additional stuff will be needed for bulk
> >> registration with CN. Do we know that the future bulk extensions can=20
> >> be
> >> created starting from the current mcoa draft that lacks of bulk
> >> registration? or we may end up with two different mechanisms one
> >> without bullk and another for bulk registration?
> >>
> >> I think we need to make just one mechanism that provides all the
> >> features that are needed and do it right in the first time
> >>
> >> In addition, we are only chartered to do one MCOA docuemnts, not a
> >> basic support and then MCOAs support optimizations, so i guess that we
> >> would need to recharter in order to this MCOA optimization support
> >> draft, right?
> >>
> >> So, my suggestion is to first figure out if bulk registration is=20
> >> needed
> >> or not.
> >
> > IMO, bulk-reg reduces signaling overhead. The problem is currently
> > there are no services (at least I am not aware) deployed using mipv6
> > and not many ipv6 sites. At first glance Bulk-reg is good on e.g. boot =

> > up
> > and if you have multiple CoAs on a single interface.
>=20
> Do you think that bulk registration will only be usefull for multiple=20
> coas in a single interface? why is that?

Not limited to, but the timing of movement is different.

> >  But in the latter case
> > will it be common in the future to have ipv6 subnets with multiple=20
> > network
> > prefixes?
>=20
> well, multihomed networks are expected to have multiple prefixes (at=20
> least in several cases) so i guess this may be pretty common (just=20
> guessing of course)

I'm not sure:-p

ryuji

> >  So for me it's a bit like planning blind and whether we need it
> > or not may not be that clear at this point. Or am I saying bull?
> >
>=20
> > I say, just create a draft for bulk (either rewrite mcoa or create a
> > separate draft and drop bulk-reg from mcoa) and
> > see if the result is over-complicated or simple and clean.
> >
>=20
> fully agree, but this is needed before taking on the work in the=20
> current mcoa draft in the wg, so that we can figure out if a mcoa=20
> mechanism that supports bulk registration is compatible or not with the=20
> current mcoa draft... agree?
>=20
> regards, marcelo
>=20
>=20
>=20
> >> If it is needed, produce a single spec (and a single implementation)
> >> that supports all the desired features.
> >>
> >> regards, marcelo
> >>
> >>
> >>
> >>> --=20
> >>> Tero Kauppinen                                 Tel: +358 9 299 3057
> >>> Research Scientist, NomadicLab, IP Networks,   Fax: +358 9 299 5055
> >>> Ericsson Research, Corporate Unit.             Mobile: +358 40 590=20
> >>> 7560
> >>> Oy L M Ericsson Ab
> >>> mailto:tero.kauppinen@ericsson.com
> >>>
> >>> _______________________________________________
> >>> Monami6 mailing list
> >>> Monami6@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/monami6
> >>>
> >>
> >>
> >> _______________________________________________
> >> Monami6 mailing list
> >> Monami6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/monami6
> >>
> >
> > _______________________________________________
> > Monami6 mailing list
> > Monami6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/monami6
> >
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 02:12:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTv43-0001bW-Ta; Thu, 13 Apr 2006 02:12:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTv42-0001Yh-IB
	for monami6@ietf.org; Thu, 13 Apr 2006 02:12:22 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTv40-000819-K1
	for monami6@ietf.org; Thu, 13 Apr 2006 02:12:22 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	524B54F0001
	for <monami6@ietf.org>; Thu, 13 Apr 2006 08:12:19 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 08:12:19 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 08:12:18 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id E3165238E;
	Thu, 13 Apr 2006 09:12:18 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 762FC95C6A;
	Thu, 13 Apr 2006 09:12:18 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 24E3F95C4A;
	Thu, 13 Apr 2006 09:12:18 +0300 (EEST)
Message-ID: <443DEBAB.5010205@ericsson.com>
Date: Thu, 13 Apr 2006 09:11:55 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>
	<1487A357FD2ED544B8AD29E528FF9DF029FA08@NAEX06.na.qualcomm.com>
In-Reply-To: <1487A357FD2ED544B8AD29E528FF9DF029FA08@NAEX06.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 13 Apr 2006 06:12:19.0090 (UTC)
	FILETIME=[382E5F20:01C65EC1]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Soliman, Hesham wrote:
> I started reading the draft and got all the way to page 6. :)
> 
> => Good start :)
> 
> I agree that it is important to save bytes, but IMO not at the cost of 
> making the format non-extendable.
> 
> => I'm not sure about that. The format can be extensible in several
> ways: 
>   - We can define sub-options
>   - We can add a version field that allows for new versions of the 
>     same option. 
> Can you elaborate on how you would like it to be extensible and how the 
> current format stops you from doing that?

Okay, I should have said 'hard to extent'. Sure there are a couple of 
bits left and room for 255 bytes altogether, but let's imagine that we 
end up with the proposed kind of format and then later on when people 
start extending the format. It will be difficult to add new fields, 
because there is no clean way to recognize (and skip) fields. Let's say 
that I write an extension called X, and someone then writes an extension 
called Y. Because I have already added a new field, the author of the 
extension Y has to also take this into account; the Y field could be 
after the X field. I just feel that creating such a chain of dependency 
is not necessarily a good characteristic of a protocol.

> 
>   At minimum the described format should follow the alignment rules which 
>   is not true here. If all fields are present, there are more than one 
>   alignment errors: Flow Label, the SPI field, and the C.S. field which 
>   doesn't even fall into natural 32-bit word boundaries. 
> 
> => What is the alignment rule? :) 

I was not referring to the alignment rule in this particular case, 
because there in none as you pointed out but to a general rule of 
aligning IPv6 options.

This option is defined so that it does
> *not* have static alignment. I know this is different from the way we define
> options in IPv6, but I'd like to hear why this is really bad and whether 
> having a fixed option is a lot better given the huge waste we will have

I don't know about being really bad, but I'm sure that some experts can 
write a novel about why alignment is generally a good thing. Anyway, 
proper alignment increases the processing speed (important for servers 
like the HA) and it eases the implementation task (less bugz)

Let's consider, for example, the C.S. field when all fields are present. 
Currently the host has to extract the information with something like:

cs = ((((char *) p->data[cs_offset])   & 0x0f) << 4) |
      ((((char *) p->date[cs_offset+1]) & 0xf0) >> 4);

instead of:

cs = p->data[cs_offset];

In addition, some architectures can't handle integers that don't start 
from their natural word boundaries, i.e.

flow_label = *((u16_t *) p->data[fl_offset]);

would crash the system.

The situation could be improved at least to some extend with the 
following re-arrangement of the fields:

       |                                                               |
       +                                                               +
       |                                                               |
       +                       Source Address                          +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                    Destination Address                        +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                            SPI                                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Source port               |    Destination port           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |        Flow Label             |   Protocol    |     C. S.     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

How does that sound?

Regz,
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:23:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTx71-0007bT-Va; Thu, 13 Apr 2006 04:23:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTx70-0007bO-UX
	for monami6@ietf.org; Thu, 13 Apr 2006 04:23:34 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTx6z-0003LA-Fe
	for monami6@ietf.org; Thu, 13 Apr 2006 04:23:34 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id B0B5C212C63
	for <monami6@ietf.org>; Thu, 13 Apr 2006 11:23:31 +0300 (EEST)
Received: from [193.234.219.40] (n40.nomadiclab.com [193.234.219.40])
	by n2.nomadiclab.com (Postfix) with ESMTP id 4631A212C5F
	for <monami6@ietf.org>; Thu, 13 Apr 2006 11:23:31 +0300 (EEST)
Message-ID: <443E0A82.3030003@iki.fi>
Date: Thu, 13 Apr 2006 11:23:30 +0300
From: Martti Kuparinen <martti.kuparinen@iki.fi>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
References: <4422AFBF.7080603@nomadiclab.com>	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>	<443B7426.3010408@ericsson.com>	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<m28xqakuyo.wl%ryuji@sfc.wide.ad.jp>
In-Reply-To: <m28xqakuyo.wl%ryuji@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Ryuji Wakikawa wrote:

> So, bulk registration for CN needs more discussion whether it's really need. 
> If yes, which RO mechanism we should support? 

>From the bytes-sent-between-the-nodes point of view bulk registration is really
beneficial and makes a lot sense.

We have made some performance analysis on the bulk registration so you (=this
list) can expect a draft next week...

> I would like to support bulk registration to HA, but not to CN at this point.
> RO mechanism is not completed yet, except for RR. If we exclude bulk registation to CN, 
> we can produce signle document

Personally I'm fine with this (to get things started) but I also would like to
see the BIDA option in the draft so we can correctly see what CoAs were
successfully registered and which not.

Binding Unique Identifier Acknowledgement sub-option (BIDA)

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   |   Type = TBD  |     Length    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Binding Unique ID (BID)   |  Status       |    Reserved   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Binding Unique ID (BID)   |  Status       |    Reserved   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

And while suggesting things, I think we really should not reuse the ACoA option
when doing bulk registration (which could confuse legacy HAs/CNs) but have these
two options instead of your proposed BID option:

Home Binding Unique Identifier sub-option (HBID)

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   |   Type = TBD  |     Length    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Binding Unique ID (BID)   |  Priority     |C|  Reserved   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                        Care-of Address                        +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Correspondent Binding Unique Identifier sub-option (CBID)

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   |   Type = TBD  |     Length    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Binding Unique ID (BID)   |  Priority     |    Reserved   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Later, when we come up with a solution for the CN bulk registration we can
modify the CBID option and not mess with the HBID option.

Martti

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:27:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxB8-0002y6-Dt; Thu, 13 Apr 2006 04:27:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxB7-0002xn-NU
	for monami6@ietf.org; Thu, 13 Apr 2006 04:27:49 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxB7-0003Qx-7r
	for monami6@ietf.org; Thu, 13 Apr 2006 04:27:49 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 34E22212C63
	for <monami6@ietf.org>; Thu, 13 Apr 2006 11:27:48 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id EFC90212C5F
	for <monami6@ietf.org>; Thu, 13 Apr 2006 11:27:47 +0300 (EEST)
Message-ID: <443E0B91.1010405@nomadiclab.com>
Date: Thu, 13 Apr 2006 11:28:01 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
References: <4422AFBF.7080603@nomadiclab.com>
	<443B7426.3010408@ericsson.com>	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>	<200604111520.58537.feketgai@index.hu>	<6780888f55d5ce9cbde5632b3473a5ce@it.uc3m.es>
	<m24q0yktkh.wl%ryuji@sfc.wide.ad.jp>
In-Reply-To: <m24q0yktkh.wl%ryuji@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Ryuji,

Ryuji Wakikawa wrote:
> 
> Can you list up the several issues of MCoA?? I only catch the issue of
> CoA authentication for bulk registartion to CN.
> 

Issues with bulk registration with HA in the current MCoA draft:

1. No legacy HA support in the bulk registration. It is not only a 
problem of choosing the right ACoA option if you have many. Legacy 
support is also a problem if the MN has just two interfaces (2 CoAs) and 
tries a bulk registration with legacy HA. In this case it might add one 
of the CoAs to the source field of the BU message and the other CoA into 
the ACoA option. Now, if this message is received by a legacy HA it 
takes the CoA from tha ACoA option and replies BA (status = 0). So the 
outcome is that the MN has a valid binding but with the other interface 
it was intending to register in the first place.

2. You cannot say that it is a bulk registration if in some cases you 
have to send more than one BU to the HA. In the other mail I specified a 
scenario (don't know how unlikly you think it is) where the MN cannot 
update all the BIDs/CoAs with a single BU. In this case the opinion was 
to send one or more BUs to remove not needed BIDs and one or more BU 
messages to update some of the BIDs. This is not a bulk registration... 
There could be several solutions for this using the lifetime field in 
the BID option, adding a remove flag to the BID option etc...

3. No support for different binding lifetimes for different home 
ragistrations. This I quess is just a minor issue?

I think if you want to have the bulk registration in the base MCoA draft 
for HA you MUST fix the first issue and SHOULD fix the second (so in 
some cases you don't have to resort to sending multiple BUs) and SHOULD 
also consider if it would be wise to have the binding lifetime in the 
BID option.


-Heikki



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:29:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxCV-0003T4-0I; Thu, 13 Apr 2006 04:29:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxCU-0003PK-91
	for monami6@ietf.org; Thu, 13 Apr 2006 04:29:14 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxCS-0003SL-KU
	for monami6@ietf.org; Thu, 13 Apr 2006 04:29:14 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	177624F0001
	for <monami6@ietf.org>; Thu, 13 Apr 2006 10:29:12 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 10:29:11 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 10:29:11 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 7E0372969;
	Thu, 13 Apr 2006 11:29:11 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 44CBB95C6A;
	Thu, 13 Apr 2006 11:29:11 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id DC55C95C4A;
	Thu, 13 Apr 2006 11:29:10 +0300 (EEST)
Message-ID: <443E0BBF.20507@ericsson.com>
Date: Thu, 13 Apr 2006 11:28:47 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
	<1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
In-Reply-To: <1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 13 Apr 2006 08:29:11.0693 (UTC)
	FILETIME=[574623D0:01C65ED4]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

We realize that some changes to the BC and the BUL are required, but do 
not think that flow matching rules should be part of the databases. 
Hence, we feel that the database structure should be something like:

    +---------+
    | Policy  | * Policies with flow matching rules.
    | DB      |   Queries results in a BID list, e.g.
    +---------+   if src_port=6666 && dst_port=80 -> BID=77,...

    +--------+
    |BU /BUL | * The standard binding list completed with the BID field.
    +--------+

Entries in the databases would be something like:

  Policy/Flow DB                            BC/BUL
  +---------------------+-------+..+---+   +---------------+-------+
  | Flow matching Rules | BID X |  | Z |   | RFC3775 stuff | BID X |
  +---------------------+-------+..+---+   +---------------+-------+
  | Flow matching Rules | BID Y |  | Z |   | RFC3775 stuff | BID Y |
  +---------------------+-------+..+---+   +---------------+-------+
  .                             .  .   .   | RFC3775 stuff | BID Z |
  +---------------------+-------+..        +---------------+-------+
  | Flow matching Rules | BID X |
  +---------------------+-------+.. . .

Note that one entry in the policy/flow DB can contain more than one BID.
-- 
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:41:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxNt-0001Ux-3e; Thu, 13 Apr 2006 04:41:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxNr-0001Us-D6
	for monami6@ietf.org; Thu, 13 Apr 2006 04:40:59 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxNq-0003tL-PL
	for monami6@ietf.org; Thu, 13 Apr 2006 04:40:59 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D8euUl027711; Thu, 13 Apr 2006 17:40:56 +0900
Date: Thu, 13 Apr 2006 17:40:51 +0900
Message-ID: <m2wtdtkgvg.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Martti Kuparinen <martti.kuparinen@iki.fi>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <443E0A82.3030003@iki.fi>
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
	<443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<m28xqakuyo.wl%ryuji@sfc.wide.ad.jp> <443E0A82.3030003@iki.fi>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hello Martti

At Thu, 13 Apr 2006 11:23:30 +0300,
Martti Kuparinen wrote:
> 
> Ryuji Wakikawa wrote:
> 
> > So, bulk registration for CN needs more discussion whether it's really need. 
> > If yes, which RO mechanism we should support? 
> 
> >From the bytes-sent-between-the-nodes point of view bulk registration is really
> beneficial and makes a lot sense.
> 
> We have made some performance analysis on the bulk registration so you (=this
> list) can expect a draft next week...

Yes, i'll wait for that.

> > I would like to support bulk registration to HA, but not to CN at this point.
> > RO mechanism is not completed yet, except for RR. If we exclude bulk registation to CN, 
> > we can produce signle document
> 
> Personally I'm fine with this (to get things started) but I also would like to
> see the BIDA option in the draft so we can correctly see what CoAs were
> successfully registered and which not.

agree.

How about HA include BIDA option only when there is an error.
When an error is occurred, BA looks like
+---------------------+---------------+----------------+
|BA (status=Bulk fail)|BIDA(BID,Error)| BIDA(BID,Error)| 
+---------------------+---------------+----------------+

Otherwise, HA replies with
+------------------------+
|BA (status=Bulk success)|
+------------------------+

This can save certain bits.


> Binding Unique Identifier Acknowledgement sub-option (BIDA)
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                                    |   Type = TBD  |     Length    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |     Binding Unique ID (BID)   |  Status       |    Reserved   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    ...
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |     Binding Unique ID (BID)   |  Status       |    Reserved   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> And while suggesting things, I think we really should not reuse the ACoA option
> when doing bulk registration (which could confuse legacy HAs/CNs) but have these
> two options instead of your proposed BID option:
> 
> Home Binding Unique Identifier sub-option (HBID)
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                                    |   Type = TBD  |     Length    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |     Binding Unique ID (BID)   |  Priority     |C|  Reserved   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                                                               |
>    +                                                               +
>    |                                                               |
>    +                        Care-of Address                        +
>    |                                                               |
>    +                                                               +
>    |                                                               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

THis is useful only when bulk Reg is used. When MN does separate registration,
128bit is useless, since CoA is in IPv6 header.
So I want to go with a new CoA option instead of ACoA option, which
format should be same as ACoA except for type value.


> Correspondent Binding Unique Identifier sub-option (CBID)
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                                    |   Type = TBD  |     Length    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |     Binding Unique ID (BID)   |  Priority     |    Reserved   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> 
> Later, when we come up with a solution for the CN bulk registration we can
> modify the CBID option and not mess with the HBID option.

I prefer using the same option for both HA and CN. We can carrry more
infromation by defining a new sub-option if necessary.

ryuji

> Martti
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:45:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxS1-0003XP-KG; Thu, 13 Apr 2006 04:45:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxS0-0003Wn-OV
	for monami6@ietf.org; Thu, 13 Apr 2006 04:45:16 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxS0-00040w-9g
	for monami6@ietf.org; Thu, 13 Apr 2006 04:45:16 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 9BDCF212C63;
	Thu, 13 Apr 2006 11:45:15 +0300 (EEST)
Received: from [193.234.219.40] (n40.nomadiclab.com [193.234.219.40])
	by n2.nomadiclab.com (Postfix) with ESMTP id 648B6212C5F;
	Thu, 13 Apr 2006 11:45:15 +0300 (EEST)
Message-ID: <443E0F9A.3070006@iki.fi>
Date: Thu, 13 Apr 2006 11:45:14 +0300
From: Martti Kuparinen <martti.kuparinen@iki.fi>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
References: <4422AFBF.7080603@nomadiclab.com>	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>	<443B7426.3010408@ericsson.com>	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>	<m28xqakuyo.wl%ryuji@sfc.wide.ad.jp>	<443E0A82.3030003@iki.fi>
	<m2wtdtkgvg.wl%ryuji@sfc.wide.ad.jp>
In-Reply-To: <m2wtdtkgvg.wl%ryuji@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Ryuji Wakikawa wrote:

> How about HA include BIDA option only when there is an error.
> When an error is occurred, BA looks like
> +---------------------+---------------+----------------+
> |BA (status=Bulk fail)|BIDA(BID,Error)| BIDA(BID,Error)| 
> +---------------------+---------------+----------------+
> 
> Otherwise, HA replies with
> +------------------------+
> |BA (status=Bulk success)|
> +------------------------+

Sounds reasonable.

>> Home Binding Unique Identifier sub-option (HBID)
>>
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>                                    |   Type = TBD  |     Length    |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |     Binding Unique ID (BID)   |  Priority     |C|  Reserved   |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +                        Care-of Address                        +
>>    |                                                               |
>>    +                                                               +
>>    |                                                               |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> THis is useful only when bulk Reg is used. When MN does separate registration,
> 128bit is useless, since CoA is in IPv6 header.
> So I want to go with a new CoA option instead of ACoA option, which
> format should be same as ACoA except for type value.

And that's why there is the C flag which tells if the CoA is included or not. In
other words, this is variable length option (either 6 or 22 bytes).

Martti

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:47:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxTu-0004WT-Ia; Thu, 13 Apr 2006 04:47:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxTt-0004WO-SA
	for monami6@ietf.org; Thu, 13 Apr 2006 04:47:13 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxTt-00045T-9q
	for monami6@ietf.org; Thu, 13 Apr 2006 04:47:13 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D8lCUl028457; Thu, 13 Apr 2006 17:47:12 +0900
Date: Thu, 13 Apr 2006 17:47:07 +0900
Message-ID: <m2vetdkgl0.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Heikki Mahkonen <heikki@nomadiclab.com>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <443E0B91.1010405@nomadiclab.com>
References: <4422AFBF.7080603@nomadiclab.com> <443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<200604111520.58537.feketgai@index.hu>
	<6780888f55d5ce9cbde5632b3473a5ce@it.uc3m.es>
	<m24q0yktkh.wl%ryuji@sfc.wide.ad.jp>
	<443E0B91.1010405@nomadiclab.com>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

At Thu, 13 Apr 2006 11:28:01 +0300,
Heikki Mahkonen wrote:
> 
> Hi Ryuji,
> 
> Ryuji Wakikawa wrote:
> > 
> > Can you list up the several issues of MCoA?? I only catch the issue of
> > CoA authentication for bulk registartion to CN.
> > 
> 
> Issues with bulk registration with HA in the current MCoA draft:
> 
> 1. No legacy HA support in the bulk registration. It is not only a 
> problem of choosing the right ACoA option if you have many. Legacy 
> support is also a problem if the MN has just two interfaces (2 CoAs) and 
> tries a bulk registration with legacy HA. In this case it might add one 
> of the CoAs to the source field of the BU message and the other CoA into 
> the ACoA option. Now, if this message is received by a legacy HA it 
> takes the CoA from tha ACoA option and replies BA (status = 0). So the 
> outcome is that the MN has a valid binding but with the other interface 
> it was intending to register in the first place.

MIP6 spec does not say to check the source address of BA with the sent CoA.
OK, this can be easily fixed. I will fix this in next revision.

> 2. You cannot say that it is a bulk registration if in some cases you 
> have to send more than one BU to the HA. In the other mail I specified a 
> scenario (don't know how unlikly you think it is) where the MN cannot 
> update all the BIDs/CoAs with a single BU. In this case the opinion was 
> to send one or more BUs to remove not needed BIDs and one or more BU 
> messages to update some of the BIDs. This is not a bulk registration... 
> There could be several solutions for this using the lifetime field in 
> the BID option, adding a remove flag to the BID option etc...

MN can update all binding by sending single BU, because BID is kept
same when binding is updated. 
I think I've already replied to your previous mail.

> 3. No support for different binding lifetimes for different home 
> ragistrations. This I quess is just a minor issue?

Can you elaborate this? 

> I think if you want to have the bulk registration in the base MCoA draft 
> for HA you MUST fix the first issue and SHOULD fix the second (so in 
> some cases you don't have to resort to sending multiple BUs) and SHOULD 
> also consider if it would be wise to have the binding lifetime in the 
> BID option.

For issue1, I will fix that. 
I think you mis-interpret the draft for the issue2. 
For issue3, i'll wait for your reply:-)

thanks,
ryuji 

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 04:49:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTxVs-0005Vg-5X; Thu, 13 Apr 2006 04:49:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTxVq-0005Vb-Hg
	for monami6@ietf.org; Thu, 13 Apr 2006 04:49:14 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTxVq-0004A8-08
	for monami6@ietf.org; Thu, 13 Apr 2006 04:49:14 -0400
Received: from n128-19.sfc.wide.ad.jp.sfc.wide.ad.jp (n128-19.sfc.wide.ad.jp
	[203.178.128.19]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3D8nDUl028756; Thu, 13 Apr 2006 17:49:13 +0900
Date: Thu, 13 Apr 2006 17:49:08 +0900
Message-ID: <m2u08xkghn.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Martti Kuparinen <martti.kuparinen@iki.fi>
Subject: Re: bulk registration (was Re: [Monami6] Changes needed to MCoA draft?
In-Reply-To: <443E0F9A.3070006@iki.fi>
References: <4422AFBF.7080603@nomadiclab.com>
	<F9EED1DE-874A-4C84-8EC2-6968D2009827@sfc.wide.ad.jp>
	<443B7426.3010408@ericsson.com>
	<910da3595853477a839bb5fbd7e79538@it.uc3m.es>
	<m28xqakuyo.wl%ryuji@sfc.wide.ad.jp> <443E0A82.3030003@iki.fi>
	<m2wtdtkgvg.wl%ryuji@sfc.wide.ad.jp> <443E0F9A.3070006@iki.fi>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

At Thu, 13 Apr 2006 11:45:14 +0300,
Martti Kuparinen wrote:
> 
> Ryuji Wakikawa wrote:
> 
> > How about HA include BIDA option only when there is an error.
> > When an error is occurred, BA looks like
> > +---------------------+---------------+----------------+
> > |BA (status=Bulk fail)|BIDA(BID,Error)| BIDA(BID,Error)| 
> > +---------------------+---------------+----------------+
> > 
> > Otherwise, HA replies with
> > +------------------------+
> > |BA (status=Bulk success)|
> > +------------------------+
> 
> Sounds reasonable.
> 
> >> Home Binding Unique Identifier sub-option (HBID)
> >>
> >>     0                   1                   2                   3
> >>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>                                    |   Type = TBD  |     Length    |
> >>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>    |     Binding Unique ID (BID)   |  Priority     |C|  Reserved   |
> >>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>    |                                                               |
> >>    +                                                               +
> >>    |                                                               |
> >>    +                        Care-of Address                        +
> >>    |                                                               |
> >>    +                                                               +
> >>    |                                                               |
> >>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > 
> > THis is useful only when bulk Reg is used. When MN does separate registration,
> > 128bit is useless, since CoA is in IPv6 header.
> > So I want to go with a new CoA option instead of ACoA option, which
> > format should be same as ACoA except for type value.
> 
> And that's why there is the C flag which tells if the CoA is included or not. In
> other words, this is variable length option (either 6 or 22 bytes).

Ah, OK. It looks fine. 

I'll fix the draft according to this.

thanks
ryuji

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 07:32:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU03w-0008Es-4u; Thu, 13 Apr 2006 07:32:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU03v-0008En-07
	for monami6@ietf.org; Thu, 13 Apr 2006 07:32:35 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU03u-00010Z-AF
	for monami6@ietf.org; Thu, 13 Apr 2006 07:32:34 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 51AEA212C63
	for <monami6@ietf.org>; Thu, 13 Apr 2006 14:32:33 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id DE722212C46
	for <monami6@ietf.org>; Thu, 13 Apr 2006 14:32:32 +0300 (EEST)
Message-ID: <443E36DD.1040305@nomadiclab.com>
Date: Thu, 13 Apr 2006 14:32:45 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
	<1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
In-Reply-To: <1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Hesham,

Soliman, Hesham wrote:
> 
> 
> 
>   I have also read this draft and I think that the Binding Update List
>   (BUL) and Binding Cache (BC) are not the right place to hold the
>   policy/flow binding information. If you use these data structures for
>   this information and the MN returns home you loose all the policies as
>   the  entries in BUL and BC are removed.
> 
> => This draft describes flow binding for the cases where the mobile node
> has either:
>   1. more than one CoA
>   2. a HoA and a CoA (i.e. the MN is at home and a foreign network at 
> the same
>      time).
> If the MN is only at home then of course the BC entries are removed and 
> the use
> of MIP is not appropriate to split flows. I don't understand your 
> concern here
> about deleting policies. If you want to route flows differently while you're
> at home (i.e. between 2 different HoAs) then MIP is not a good tool for 
> doing that.
> But I don't see much benefit in that scenario.
>
==> As Tero showed/told in his mail we think that the multihoming should 
be regarded as a general technical issue and the MIPv6 is needed to 
enable the practical use of multihoming. I mean MIPv6 is needed so the 
MN can use its identifier (HoA) for traffic flows instead of the 
locators (CoAs). This way if one flow moves between CoAs (possibly 
interfaces) the traffic flow does not stop. If the monami6 charter says 
that the multihoming should be regarded as something which can only be 
achieved if you use MIPv6 and in the way the monami6 describes (only in 
foreign link), it is IMO wrong. This said, my reasoning is that MNs have 
a need to bind flows to interfaces or different HoAs even if they are 
attached to home network. When the MN moves away from the home network 
these flows must also be mapped to CoAs (BIDs) and when it returns again 
they are mapped to interfaces or HoAs again.

I don't know if this is something that should be standardized or should 
it be left to implementors. I do however think that if you already have 
a need for some general policy data structure in multihomed node you 
should not make a specification which says that you need this 
information also to be copied into MIPv6 data structures if there is no 
reason for having it there. I mean it is enough to map a policy to 
interface(s), HoA(s) or CoA(s) with BID(s) which is specified in the 
MCoA draft.

>   Or if it is decided that these
>   data structures are best place to hold this information, shouldn't there
>   be some way to keep the "policy"/"flow binding" entries there while the
>   MN is at home?
> 
> => What for? Could please show a scenario?
>
==> As I mentioned above I think that the MNs have a need for the 
multihoming mechanism even if they are located at home network. One 
situation could be that the MN has two interfaces which are both 
attached to their home links. In this case some policies are needed to 
map flows between the interfaces and HoAs and if one or both interfaces 
make a handover then these flows need to be mapped to BIDs. I don't know 
if this is reasonable scenario? At least its possible but might be 
unlikely. Hey, at least I tried. =)

>   In addition there should be machanism to use multiple
>   addresses/interfaces for one flow. I think the packet format as it is
>   right now does not offer a way to extend support for using multiple
>   addresses per flow, right?
> 
> => That's right. Splitting the same flow to two different interfaces
> is not a good thing to do because:
>   - It can cause packets to arrive out of order
>   - It can break security if the packets are protected.
> So I don't think this is something we want to do.
>
==> The drafts ( "Motivations and Scenarios for Using Multiple 
Interfaces and Global Addresses" and "Analysis of Multihoming in Mobile 
IPv6" ) in the monami6 WG say that this could be used in some scenarios. 
Anyway, I would not be too concern how the packets would arrive (TCP) or 
how the security is handled in this situation. I think this is a whole 
new technical discussion which is not part of the monami6 charter. I 
think that in this WG it should be researched if this is possible or 
not, technically I mean. The use cases for it could come up later in 
some other WG. However, the other draft (above) already specifies at 
least some use cases...

Finally, I'm not saying that the flow binding draft is completely 
useless. I think that in some cases the BU would be good place to 
distribute policies. One good issue is that the MIPv6 security 
mechanisms can be used to secure also the policies. However, I think 
that these policies should be kept in the general policy data structure 
and they should be mapped to CoAs with BIDs not FIDs. Bad thing is that 
if you want to enable multihoming for MNs in home link the BU cannot be 
used to distribute the policies.

-Heikki

> Hesham
> 
> Best regards,
> 
> Heikki Mahkonen
> 
> Tero Kauppinen (JO/LMF) wrote:
>  > I started reading the draft and got all the way to page 6. :)
>  >
>  > I agree that it is important to save bytes, but IMO not at the cost of
>  > making the format non-extendable.
>  >
>  > At minimum the described format should follow the alignment rules which
>  > is not true here. If all fields are present, there are more than one
>  > alignment errors: Flow Label, the SPI field, and the C.S. field which
>  > doesn't even fall into natural 32-bit word boundaries. I realize that
>  > one or more fields can be missing in which case the layout is different,
>  > but still alignment rules should be obeyed in all cases.
>  >
> 
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 07:56:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0R7-0005YI-67; Thu, 13 Apr 2006 07:56:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0R6-0005YA-3U
	for monami6@ietf.org; Thu, 13 Apr 2006 07:56:32 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0R4-0001dQ-H6
	for monami6@ietf.org; Thu, 13 Apr 2006 07:56:32 -0400
Received: from [203.178.128.19] (n128-19.sfc.wide.ad.jp [203.178.128.19])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3DBuSUl018606
	for <monami6@ietf.org>; Thu, 13 Apr 2006 20:56:28 +0900
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <1144820195.24464.16.camel@localhost>
References: <443BC71A.3020401@enst-bretagne.fr>
	<1144820195.24464.16.camel@localhost>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2FE01C70-5722-4B92-9315-CFBEE8B886C2@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Monami6] MCoA draft
Date: Thu, 13 Apr 2006 20:56:22 +0900
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Chan-wah

On 2006/04/12, at 14:36, Chan-Wah Ng wrote:

> On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
>> Folks,
>>
>> According to the discussion at Vancounver and Dallas, we think  
>> that we
>> reached a rough consensus to accept
>
> Really?  Unless you call a ratio of less than 3 (for) : 1 (against) a
> "rough consensus" (which was what I counted in Dallas).
>
>>
>> Multiple Care-of addresses registration
>> draft-wakikawa-mobileip-multiplecoa-05
>>
>> as a WG document for the 3rd deliverable:
>>
>>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
>> Support (RFC 3963) to support the registration of multiple Care-of
>> Addresses at a given Home Agent address [Standard Track].
>>
>> The document has been improved between the 2 IETF meetings in a  
>> way that
>> we think meets the request of the WG members as expressed at  
>> Vancouver.
>
> Again, as mentioned in ML: I see at least two unresolved issues:
>
> - Bulk Registrations.
> - Simultaneously at home and foreign.

Right, these are issues brought up on ML.

However, I still don't think the second is an issue.
Keigo's proposal can be also achieved by home network configuration,
which needs no modification to current spec. On the other hand, his  
proposal
may bring several issue which may break notion of MIP's returning home.
We can keep discussing this on ML.

The first one should be Bulk Registration to CN.

ryuji

> Having said all that, I am not against moving the draft to WG  
> draft.  In
> fact, changing it to WG draft would force us to maintain an issue  
> list,
> then we will truly know how many issues there are.  I just wanted to
> keep the fact rights.
> /rgds
> /cwng
>
>> The document will therefore be forwarded to the IETF secretariat.
>>
>> In the meantime, do not hesitate to (continue to) comment on the  
>> draft.
>>
>> Nicolas & Thierry.
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 08:06:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0aU-0008BJ-Eq; Thu, 13 Apr 2006 08:06:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0aT-0008BE-Mr
	for monami6@ietf.org; Thu, 13 Apr 2006 08:06:13 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0aT-0001qx-27
	for monami6@ietf.org; Thu, 13 Apr 2006 08:06:13 -0400
Received: from [203.178.128.19] (n128-19.sfc.wide.ad.jp [203.178.128.19])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3DC6CUl019607
	for <monami6@ietf.org>; Thu, 13 Apr 2006 21:06:12 +0900
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <7c33e94a3484445558456f4277735bc5@it.uc3m.es>
References: <443BC71A.3020401@enst-bretagne.fr>
	<1144820195.24464.16.camel@localhost>
	<60BE7F1C-66BE-4F47-8B2C-ABE84A665769@enst-bretagne.fr>
	<7c33e94a3484445558456f4277735bc5@it.uc3m.es>
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <923D8672-9276-438A-BBBB-1D80CC125DB0@sfc.wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Monami6] MCoA draft
Date: Thu, 13 Apr 2006 21:06:05 +0900
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Marcelo

On 2006/04/12, at 17:30, marcelo bagnulo braun wrote:

> Hi,
>
> I must say that i fully agree with Chan-Wah here...
>
> El 12/04/2006, a las 9:05, Nicolas Montavont escribi=C3=B3:
>
>> Hi,
>>
>> On Apr 12, 2006, at 7:36 AM, Chan-Wah Ng wrote:
>>
>>> On Tue, 2006-04-11 at 17:11 +0200, Nicolas Montavont wrote:
>>>> Folks,
>>>>
>>>> According to the discussion at Vancounver and Dallas, we think =20
>>>> that we
>>>> reached a rough consensus to accept
>>>
>>> Really?  Unless you call a ratio of less than 3 (for) : 1 =20
>>> (against) a
>>> "rough consensus" (which was what I counted in Dallas).
>>
>> Most of people were for the adoption of the document as a WG =20
>> document, including AD and chair of other WG.
>>
>> The few people who were against failed to show major concerns =20
>> (some issues are still unresolved of course, but this can be dealt =20=

>> while the document is a WG document.
>>
>
> that is not what i recall from the meeting.
>
> imho there was not clear rough consensus in the dallas meeting
>
> however, the decision must be taken on the list i guess
>
>>>
>>>>
>>>> Multiple Care-of addresses registration
>>>> draft-wakikawa-mobileip-multiplecoa-05
>>>>
>>>> as a WG document for the 3rd deliverable:
>>>>
>>>>    - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
>>>> Support (RFC 3963) to support the registration of multiple Care-of
>>>> Addresses at a given Home Agent address [Standard Track].
>>>>
>>>> The document has been improved between the 2 IETF meetings in a =20
>>>> way that
>>>> we think meets the request of the WG members as expressed at =20
>>>> Vancouver.
>>>
>>> Again, as mentioned in ML: I see at least two unresolved issues:
>>>
>>> - Bulk Registrations.
>>> - Simultaneously at home and foreign.
>>
>> Sure, but we didn't say that the document is ready for the IESG.
>>
>
> but there was a consensus call in the ml sent by Thierry and people =20=

> brought up those issues as problems in order to accept this  draft =20
> as wg item (not in order to sent it to the IESG).
>
> this, as i understand it, means that there is no consensus to =20
> accept this document as a wg item until there is not a clear =20
> agreement in these issues

I give answer to most of issues. The left one is bulk registration to =20=

CN which we still don't know if it's necessary or not.
THere is no consensus yet to support this in WG. Even if we really =20
need, we can continue to discuss this in separate document.

>
> in particular, i am concerned about the bulk registration issue. =20
> imho this is a major issue, because it is not obvious to me that =20
> the current draft can be extended to support bulk registration =20
> cleanly. I would like to understand if we think that bulk =20
> registration is needed, and if it is, how can be fitted into the =20
> mcoa draft neatly, without being caught in a draft that doesn't =20
> naturally includes such feature. That is why i think more analysis =20
> is needed in this point.

At least, the current spec can support Home bulk registration, though =20=

I have to fix some minor issues.
About CN bulk registration, I want to know whether it's really need =20
at this point.
At the meeting, there are comments saying bulk registration is enough =20=

only for home registration.

>>> Having said all that, I am not against moving the draft to WG =20
>>> draft.  In
>>> fact, changing it to WG draft would force us to maintain an issue =20=

>>> list,
>>> then we will truly know how many issues there are.
>>
>> That's exactly our point, we believe that it is the best way to =20
>> work on the document.
>>
>
> probably, but the point is that there is no consensus to work on =20
> this document yet since there is no consensus to accept it as a wg =20
> item (yet)

I believe most of issues can be solved with modifications to MCoA.
Your further comments are really appreciated to complete MCoA.

thanks
ryuji

> regards, marcelo
>
>
>> Nicolas
>>
>>> I just wanted to
>>> keep the fact rights.
>>>
>>> /rgds
>>> /cwng
>>>
>>>> The document will therefore be forwarded to the IETF secretariat.
>>>>
>>>> In the meantime, do not hesitate to (continue to) comment on the =20=

>>>> draft.
>>>>
>>>> Nicolas & Thierry.
>>>>
>>>>
>>>> _______________________________________________
>>>> Monami6 mailing list
>>>> Monami6@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/monami6
>>>>
>>>
>>> _______________________________________________
>>> Monami6 mailing list
>>> Monami6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 08:07:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0bM-0008NH-Sj; Thu, 13 Apr 2006 08:07:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0bM-0008NC-3C
	for monami6@ietf.org; Thu, 13 Apr 2006 08:07:08 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0bL-0001rj-Io
	for monami6@ietf.org; Thu, 13 Apr 2006 08:07:08 -0400
Received: from [203.178.128.19] (n128-19.sfc.wide.ad.jp [203.178.128.19])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3DC6CUm019607; Thu, 13 Apr 2006 21:07:02 +0900
In-Reply-To: <443BC71A.3020401@enst-bretagne.fr>
References: <443BC71A.3020401@enst-bretagne.fr>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F266BC83-8559-4F65-BFC0-EB8FB1A27610@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Date: Thu, 13 Apr 2006 21:06:56 +0900
To: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Monami6 WG <monami6@ietf.org>
Subject: [Monami6] Re: MCoA draft
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Nicolas and Thierry

We will update the MCoA according to discussion on ML and submit it  
to Monami WG soon.

thanks
ryuji


On 2006/04/12, at 0:11, Nicolas Montavont wrote:

> Folks,
>
> According to the discussion at Vancounver and Dallas, we think that we
> reached a rough consensus to accept
>
> Multiple Care-of addresses registration
> draft-wakikawa-mobileip-multiplecoa-05
>
> as a WG document for the 3rd deliverable:
>
>   - A protocol extension to Mobile IPv6 (RFC 3775) and NEMO Basic
> Support (RFC 3963) to support the registration of multiple Care-of
> Addresses at a given Home Agent address [Standard Track].
>
> The document has been improved between the 2 IETF meetings in a way  
> that we think meets the request of the WG members as expressed at  
> Vancouver. The document will therefore be forwarded to the IETF  
> secretariat.
>
> In the meantime, do not hesitate to (continue to) comment on the  
> draft.
>
> Nicolas & Thierry.
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 08:14:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0iT-0007D4-KK; Thu, 13 Apr 2006 08:14:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0iS-0007Cz-6p
	for monami6@ietf.org; Thu, 13 Apr 2006 08:14:28 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0iR-00021s-Me
	for monami6@ietf.org; Thu, 13 Apr 2006 08:14:28 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 4C61C212C63
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:14:26 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id D6CBB212C46
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:14:25 +0300 (EEST)
Message-ID: <443E40AF.5090303@nomadiclab.com>
Date: Thu, 13 Apr 2006 15:14:39 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: monami6@ietf.org
Subject: [Fwd: Re: bulk registration (was Re: [Monami6] Changes needed to
	MCoA draft?]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

Ryuji Wakikawa wrote:
> 
> MIP6 spec does not say to check the source address of BA with the sent CoA.
> OK, this can be easily fixed. I will fix this in next revision.
> 
==> I think if you are going to use the BID option specified in Martti's
mail this is not an issue...

> 
>>2. You cannot say that it is a bulk registration if in some cases you 
>>have to send more than one BU to the HA. In the other mail I specified a 
>>scenario (don't know how unlikly you think it is) where the MN cannot 
>>update all the BIDs/CoAs with a single BU. In this case the opinion was 
>>to send one or more BUs to remove not needed BIDs and one or more BU 
>>messages to update some of the BIDs. This is not a bulk registration... 
>>There could be several solutions for this using the lifetime field in 
>>the BID option, adding a remove flag to the BID option etc...
> 
> 
> MN can update all binding by sending single BU, because BID is kept
> same when binding is updated. 
> I think I've already replied to your previous mail.
>
==> Ken Nagami wrote in his mail...

> CoA of BID1 or BID2 needs to remove. MN sends BU with lifetime 0 and
> BID-option.
> In this case, I think it does not have a problem.
> MN needs to send bulk BU with reused BID and removed BID separately
 > in the current draft.
>
> BID1, HoA, CoA1  -> CoA4
> BID2, HoA, CoA2  -> remove
> BID3, HoQ, CoA3
>
> Regards,
> Ken Nagami
>
==> So this seems to me that in this situation you must resort into
sending multiple BUs. One with lifetime 0 and one with valid lifetime.
So you could use a flag (lets say R = remove) in BID option which is
added to the bulk(!) BU. Now if the R = 1 you can remove the BID in the
receiving end.

> 
>>3. No support for different binding lifetimes for different home 
>>ragistrations. This I quess is just a minor issue?
> 
> 
> Can you elaborate this? 
> 
==> When the MN sends a bulk BU message this message has only on
lifetime field in the BU header although this message might have several
CoAs from several different interfaces. Each of the CoAs from the
different interfaces might have a different valid lifetimes (or what is
left of them). I don't know how you have planned to implement this case
but seems to me that RFC 3775 requires you to make the home registration
with the smallest lifetime between the home or foreign prefixes. This
means that if you have several CoAs you have to choose the smallest
valid lifetime and use it in the BU header. So every binding will have
the same lifetime which in some cases could be quite short. This also
means that when it is time to refresh the bindings, the MN has to
refresh all the bindigs at the same time as they have the same lifetime
between them ==> bulk BU.

-Heikki


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 08:17:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0l3-0008LL-CC; Thu, 13 Apr 2006 08:17:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0l2-0008LG-4Z
	for monami6@ietf.org; Thu, 13 Apr 2006 08:17:08 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0l1-000265-L4
	for monami6@ietf.org; Thu, 13 Apr 2006 08:17:08 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id F1F7A212C63
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:17:06 +0300 (EEST)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id 8F530212C46
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:17:06 +0300 (EEST)
Message-ID: <443E414F.1070904@nomadiclab.com>
Date: Thu, 13 Apr 2006 15:17:19 +0300
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <443CD92F.4080806@ericsson.com>	<443CDE7B.2090501@nomadiclab.com>	<443CE332.2030201@ericsson.com>	<443CEB48.3000202@enst-bretagne.fr>	<443CF632.5020909@nomadiclab.com>
	<443CF94B.6070903@enst-bretagne.fr>
In-Reply-To: <443CF94B.6070903@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Nicolas,

Nicolas Montavont wrote:
> 
> The FID is mandatory in our draft.
> The FID uniquely identifies a flow binding, and really helps when you 
> want to cancel an existing flow binding.
> 
==> OK! Thank you for clarifying this. As I said I was thinking more in 
lines that the FID = BID to map the flow binding to a BID and that is 
why I said that it is not possible to map it to several BIDs with the 
current packet structure...

>
> We couldn't use the BID, because one BID is linked to one CoA, while in 
> our case, we may need several identifiers for a single CoA. Therefore, 
> an identifier must be linked to a flow binding, not only to a CoA.
>
==> I think it is possible to link one flow to several BIDs or several 
flows to one BID in the general policy data structure.

>
> Because when a node has to forward a packet (CN or HA) to the MN, it 
> should be able to check if the flow maps an existing binding. For 
> example, assume a MN that has registered CoA1 for destination port 1000. 
> When the CN has to send a packet of this flow (port number = 1000), it 
> needs to look into its BC to select the appropriate CoA.
> 
> Does it make sense to you?
>
==> I don't know does it make sense. As said in the earlier mails I 
think that policies should anyway be kept in this general policy data 
scturcture and they should be mapped to CoA with some means. Now, what I 
mean with policy is the same data that your draft actually specifies for 
flow binding. I don't think that this data is needed in two places 
(general policy data structure and BUL/BC), do you? I have been thinking 
that for the mapping between general policy data structure entries and 
BUL/BC entries are made with the BIDs.

I quess you must have differnet opinion?

> 
> This is not very well explained yet in the document, I agree with you :(
> Let start with the easiest: "remove" means that the MN requests the node 
> to delete an existing flow binding.
>
> 
> The idea of the "discard" action was to allow a MN to request its HA not 
> to forward a specific flow. Assume a MN that goes from 802.11 to a GPRS 
> connection. The MN may request its HA to stop forwarding video packets 
> while it uses the GPRS interface.
> 
==> OK! This sounds good. I didn't get this from the draft. Thank you!

-Heikki

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 08:49:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU1G6-0007EG-Hb; Thu, 13 Apr 2006 08:49:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU1G5-0007BG-TG
	for monami6@ietf.org; Thu, 13 Apr 2006 08:49:13 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU1G3-0002xe-Ct
	for monami6@ietf.org; Thu, 13 Apr 2006 08:49:11 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3DCn9aB003030
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:49:09 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 02878-10 for <monami6@ietf.org>;
	Thu, 13 Apr 2006 15:49:07 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3DCn5dX003025
	for <monami6@ietf.org>; Thu, 13 Apr 2006 15:49:07 +0300
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
From: =?ISO-8859-1?Q?G=E1bor?= Fekete <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
In-Reply-To: <443E36DD.1040305@nomadiclab.com>
References: <443CD92F.4080806@ericsson.com> <443CDE7B.2090501@nomadiclab.com>
	<1487A357FD2ED544B8AD29E528FF9DF029FA09@NAEX06.na.qualcomm.com>
	<443E36DD.1040305@nomadiclab.com>
Content-Type: text/plain
Date: Thu, 13 Apr 2006 15:48:44 +0300
Message-Id: <1144932524.10459.24.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

On Thu, 2006-04-13 at 14:32 +0300, Heikki Mahkonen wrote:
> Hi Hesham,
> 
> Soliman, Hesham wrote:
> > 
> > 
> > 
> >   I have also read this draft and I think that the Binding Update List
> >   (BUL) and Binding Cache (BC) are not the right place to hold the
> >   policy/flow binding information. If you use these data structures for
> >   this information and the MN returns home you loose all the policies as
> >   the  entries in BUL and BC are removed.
> > 
> > => This draft describes flow binding for the cases where the mobile node
> > has either:
> >   1. more than one CoA
> >   2. a HoA and a CoA (i.e. the MN is at home and a foreign network at 
> > the same
> >      time).
> > If the MN is only at home then of course the BC entries are removed and 
> > the use
> > of MIP is not appropriate to split flows. I don't understand your 
> > concern here
> > about deleting policies. If you want to route flows differently while you're
> > at home (i.e. between 2 different HoAs) then MIP is not a good tool for 
> > doing that.
> > But I don't see much benefit in that scenario.
> >
> ==> As Tero showed/told in his mail we think that the multihoming should 
> be regarded as a general technical issue and the MIPv6 is needed to 
> enable the practical use of multihoming. I mean MIPv6 is needed so the 
> MN can use its identifier (HoA) for traffic flows instead of the 
> locators (CoAs). This way if one flow moves between CoAs (possibly 
> interfaces) the traffic flow does not stop. If the monami6 charter says 
> that the multihoming should be regarded as something which can only be 
> achieved if you use MIPv6 and in the way the monami6 describes (only in 
> foreign link), it is IMO wrong. This said, my reasoning is that MNs have 
> a need to bind flows to interfaces or different HoAs even if they are 
> attached to home network. When the MN moves away from the home network 
> these flows must also be mapped to CoAs (BIDs) and when it returns again 
> they are mapped to interfaces or HoAs again.
> 
The first thing that cought my attention when started with monami6 is
that it says "Mobile Nodes and Multiple Interfaces in IPv6" but then it
deals only with MIP and NEMO. So, IMHO, the title is a bit misleading.

> I don't know if this is something that should be standardized or should 
> it be left to implementors. I do however think that if you already have 
> a need for some general policy data structure in multihomed node you 
> should not make a specification which says that you need this 
> information also to be copied into MIPv6 data structures if there is no 
> reason for having it there. I mean it is enough to map a policy to 
> interface(s), HoA(s) or CoA(s) with BID(s) which is specified in the 
> MCoA draft.

I agree. But, again, monami6 seems to be MIPv6 (and NEMO) specific.
Or isn't it the case? Now I am confused!

> 
> ...
> Finally, I'm not saying that the flow binding draft is completely 
> useless. I think that in some cases the BU would be good place to 
> distribute policies. One good issue is that the MIPv6 security 
> mechanisms can be used to secure also the policies. However, I think 
> that these policies should be kept in the general policy data structure 
> and they should be mapped to CoAs with BIDs not FIDs. Bad thing is that 
> if you want to enable multihoming for MNs in home link the BU cannot be 
> used to distribute the policies.
> 
If a multi-interfaced MN is at home, you may still use BUs to distribute
policies to CNs.

Just as a side note, neither MIP nor NEMO was designed for multihoming
(or flow-separation), so they have to be "hacked". Monami6 is trying to
"hack" them. In my opinion the biggest ugliness is caused by the fact
that HoA is not only an ID but a locator at the _same_time_.
For flow-separation (different ifaces for different flows) you have to
have a node that does this separation (for inbound traffic for the MN).
For MIPv6, If all the CNs support MIP6 then you are good, but if not
then you have to rely on the HA. But the HA is not there for you all the
time, i.e., if it stops proxying for the HoA then you are left with no
"flow-separator" node (for incoming flows).

Gabor



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 11:39:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU3uy-0004ue-VR; Thu, 13 Apr 2006 11:39:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU3uy-0004u3-6r
	for monami6@ietf.org; Thu, 13 Apr 2006 11:39:36 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU3uw-0000hc-4f
	for monami6@ietf.org; Thu, 13 Apr 2006 11:39:34 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FU3pw-0006hy-Cv
	for monami6@ietf.org; Thu, 13 Apr 2006 11:34:25 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DFYMGa017622
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Thu, 13 Apr 2006 08:34:23 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DFYL8b028125
	for <monami6@ietf.org>; Thu, 13 Apr 2006 08:34:22 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 08:34:21 -0700
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: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Thu, 13 Apr 2006 08:34:22 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00205DE4B@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZewUJQal384zlVS4SdCQ8cg+xn7AATWD4g
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 13 Apr 2006 15:34:21.0833 (UTC)
	FILETIME=[BC809790:01C65F0F]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


 >=20
 > Okay, I should have said 'hard to extent'. Sure there are a=20
 > couple of=20
 > bits left and room for 255 bytes altogether, but let's=20
 > imagine that we=20
 > end up with the proposed kind of format and then later on=20
 > when people=20
 > start extending the format. It will be difficult to add new fields,=20
 > because there is no clean way to recognize (and skip)=20
 > fields. Let's say=20
 > that I write an extension called X, and someone then writes=20
 > an extension=20
 > called Y. Because I have already added a new field, the=20
 > author of the=20
 > extension Y has to also take this into account; the Y field could be=20
 > after the X field. I just feel that creating such a chain of=20
 > dependency=20
 > is not necessarily a good characteristic of a protocol.

=3D> Ok, but can explain how this is different in this particular option
from any other option? These extensions you refer to would be defined
as suboptions so they're completely transparent to this option.=20
Specifically, I'm hoping you could tell me the following:
How do you extend any other option in IPv6 and why is it not=20
applicable here? But please tell me in detail not in an abstract manner.


 > This option is defined so that it does
 > > *not* have static alignment. I know this is different from=20
 > the way we define
 > > options in IPv6, but I'd like to hear why this is really=20
 > bad and whether=20
 > > having a fixed option is a lot better given the huge waste=20
 > we will have
 >=20
 > I don't know about being really bad, but I'm sure that some=20
 > experts can=20
 > write a novel about why alignment is generally a good thing.=20

=3D> Please note that the option will always be aligned, i.e. if not=20
naturally, by padding. So if you're arguing for padded alignment
Vs natural alignment then please clarify that. I know there is=20
a tradeoff with simplicity here, but IMO it's more important to
be radio efficient than to design for a simple implementation.
At least from a job security view point :)


  Anyway,=20
 > proper alignment increases the processing speed (important=20
 > for servers=20
 > like the HA) and it eases the implementation task (less bugz)

=3D> Agreed.

 >=20
 > cs =3D ((((char *) p->data[cs_offset])   & 0x0f) << 4) |
 >       ((((char *) p->date[cs_offset+1]) & 0xf0) >> 4);
 >=20
 > instead of:
 >=20
 > cs =3D p->data[cs_offset];

=3D> Sure, no disagreement here.

 >=20
 > In addition, some architectures can't handle integers that=20
 > don't start=20
 > from their natural word boundaries, i.e.
 >=20
 > flow_label =3D *((u16_t *) p->data[fl_offset]);
 >=20
 > would crash the system.

=3D> I'm not sure if there is something that doesn't start
on a natural boundary here. More below.

 >=20
 > The situation could be improved at least to some extend with the=20
 > following re-arrangement of the fields:
 >=20
 >        |                                                    =20
 >           |
 >        +                                                    =20
 >           +
 >        |                                                    =20
 >           |
 >        +                       Source Address               =20
 >           +
 >        |                                                    =20
 >           |
 >        +                                                    =20
 >           +
 >        |                                                    =20
 >           |
 >       =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >        |                                                    =20
 >           |
 >        +                                                    =20
 >           +
 >        |                                                    =20
 >           |
 >        +                    Destination Address             =20
 >           +
 >        |                                                    =20
 >           |
 >        +                                                    =20
 >           +
 >        |                                                    =20
 >           |
 >       =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >        |                            SPI                     =20
 >           |
 >       =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >        |     Source port               |    Destination port=20
 >           |
 >       =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >        |        Flow Label             |   Protocol    |    =20
 > C. S.     |
 >       =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >=20
 > How does that sound?

=3D> It looks aligned perfectly to me but it's wrong :)=20
if you want this option you need to change RFC 2460 to make=20
the flow label 16 bits instead of 20 :(=20

Hesham



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 13:20:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU5US-0007fy-Jx; Thu, 13 Apr 2006 13:20:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU5UQ-0007do-RX
	for monami6@ietf.org; Thu, 13 Apr 2006 13:20:18 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU5UN-0003uM-V7
	for monami6@ietf.org; Thu, 13 Apr 2006 13:20:18 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DHJPL8029784
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Thu, 13 Apr 2006 10:20:08 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DHJOE6000975
	for <monami6@ietf.org>; Thu, 13 Apr 2006 10:19:25 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 10:18:54 -0700
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: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Thu, 13 Apr 2006 10:18:53 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00205DF7D@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZe7fzDYRj6jfQcQxWVR9aDh94LywALmPEg
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 13 Apr 2006 17:18:54.0649 (UTC)
	FILETIME=[57645A90:01C65F1E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


 > =3D=3D> As Tero showed/told in his mail we think that the=20
 > multihoming should=20
 > be regarded as a general technical issue and the MIPv6 is needed to=20
 > enable the practical use of multihoming. I mean MIPv6 is=20
 > needed so the=20
 > MN can use its identifier (HoA) for traffic flows instead of the=20
 > locators (CoAs). This way if one flow moves between CoAs (possibly=20
 > interfaces) the traffic flow does not stop. If the monami6=20
 > charter says=20
 > that the multihoming should be regarded as something which=20
 > can only be=20
 > achieved if you use MIPv6=20

=3D> Monami is based on MIPv6 as far as I know.=20


  and in the way the monami6=20
 > describes (only in=20
 > foreign link), it is IMO wrong.=20

=3D> Monami is not intended to work only in the foreign link
but it's a side effect of MIPv6 that the signalling only takes
place while your not home. Perhaps you have another idea for doing
this while the MN is home? If so please propose it. I assume it's not
based on MIPv6. If you can see a way of doing this with MIPv6 please
propose that too. Otherwise I'm not sure how to solve this perceived
problem. I just want to make it clear that this is how MIPv6 works
today.


 > that MNs have=20
 > a need to bind flows to interfaces or different HoAs even if=20
 > they are=20
 > attached to home network. When the MN moves away from the=20
 > home network=20
 > these flows must also be mapped to CoAs (BIDs) and when it=20
 > returns again=20
 > they are mapped to interfaces or HoAs again.

=3D> I think it would be nice to do that but I don't know=20
of a reliable way of doing that other than sessions signalling/ SRV
records ...etc. In practice, I think that requiring this in a home=20
network is not necessary since almost all MIP deployments rely=20
on virtual home networks.=20

 > I don't know if this is something that should be=20
 > standardized or should=20
 > it be left to implementors. I do however think that if you=20
 > already have=20
 > a need for some general policy data structure in multihomed node you=20
 > should not make a specification which says that you need this=20
 > information also to be copied into MIPv6 data structures if=20
 > there is no=20
 > reason for having it there.=20

=3D> Of course there is a reason to have it. While the binding is
available,=20
packets are routed based on the policy stored. When there is no binding
there is no policy.=20


I mean it is enough to map a policy to=20
 > interface(s), HoA(s) or CoA(s) with BID(s) which is specified in the=20
 > MCoA draft.

=3D> I don't understand that. Did you read the usage scenarios section =
in
the draft?
You seem to assunme that policies are static.

 > =3D=3D> As I mentioned above I think that the MNs have a need for the =

 > multihoming mechanism even if they are located at home network. One=20
 > situation could be that the MN has two interfaces which are both=20
 > attached to their home links. In this case some policies are=20
 > needed to=20
 > map flows between the interfaces and HoAs and if one or both=20
 > interfaces=20
 > make a handover then these flows need to be mapped to BIDs.=20

=3D> This is different from what you said earlier. You can use the =
current
draft to set policies when one interface is at home and the other is=20
away. You can't use it when both interfaces are at home. And I was=20
questioning the need for that.=20


 > I don't know=20
 > if this is reasonable scenario? At least its possible but might be=20
 > unlikely. Hey, at least I tried. =3D)

=3D> I can't say it's unreasonable, I do think it's unlikely. I'm=20
not saying it can't or shouldn't be solved. I'm saying that it's not=20
doable with MIPv6 and that it's not a high priority scenario given what
we know about current MIP deployments. Feel free to shed a different
light
on this though.


 > =3D=3D> The drafts ( "Motivations and Scenarios for Using Multiple=20
 > Interfaces and Global Addresses" and "Analysis of=20
 > Multihoming in Mobile=20
 > IPv6" ) in the monami6 WG say that this could be used in=20
 > some scenarios.=20
 > Anyway, I would not be too concern how the packets would=20
 > arrive (TCP) or=20
 > how the security is handled in this situation. I think this=20
 > is a whole=20
 > new technical discussion which is not part of the monami6 charter.=20

=3D> Well, it would be a broken solution. I'm sure somewhere in IETF
there is a doc that says we don't want to produce a broken solution :)

I=20
 > think that in this WG it should be researched if this is possible or=20
 > not, technically I mean.=20

=3D> Sure. Feel free to provide input on this topic. I'm happy to =
discuss
it.


 > Finally, I'm not saying that the flow binding draft is completely=20
 > useless. I think that in some cases the BU would be good place to=20
 > distribute policies. One good issue is that the MIPv6 security=20
 > mechanisms can be used to secure also the policies. However, I think=20
 > that these policies should be kept in the general policy=20
 > data structure=20
 > and they should be mapped to CoAs with BIDs not FIDs.=20

=3D> Policy-based routing is a very old concept. The MIP BC can be=20
implemented as a separate data structure, or in the routing table,=20
or in the NC ...etc. We don't require people to implement it in the BC.=20
It's up to you.=20

Hesham


Bad=20
 > thing is that=20
 > if you want to enable multihoming for MNs in home link the=20
 > BU cannot be=20
 > used to distribute the policies.
 >=20
 > -Heikki
 >=20
 > > Hesham
 > >=20
 > > Best regards,
 > >=20
 > > Heikki Mahkonen
 > >=20
 > > Tero Kauppinen (JO/LMF) wrote:
 > >  > I started reading the draft and got all the way to page 6. :)
 > >  >
 > >  > I agree that it is important to save bytes, but IMO not=20
 > at the cost of
 > >  > making the format non-extendable.
 > >  >
 > >  > At minimum the described format should follow the=20
 > alignment rules which
 > >  > is not true here. If all fields are present, there are=20
 > more than one
 > >  > alignment errors: Flow Label, the SPI field, and the=20
 > C.S. field which
 > >  > doesn't even fall into natural 32-bit word boundaries.=20
 > I realize that
 > >  > one or more fields can be missing in which case the=20
 > layout is different,
 > >  > but still alignment rules should be obeyed in all cases.
 > >  >
 > >=20
 > >=20
 > > _______________________________________________
 > > Monami6 mailing list
 > > Monami6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/monami6
 > >=20
 > >=20
 > >=20
 > -------------------------------------------------------------
 > -----------
 > >=20
 > > _______________________________________________
 > > Monami6 mailing list
 > > Monami6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/monami6
 >=20
 >=20
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 >=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 13:36:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU5k0-0002vT-EX; Thu, 13 Apr 2006 13:36:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU5jz-0002YQ-IV
	for monami6@ietf.org; Thu, 13 Apr 2006 13:36:23 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU5hl-0004VX-SA
	for monami6@ietf.org; Thu, 13 Apr 2006 13:34:09 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DHY4tE010041
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Thu, 13 Apr 2006 10:34:05 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3DHY1IL015752
	for <monami6@ietf.org>; Thu, 13 Apr 2006 10:34:04 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Apr 2006 10:34:02 -0700
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: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Thu, 13 Apr 2006 10:34:00 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00205DFC7@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZewUJQal384zlVS4SdCQ8cg+xn7AAXuyCQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 13 Apr 2006 17:34:02.0489 (UTC)
	FILETIME=[7481BE90:01C65F20]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org




 >=20
 > The situation could be improved at least to some extend with the=20
 > following re-arrangement of the fields:

=3D> This format is not correct (see my earlier email), but another=20
option might be to represent the flow label in 24 or 32 bits, with=20
redundant 4, or 12 bits, respectively. I'm ok with this approach.=20

Hesham


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 13 23:22:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FUEsf-0006St-LP; Thu, 13 Apr 2006 23:21:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FUEse-0006So-4v
	for monami6@ietf.org; Thu, 13 Apr 2006 23:21:56 -0400
Received: from jens246.inetcore.com ([202.33.8.246] helo=chappy.inetcore.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUEsc-00084B-IV
	for monami6@ietf.org; Thu, 13 Apr 2006 23:21:56 -0400
Received: from nagami-T42.wide.ad.jp (nt-23 [172.16.2.1])
	by chappy.inetcore.com (8.13.3/8.13.3) with ESMTP id k3E3Lo7D018024;
	Fri, 14 Apr 2006 12:21:51 +0900 (JST)
	(envelope-from nagami@wide.ad.jp)
Message-Id: <6.2.3.4.2.20060414120837.096fa140@inc.inetcore.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2J rev4.2
Date: Fri, 14 Apr 2006 12:19:27 +0900
To: Monami6 WG <monami6@ietf.org>, monami6@ietf.org
From: Ken Nagami <nagami@wide.ad.jp>
Subject: Re: [Fwd: Re: bulk registration (was Re: [Monami6] Changes
	needed toMCoA draft?]
In-Reply-To: <443E40AF.5090303@nomadiclab.com>
References: <443E40AF.5090303@nomadiclab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki,

>>>2. You cannot say that it is a bulk registration if in some cases 
>>>you have to send more than one BU to the HA. In the other mail I 
>>>specified a scenario (don't know how unlikly you think it is) 
>>>where the MN cannot update all the BIDs/CoAs with a single BU. In 
>>>this case the opinion was to send one or more BUs to remove not 
>>>needed BIDs and one or more BU messages to update some of the 
>>>BIDs. This is not a bulk registration... There could be several 
>>>solutions for this using the lifetime field in the BID option, 
>>>adding a remove flag to the BID option etc...
>>
>>MN can update all binding by sending single BU, because BID is kept
>>same when binding is updated. I think I've already replied to 
>>your previous mail.
>==> Ken Nagami wrote in his mail...
>
>>CoA of BID1 or BID2 needs to remove. MN sends BU with lifetime 0 and
>>BID-option.
>>In this case, I think it does not have a problem.
>>MN needs to send bulk BU with reused BID and removed BID separately
> > in the current draft.
>>
>>BID1, HoA, CoA1  -> CoA4
>>BID2, HoA, CoA2  -> remove
>>BID3, HoQ, CoA3
>>
>>Regards,
>>Ken Nagami
>==> So this seems to me that in this situation you must resort into
>sending multiple BUs. One with lifetime 0 and one with valid lifetime.
>So you could use a flag (lets say R = remove) in BID option which is
>added to the bulk(!) BU. Now if the R = 1 you can remove the BID in the
>receiving end.

I understand this issue.
So, we will add a flag or a lifetime in the next MCOA draft.

Ken Nagami


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 14 03:51:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FUJ5i-0006Ka-OA; Fri, 14 Apr 2006 03:51:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FUJ5h-0006Du-U2
	for monami6@ietf.org; Fri, 14 Apr 2006 03:51:41 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUJ5K-0007u0-Gt
	for monami6@ietf.org; Fri, 14 Apr 2006 03:51:41 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IXP00GO7CFX06@szxga03-in.huawei.com> for
	monami6@ietf.org; Fri, 14 Apr 2006 15:50:21 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IXP005PJCFXH7@szxga03-in.huawei.com> for
	monami6@ietf.org; Fri, 14 Apr 2006 15:50:21 +0800 (CST)
Received: from x49105 ([10.110.114.175])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IXP001OOCVUFC@szxml01-in.huawei.com> for
	monami6@ietf.org; Fri, 14 Apr 2006 15:59:57 +0800 (CST)
Date: Fri, 14 Apr 2006 15:42:20 +0800
From: Sam Xia <xiazhongqi@huawei.com>
To: monami6@ietf.org
Message-id: <000401c65f96$f64555b0$af726e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hello, everyone,
          I am confused about a sentence in Analysis of Multihoming in
Mobile IPv6. 
The sentence is "The fact that a mobile node has multiple interfaces does
not 
imply that it has multiple HoAs and vice-versa" and located at the last
paragragh on page 10.
          I think one interface should have a corresponding address or more.
So, if a mobile node is in its home, each of its interfaces has a address at
least.

Anyone can give me the detailed explaination or a scenario? Thanks.



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 14 10:14:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FUP4T-0007cN-42; Fri, 14 Apr 2006 10:14:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FUP4S-0007U6-38
	for monami6@ietf.org; Fri, 14 Apr 2006 10:14:48 -0400
Received: from posti6.jyu.fi ([130.234.4.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUP4O-00034q-Lr
	for monami6@ietf.org; Fri, 14 Apr 2006 10:14:46 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3EEEgt0021711
	for <monami6@ietf.org>; Fri, 14 Apr 2006 17:14:42 +0300
Received: from posti6.jyu.fi ([127.0.0.1])
	by localhost (posti6.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 21636-04 for <monami6@ietf.org>;
	Fri, 14 Apr 2006 17:14:41 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3EEEdIj021695
	for <monami6@ietf.org>; Fri, 14 Apr 2006 17:14:41 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Fri, 14 Apr 2006 17:14:08 +0300
User-Agent: KMail/1.9.1
References: <000401c65f96$f64555b0$af726e0a@china.huawei.com>
In-Reply-To: <000401c65f96$f64555b0$af726e0a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604141714.09878.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Sam,

On Friday 14 April 2006 10:42, Sam Xia wrote:
> Hello, everyone,
>           I am confused about a sentence in Analysis of Multihoming in
> Mobile IPv6. 
> The sentence is "The fact that a mobile node has multiple interfaces does
> not 
> imply that it has multiple HoAs and vice-versa" and located at the last
> paragragh on page 10.
>           I think one interface should have a corresponding address or more.
> So, if a mobile node is in its home, each of its interfaces has a address at
> least.
> 
> Anyone can give me the detailed explaination or a scenario? Thanks.

Read it like:
"A mobile node with multiple interfaces may or may not have multiple HoAs."
"A mobile node with multiple HoAs may or may not have multiple interfaces."

So, I guess you have concerns with the "MN is at home with multiple interfaces"
case. Well, in that case it "may have multiple HoAs".
I assume that:
The MN has a HoA == The MN has assigned the HoA to one of its physical interfaces or
has a binding at the HA for HoA.

Gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 14 13:47:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FUSNb-0004xn-7v; Fri, 14 Apr 2006 13:46:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FUSNZ-0004kT-DM
	for monami6@ietf.org; Fri, 14 Apr 2006 13:46:45 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FUSNW-0001N9-Td
	for monami6@ietf.org; Fri, 14 Apr 2006 13:46:43 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3EHkeJ8006184
	for <monami6@ietf.org>; Fri, 14 Apr 2006 20:46:40 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 06016-10 for <monami6@ietf.org>;
	Fri, 14 Apr 2006 20:46:39 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3EHka8P006172
	for <monami6@ietf.org>; Fri, 14 Apr 2006 20:46:39 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: "Monami6 WG" <monami6@ietf.org>
Subject: [Monami6] Question on draft-soliman-monami6-flow-binding-00.txt
Date: Fri, 14 Apr 2006 20:46:03 +0300
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604142046.05052.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi list,

Some question related to draft-soliman-monami6-flow-binding-00.txt.

1. If the R bit is set in the flow-id option does that
   mean that the Source Address of the flow is the
   destination address of the BU?
2. The flow-id option has the Destination Address
   field. The flow-id is placed in a BU. For me, the BU
   is all about the HoA. The BU tells to the receiver
   what to do with the HoA (e.g. bind to a CoA).
   I think either the Destination Address field should be
   removed in favor of the HoA of the BU, or the flow
   identifier should not be carried in BUs. Any good reason
   this field must be present?
3. In a CN/HA, can two binding cache entries with different
   HoAs have the same FID?
   e.g.:  HoA1-CoA1-FID1
          HoA2-CoA2-FID1
4. Can multiple flow-options be bound to a single BUL entry?
   The draft indicates it but in section 5.1 it does not
   seem that the proposed BUL change supports that.
5. It would be nice to have some conceptual figures of BC and
   BUL to clarify the relation between policies (flow dentifiers)
   and bindings.
6. Action "Discard" is not discussed in section 5.2.1.
7. In section 5.2.2. "Using Alternate Care-Of Address":

   "A mobile node can use an alternate care-of address to issue a Flow
    Identifier for a different Flow Binding."

   Different than what? I do not get it.
8. What does section 5.4 have to do with movement?
9. Section 6 indicates that this draft overlaps with
   draft-wakikawa-mobileip-multiplecoa. So will this draft be changed
   to be a policy extension of draft-wakikawa-mobileip-multiplecoa?
10. Section 6 is quite incomplete and I guess it has quite a bit of
   overlap with section 7. At least some references to the relevant
   HA operations would be good.
11. What happens if HA gets BU with D flag set and it already has
   a different binding with D flag set for the same HoA?
12. Can a Default Binding have a FID?
   If yes then in Section 7.4.2 it should be mentioned. E.g. "If the
   FID in the BU corresponds to the Default Binding then the HA
   deletes all bindings of the HoA."
13. In section 8:
   "... The
   lifetime of the binding is the lifetime of the binding update. ..."
   Why is it mentioned here? Is it important? It's not mentioned for
   HA nor for CN BUs.
14. Section 8:
   "...acknowledgement and includes the flow identification option.  Only
   the first eight octets are required in the option. ..."
   Which option? I guess the flow identification option in the BA. Or not?
15. In Section 10.1:
  "... Care-of address.  In order to differentiate between several bindings
   for the same home address, a Flow Identifier (FID) is used. ..."
   Isn't it the BID rather than the FID?
16. Section 10.3:
  "... several egress interfaces, (ii) when several mobile networks are
   operating the same mobile network, ..."
  Can "several mobile networks" operate a mobile network? Or is it
  "several mobile routers"?

If this draft becomes an add-on for draft-wakikawa-mobileip-multiplecoa and
also bulk-registration for draft-wakikawa-mobileip-multiplecoa is accepted,
I am a bit concerned about the BU packet sizes.

And I just wonder if it was not better to somehow specify flow policies
separately from MIP (or NEMO) and keep it as a general multihoming issue.
For example, there may be several other protocols other than MIP that can
handle multihoming (e.g HIP, DCCP, SCTP) and could benefit from having
policies. Obviously it indicates that policies should not be sent in BUs
but with a separate protocol.
The idea is that we'd have a general policy description and distribution
protocol. The participants in this protocol would then decide what they
do with these policies. The policy description should be such that it could
be mapped to e.g. MIPv6 bindings. For example, again with MIPv6, the
destination address field in the policy descriptor would mean the HoA and
the action for the policy would be the CoA. Then a MIPv6 module at a router
acting as a HA can map this policy to an existing BC entry.
This means that policies are distributed with some extra signaling. But still
it may be useful to other protocols too than MIPv6.
Any ideas/opinions about this?

Regards,
Gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Sun Apr 16 14:41:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVCB3-0006dj-UX; Sun, 16 Apr 2006 14:40:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVCB3-0006ct-5x
	for monami6@ietf.org; Sun, 16 Apr 2006 14:40:53 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVCB0-0002Qq-Fd
	for monami6@ietf.org; Sun, 16 Apr 2006 14:40:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3GIemet015071
	for <monami6@ietf.org>; Sun, 16 Apr 2006 21:40:48 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 14991-05 for <monami6@ietf.org>;
	Sun, 16 Apr 2006 21:40:46 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3GIeiOG015066
	for <monami6@ietf.org>; Sun, 16 Apr 2006 21:40:46 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: "Monami6 WG" <monami6@ietf.org>
Date: Sun, 16 Apr 2006 21:40:37 +0300
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Content-Disposition: inline
X-Length: 2730
X-UID: 1
Subject: [Monami6] Questions on draft-nomadv6-mobileip-filters-03.txt.
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200604162140.39561.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hello everyone,

And now, some questions on draft-nomadv6-mobileip-filters-03.txt.

1. Section 4.1.1 says:
  "Filters for Mobile IPv6 is applicable only in the context of a mobile 
   node maintaining multiple points of attachment to one or more 
   Internet administrative domains. ..."
  Why would not it be applicable with single point of attachment. E.g. the
  MN may have multiple CoAs on its single interface but the end-to-end
  characteristics of these CoAs may be different. Cannot it be?
  E.g. packets to different CoAs may be routed on different paths.

2. Section 4.1.1:
  "N    When set, the binding agent MUST act based on the functions 
        described in section 4.1.3 and add a new entry to the binding 
        cache without deleting any existing entries for the mobile ..."
  I guess this does not mean that "if the N bit is set then the agent
  MUST add a new entry". So I think this text should be deleted or
  clarified.

3. What if the N-bit is set and the BU is a CoA de-registration BU?
  E.g. Can a de-registration BU carry a Filter Deletion Extension?

4. What is the mechanism of matching flows? First match the destination
  address with a HoA and then find the proper CoA using the filters?

5. Section 4.1.3:
  "then a new one will automatically be configured by each involved 
   Filtering Agent to the lowest possible Index of 0.  "
  What does "configured" mean? Created? So the Agent would then create
  a Default filter for the HoA that has index 0, weight 1 and applies
  to any packet? Just because it is not clear from the text.

6. How does the MN specify the Default Filter? With a BU, N-bit set,
  no Filter Modules but only an FCL with index 0? Or can the Default Filter
  be more specific than "match any packet", that is, specifying with a BU,
  N-bit set, Filter Modules and an FCL with index 0?

7. At an agent, does every registered HoA have a Default Filter
  (or rather a Default Binding or Default CoA)?

8. Section 4.1.4:
  "binding. If the lifetime of a binding expires or it is cancelled by 
   the registration of another mobility binding ..."
  Cancellation means "deletion" here? If yes, is it so that it can happen
  only if the MN sends a BU with the N-bit not set while having multiple
  bindings for the corresponding HoA?
  What about an RFC3775 de-registration BU? Is that "cancellation"?
  And if "all associated Filters are deleted from the binding cache" then
  what about shared Filters? Do you delete a shared Filter even if its
  still valid for another Binding Cache entry (a Binding)?
  Oh, yes, and what is the lifetime of a shared Filter?

9. The first paragraph of Section 4.1.6 is overcomplicated. Does not it say
  that a CoA can be bound to multiple HoAs of the MN?
  And in the second paragraph, cannot the MN send the BU for HoA-A from B
  without AltCoA? I think it can.

10. In section 4.1.7 it says:
  "points of attachment, the mobile node MUST de-register all the other 
   bindings that belong to the same home IP address. ..."
  Does the MN need to de-register even at the CNs? Is it for keeping things
  clean and simple? I mean, is the idea that if we are at the network of a
  HoA with an interface then forget this draft for that HoA?

11. Section 4.2:
  "When MN requires transferring flow `d to the interface connected to 
   FN-B, MN sends a binding update with HoA-2 and CoA-C, together with 
   CoA-B in the Alternate care-of-address mobility option and with the 
   required filtering extensions (see section 4.1.6). ..."
  I guess it is just an example but just in case, I'd like to note that
  the BU could be sent from B without AltCoA.
  And also, in the previous paragraph the N-bit was set, and here no text
  about the N-bit. It is obviously set here too, but still.

12. Section 5:
  "... in the destination option. Binding updates without the N 
   bit set are considered as idle mobility bindings. ..."
  Just for clarification, I guess Binding != BU. Rather a Binding is an
  association represented by a Binding Cache Entry.
  Is a NOMADv6 BU without N-bit set the same as an RFC3775 BU?
  So I guess it's more like "Binding updates without the N 
  bit set create idle mobility bindings.". No?

13. So what does this N-bit indicate? Does it indicate that
  a) enable multiple bindings for the HoA in this BU ___AND___
  b) this BU contains filter description(s)/actions?

14. Section 6.1:
  "...Filters will be associated with the registered care-of address at all 
   Filtering Agents (HA,CN,MAP). A mobile node that maintains multiple 
   points of attachment may request for simultaneous mobility bindings 
   by setting the N bit in its binding Updates. ... "
  I guess the "...Filters will be associated with the registered care-of
  address at the Filtering Agent (HA, CN or MAP)".
  Also, what about a MN with a single point of attachment having multiple
  CoAs? It "may request for simultaneous mobility bindings" too.

15. A Filter can be shared between different Bindings and a Binding can be
  associated with multiple Filters.
  For me this tells that Bindings and Filters should be allowed to be
  handled independently and stored in separate "Databases". E.g. according
  to this draft if you want to change only the CoA of an existing Binding
  at the Filtering Agent then you have to send two BUs. One for creating a
  Binding with the new CoA and associated with the same Filter and another
  BU to remove the other Binding.
  BID of draft-wakikawa-mobileip-multiplecoa-05.txt might come handy ;)

16. In Section 6.1.2, does the replacing of a shared filter affect all the
  involved Bindings at the Filtering Agent and not only the one indicated
  by this BU?

17. In Section 6.1.5, how can a single BU re-new the lifetime of all the
  Bindings of a HoA?
  The lifetime belongs not only to the HoA but to a Binding and
  a Binding is identified by (HoA, CoA). Or not?

18. So Section 6.1.6 and 6.1.7 deletes only filters and does not touch Bindings?
  First sign of handling filters independently from bindings :)

19. The 1st paragraph of Section 6.1.8 is quite incomprehensible. Transferring a
  filter? FROM where TO where? Like dis-associating a filter from Binding-A and 
  associating it with Binding-B?

20. The 2nd paragraph of Section 6.1.8 is lost and is desperately looking for its
  place in the draft :). And also:
  "... by the corresponding mobility binding. In the case of 
   shared Filters, packets of matching flows will get distributed 
   between multiple points of attachment with respect to the Weight 
   value of each Filter."
  I thought a shared Filter was "shared" between multiple Bindings. Does "shared
  Filter" mean a Binding with multiple Filters. Just because I cannot see how
  the weight of a Filter can control distribution on multiple PoAs.
  Should not the weight be associated with Bindings rather than Filters in this
  case?
  Or is the semantic of "weight" implementation specific?

21. Section 6.2:
  "Should the Filtering Agent succeed in applying the Filters, then the 
   Filtering Acknowledgement indicating the index of the success MUST be 
   sent, only if `A bit is set on the Binding Update. "
  What about registration with the HA? No Filtering Ack? There is BA...
  "When a mobility binding expires or is deregistered by a mobile node  
   then all associated Filters are deleted with it. ..."
  What about shared filters?

22. Section 7:
  "once. A Filter Module may include one or more predicates. ..."
  What are predicates? Give me an example of a Filter Module with multiple
  predicates please because I don't get it from the text!

That's all for now :)

Thanks,
Gabor


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Apr 17 09:42:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVU05-000746-Dj; Mon, 17 Apr 2006 09:42:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVU03-000741-FN
	for monami6@ietf.org; Mon, 17 Apr 2006 09:42:43 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVU02-0006LS-O9
	for monami6@ietf.org; Mon, 17 Apr 2006 09:42:43 -0400
Received: from [192.168.0.11] (p7006-ipbf1107marunouchi.tokyo.ocn.ne.jp
	[124.101.246.6]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3HDgeUl027881
	for <monami6@ietf.org>; Mon, 17 Apr 2006 22:42:40 +0900
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <442A4191.90504@nomadiclab.com>
References: <4422AC28.6020000@nomadiclab.com>
	<254DFE31-8067-4429-A23F-9A1E494E5BA8@sfc.wide.ad.jp>
	<442A4191.90504@nomadiclab.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DF37AA8B-4D7C-4441-9FF2-A61C5656FA6A@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Monami6] Problem with MCoA draft?!
Date: Mon, 17 Apr 2006 22:42:33 +0900
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.9 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki


On 2006/03/29, at 17:13, Heikki Mahkonen wrote:

> Hi Ryuji,
>
> Thank you for your reply. I have included my (hopefully) clarifying  
> comments inline.
>
> Ryuji Wakikawa wrote:
>> You don't need to de-register CoA1 and CoA2, but only update CoA1  
>> and  CoA2 to CoA4 by two BUs.
>> HA can update the correspondent binding with the new CoA (i.e.  
>> CoA4)  because of BID.
>
> ==> OK! When I wrote the original mail I didn't take into acount  
> that it is possible to reuse BIDs. This I think is what you are  
> talking about in your reply, aren't you? I originally had the  
> misunderstanding that you create new BID for every CoA. So what you  
> do is you rather make one BID for the first CoA you register and  
> when this CoA changes you use the same BID for updating the  
> binding, right? This is a good mechanism but I still see a problem  
> with it and I try to clarify what I think the problem is.

ok

>> Anyway, your scenario may happen, but imagine when a MN has three   
>> different interfaces,
>> the address change will not be often occurred at the same time.
>
> ==> Yes it actually can, because ( I have a good imagination, no  
> =) ), you might have multiple CoAs per interface in this scenario  
> as well. So when you make a handover from one access network to  
> another and you had or now have multiple CoAs you end up sending  
> either one bulk BU or many BUs. So you could say that in this  
> scenario as well multiple CoAs are changing at the same time.

hmm, don't know how many access network distribute multiple prefixes.

>
>> For example, WLAN and EVDO are different coverage and handover  
>> timing  is also different.
>> That's why we only support separate BUs.
>
> ==> By saying this do you also say that you only want to support  
> one CoA per interface?

No.

> I have been focusing on this subject in more general level and  
> thinking how this would work for the different scenarios described  
> in the Analysis of Multihoming in Mobile IPv6 draft (draft-ietf- 
> monami6-mipv6-analysis-00.txt). There you also have scenarios where  
> you have more than one CoA in one interface (for instance more than  
> one prefix in the access network).

The point is that the current CoA can handle this case without any  
problem.  The optimization to the protocol is important, but the  
overhead should be considered.
If the chance to optimization is rare, additional spec. for  
optimization leads just complexity to the protocol.

You scenario above is valid, but the point is how necessary we  
optimize this case.

>
>> The important aspect of bulk BU is that the address changes must  
>> be  happened at the same time. Otherwise, the MN shouldn't send  
>> BUs for  multiple CoAs.
>>
>
> ==> OK! I originally meant that the CoA1 and CoA2 are CoAs from the  
> same interface. So let me clarify my example. You have one HoA,  
> three CoAs and two interfaces. Two of the CoAs are from the same  
> interface. So even  when the CN or HA does not know based on the  
> CoAs or BIDs which address is from which MNs interface the BC would  
> look like this.
>
> BID1, HoA, CoA1 (WLAN)
> BID2, HoA, CoA2 (WLAN)
> BID3, HoA, CoA3 (EVDO)
>
> So now when your WLAN interface makes a handover from a link with  
> two prefixes to a link with only one prefix the CoA1 and CoA2 needs  
> to be "updated" to CoA4 which is now the new CoA of the WLAN  
> interface. In this case you can only reuse one of the BIDs (either  
> BID1 or BID2) for the CoA4 and you have to do something else to  
> remove the binding with the leftover BID. So this is why I make  
> such a fuss about this what if you have this many CoAs and they are  
> changed to this many CoAs. =) But OK, if you only want to support  
> one CoA per interface then this is no problem at all.
>
> My opinion is that you can't make the assumption that MNs are only  
> using one CoA per interface. At least, this assumption should be  
> clearly stated in the draft.

I didn't. My problem is whether this scenario is often happened or  
not. I think nobody knows at this point.

>
>>> One option could be for the MN to always add all the valid CoAs   
>>> into the BU message with lifetime 0 and when CN or HA receives  
>>> this  BU message it would
>> why lifetime zero?
>
> ==> =) I don't know, beats me (who wrote this?)! =) OK, I was  
> clearly thinking something else and writing something completely  
> different.
> My point which I tried to make (and clearly did not make) is that  
> when in a situation where you are replacing N bindings with N-M  
> (M>0) bindings you can't reuse all the BIDs and therefore you  
> cannot update all the BC entries. This is why you would need some  
> other means of removeing the bindings you don't need anymore and  
> updating them with the new ones and also leave the bindings still  
> valid (from different interfaces) in to the BC.

ok

>> No.
>> If MN has three CoAs, MN can send two BUs (a BU for CoA1 and a BU  
>> for  CoA2 and CoA3).
>
> ==> Hmmm... I don't understand this. Do you mean one BU for CoA1  
> and one for CoA2? Because the CoA3 should be left into the BC as it  
> is still valid because the EVDO interface did not move. Therefore,  
> no BUs should be sent with BID3 or how do you see this? So after  
> the update the binding cache should look like this, right.
>
> BID4, HoA, CoA4 (WLAN)
> BID3, HoA, CoA3 (EVDO)
>
> Now the BID4 could be BID1 or BID2 but one of these BC entries  
> needs to be removed by some other means.
>> deregistration and registration are occurred at once as same as  
>> MIP6.  i.e. Updating binding.
>
> ==> Actually I have to disagree here also. This is not always the  
> case!
>
> I think that there are three cases which need to be thought of:
>
> case 1:
> You have the same amount of CoA(s) in the new access network as you  
> had in the previous access network. In this case yes you can simply  
> update the binding and reuse the BID(s) for this. This is the same  
> as in MIP6 (RFC 3775). So no problem here! Other than the fact that  
> you need bulk registration to minimize the signaling overhead if  
> you have more than one CoA.
ok

> case 2:
> You have more CoAs in the new access network than you had in the  
> previous access network. In this case you can update the existing  
> bindings by reusing the BIDs and allocate new BID(s) for the  
> additional CoAs. So no problem here other that the possible  
> signaling overhead.

ok:-)

> case 3:
> You have less CoAs in the new access network than you had in the  
> previous access network. In this case you can only reuse some of  
> the BIDs to update the binding but have to have some mechanism to  
> remove the  not valid CoAs as well. So this case is the problem I'm  
> talking about.

I see.

>>> Do you or anybody have any thoughts about this?
>> I don't know if I understand your point
>
> ==> I hope you now see what I tried to explain in the original  
> mail? If you choose to only support one CoA per interface and this  
> is also WG's decision then I think this should also be stated in  
> the drafts which are writen for this WG.

I understood your problem, but I want to know how this optimization  
is important since this leads just small advantage with addition  
modification.

ryuji

> Best regards,
>
> Heikki Mahkonen
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 18 03:11:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVkNE-0004p4-It; Tue, 18 Apr 2006 03:11:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVkND-0004oz-5C
	for monami6@ietf.org; Tue, 18 Apr 2006 03:11:43 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVkNC-0001Ot-3Z
	for monami6@ietf.org; Tue, 18 Apr 2006 03:11:43 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9C4AE4F0001
	for <monami6@ietf.org>; Tue, 18 Apr 2006 09:11:40 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Apr 2006 09:11:40 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Apr 2006 09:11:39 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id DC7A029F5;
	Tue, 18 Apr 2006 10:11:39 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 98FDE95C6A;
	Tue, 18 Apr 2006 10:11:39 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 30FE195C4A;
	Tue, 18 Apr 2006 10:11:39 +0300 (EEST)
Message-ID: <4444912A.4030300@ericsson.com>
Date: Tue, 18 Apr 2006 10:11:38 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
References: <1487A357FD2ED544B8AD29E528FF9DF00205DE4B@NAEX06.na.qualcomm.com>
In-Reply-To: <1487A357FD2ED544B8AD29E528FF9DF00205DE4B@NAEX06.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 18 Apr 2006 07:11:39.0988 (UTC)
	FILETIME=[56B50940:01C662B7]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

teristic of a protocol.
> 
> => Ok, but can explain how this is different in this particular option
> from any other option? These extensions you refer to would be defined
> as suboptions so they're completely transparent to this option.

I was more thinking the case that someone would like to extend this 
particular suboption. Naturally defining a new suboption solves the 
case, but the reason why I'm thinking about the need to extend this 
particular suboption is that I'm trying to figure out is there something 
else needed besides the fields specified in the draft. This is of course 
only valid if all flow binding related fields should be inside the same 
suboption.

> => Please note that the option will always be aligned, i.e. if not 
> naturally, by padding.

Of course.

> I know there is 
> a tradeoff with simplicity here, but IMO it's more important to
> be radio efficient than to design for a simple implementation.
> At least from a job security view point :)

Well, tradeoffs are tricky...

> => I'm not sure if there is something that doesn't start
> on a natural boundary here. More below.

You are right. The only way I see is to make the flow label easier to 
handle as an integer would be to extend it to 32 bits (in this draft).

> => It looks aligned perfectly to me but it's wrong :) 

Oops, my mistake. :|

The flow field could be extended to 24 bits but naturally only 20 bits 
would be meaningful.

  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |        Flow Label                             |     Protocol  |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |     C. S.     |
  +-+-+-+-+-+-+-+-+

There would still be alignment issues (in the case some of the other 
fields would not be present) but at least the SPI field would be aligned 
correctly.

Extending the flow label field to 32 bits (still only using 20 bits, 
though) would also be something worth considering for:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            SPI                                |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            Flow Label                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Source port               |    Destination port           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|   Protocol    |     C. S.     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

It would surely waste 12 bits but would solve those alignment issues in 
the given format. A tradeoff :)

 > if you want this option you need to change RFC 2460 to make
 > the flow label 16 bits instead of 20 :(

Yep, we leave the RFC alone.

-- 
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 18 08:02:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVou8-0003Fi-CB; Tue, 18 Apr 2006 08:02:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVou6-0003FT-Pv
	for monami6@ietf.org; Tue, 18 Apr 2006 08:01:58 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVou5-0001im-Ay
	for monami6@ietf.org; Tue, 18 Apr 2006 08:01:58 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3IC1t87026257
	for <monami6@ietf.org>; Tue, 18 Apr 2006 15:01:55 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 26180-05 for <monami6@ietf.org>;
	Tue, 18 Apr 2006 15:01:53 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3IC1pGv026241
	for <monami6@ietf.org>; Tue, 18 Apr 2006 15:01:53 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: [Monami6] Any work going on merging the flow binding drafts?
Date: Tue, 18 Apr 2006 15:01:30 +0300
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604181501.31945.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

I read somewhere in this list that someone started to
merge the flow binding drafts into a single one since
they overlap each other quite much.
Is this work still ongoing or have plans changed since then?
So, basically, what is the state on 

<quote>
- A "Flow/binding policies exchange" solution for an exchange of
policies from the mobile host/router to the Home Agent and from the
Home Agent to the mobile host/router influencing the choice of the
Care-of Address and Home Agent address [Standard Track].
</quote>

?

Thanks
Gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 18 10:31:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVrES-0008EC-9m; Tue, 18 Apr 2006 10:31:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVrEQ-0008E7-HK
	for monami6@ietf.org; Tue, 18 Apr 2006 10:31:06 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVrEP-0002OI-4s
	for monami6@ietf.org; Tue, 18 Apr 2006 10:31:06 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3IEV3TI028009
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Tue, 18 Apr 2006 07:31:04 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k3IEV1kV023934
	for <monami6@ietf.org>; Tue, 18 Apr 2006 07:31:02 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Apr 2006 07:31:01 -0700
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: [Monami6] Any work going on merging the flow binding drafts?
Date: Tue, 18 Apr 2006 07:30:59 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF0022B61FC@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Any work going on merging the flow binding drafts?
Thread-Index: AcZi3+8DhlG848tjQfSiZ4lMdW6hWwAFKfBQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 18 Apr 2006 14:31:01.0087 (UTC)
	FILETIME=[B72586F0:01C662F4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org



 > I read somewhere in this list that someone started to
 > merge the flow binding drafts into a single one since
 > they overlap each other quite much.
 > Is this work still ongoing or have plans changed since then?

=3D> The plans have not changed, the merged draft is draft-soliman...

Hesham

 > So, basically, what is the state on=20
 >=20
 > <quote>
 > - A "Flow/binding policies exchange" solution for an exchange of
 > policies from the mobile host/router to the Home Agent and from the
 > Home Agent to the mobile host/router influencing the choice of the
 > Care-of Address and Home Agent address [Standard Track].
 > </quote>
 >=20
 > ?
 >=20
 > Thanks
 > Gabor
 >=20
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 >=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 18 11:23:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVs2z-0007WF-0a; Tue, 18 Apr 2006 11:23:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVs2x-0007Uj-47
	for monami6@ietf.org; Tue, 18 Apr 2006 11:23:19 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVs2v-0005Do-Mh
	for monami6@ietf.org; Tue, 18 Apr 2006 11:23:19 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3IFNGDB032765
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <monami6@ietf.org>; Tue, 18 Apr 2006 08:23:16 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3IFNFtU011952
	for <monami6@ietf.org>; Tue, 18 Apr 2006 08:23:16 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Apr 2006 08:23:15 -0700
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: [Monami6] Packet format: draft-soliman-monami6-flow-binding-00.txt
Date: Tue, 18 Apr 2006 08:23:13 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF0022B6271@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Packet format:
	draft-soliman-monami6-flow-binding-00.txt
Thread-Index: AcZit2toA/DqhHYiShyJkMH2kowNQgAQ/VGw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 18 Apr 2006 15:23:15.0662 (UTC)
	FILETIME=[037FB6E0:01C662FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


 > > =3D> Ok, but can explain how this is different in this=20
 > particular option
 > > from any other option? These extensions you refer to would=20
 > be defined
 > > as suboptions so they're completely transparent to this option.
 >=20
 > I was more thinking the case that someone would like to extend this=20
 > particular suboption.=20

=3D> ok, but s/suboption/option.

  Naturally defining a new suboption solves the=20
 > case, but the reason why I'm thinking about the need to extend this=20
 > particular suboption is that I'm trying to figure out is=20
 > there something=20
 > else needed besides the fields specified in the draft. This=20
 > is of course=20
 > only valid if all flow binding related fields should be=20
 > inside the same=20
 > suboption.

=3D> Well, I don't know of any other field used today but your point
is well taken. As I mentioned earlier, we can have a version field
to do what you're asking for.=20

 > > I know there is=20
 > > a tradeoff with simplicity here, but IMO it's more important to
 > > be radio efficient than to design for a simple implementation.
 > > At least from a job security view point :)
 >=20
 > Well, tradeoffs are tricky...

=3D> Engineering is tricky ;)

 > The flow field could be extended to 24 bits but naturally=20
 > only 20 bits=20
 > would be meaningful.
 >=20
 >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >   |        Flow Label                             |     Protocol  |
 >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >   |     C. S.     |
 >   +-+-+-+-+-+-+-+-+
 >=20
 > There would still be alignment issues (in the case some of the other=20
 > fields would not be present) but at least the SPI field=20
 > would be aligned=20
 > correctly.
 >=20
 > Extending the flow label field to 32 bits (still only using 20 bits,=20
 > though) would also be something worth considering for:
 >=20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 > |                            SPI                                |
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 > |                            Flow Label                         |
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 > |     Source port               |    Destination port           |
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 > |   Protocol    |     C. S.     |
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >=20
 > It would surely waste 12 bits but would solve those=20
 > alignment issues in=20
 > the given format. A tradeoff :)

=3D> I'm fine with either option, but since we're going to add a=20
possibility to define address ranges (a comment in Dallas), let's=20
add that first then decide whether it's better to represent this=20
as a 24 or 32 bits. Probabilistically speaking (only based on my gutt
feeling) The C.S. is unlikely to be there, so if we can fit the=20
Flow label and protocol in one word that would make sense IMO.=20

Hesham


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 18 22:16:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW2FI-0004do-NC; Tue, 18 Apr 2006 22:16:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW2FH-0004dj-CR
	for monami6@ietf.org; Tue, 18 Apr 2006 22:16:43 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW2FF-00064j-2X
	for monami6@ietf.org; Tue, 18 Apr 2006 22:16:43 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IXY003116I7ME@szxga03-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 10:20:31 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IXY00C8F6I713@szxga03-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 10:20:31 +0800 (CST)
Received: from l49442 ([10.70.67.114])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IXY00HM76Y9GS@szxml01-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 10:30:09 +0800 (CST)
Date: Wed, 19 Apr 2006 10:12:27 +0800
From: "Starry.Lin" <linjing@huawei.com>
Subject: RE: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
In-reply-to: <000401c65f96$f64555b0$af726e0a@china.huawei.com>
To: xiazhongqi@huawei.com
Message-id: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
Organization: HW
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

In my opinion, i think it's to say that some/all interfaces of a MN may have
the same HA and HoA. For instance, you can image a MN have both WLAN and
WCDMA interface, and the WLAN and WCDMA access services are both provided by
the same Operator. Thus the MN's interface on the WLAN and interface on the
WCDMA network may use the same HA and HoA provided by the same Operator. An
other scenario is that no matter how many access capabilities the MN has,
the Mobile IP, as a service, is provided by one operator.
Any way, the key point is that multiple interfaces only imply that the MN
has multiple CoA on each interface( if the interface is active), not the
HoA.


-----Original Message-----
From: Sam Xia [mailto:xiazhongqi@huawei.com] 
Sent: Friday, April 14, 2006 3:42 PM
To: monami6@ietf.org
Subject: [Monami6] a question about Analysis of Multihoming in Mobile IPv6


Hello, everyone,
          I am confused about a sentence in Analysis of Multihoming in
Mobile IPv6. 
The sentence is "The fact that a mobile node has multiple interfaces does
not 
imply that it has multiple HoAs and vice-versa" and located at the last
paragragh on page 10.
          I think one interface should have a corresponding address or more.
So, if a mobile node is in its home, each of its interfaces has a address at
least.

Anyone can give me the detailed explaination or a scenario? Thanks.



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 04:06:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW7hP-0001al-OP; Wed, 19 Apr 2006 04:06:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW7hP-0001ag-4t
	for monami6@ietf.org; Wed, 19 Apr 2006 04:06:07 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW7hN-00052e-Mu
	for monami6@ietf.org; Wed, 19 Apr 2006 04:06:07 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3J85tQ8003542; Wed, 19 Apr 2006 10:05:55 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3J85qZu003538; Wed, 19 Apr 2006 10:05:52 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3J85qBs017534
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Apr 2006 10:05:52 +0200
Message-ID: <4445EF03.7070904@enst-bretagne.fr>
Date: Wed, 19 Apr 2006 10:04:19 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

Starry.Lin wrote:

>In my opinion, i think it's to say that some/all interfaces of a MN may have
>the same HA and HoA. For instance, you can image a MN have both WLAN and
>WCDMA interface, and the WLAN and WCDMA access services are both provided by
>the same Operator. Thus the MN's interface on the WLAN and interface on the
>WCDMA network may use the same HA and HoA provided by the same Operator. An
>other scenario is that no matter how many access capabilities the MN has,
>the Mobile IP, as a service, is provided by one operator.
>Any way, the key point is that multiple interfaces only imply that the MN
>has multiple CoA on each interface( if the interface is active), not the
>HoA.
>  
>
This is a good interpretation of the sentence.
A MN may have multiple interfaces (possibly bound to multiple CoAs), and 
ony one HoA.

Nicolas

>
>-----Original Message-----
>From: Sam Xia [mailto:xiazhongqi@huawei.com] 
>Sent: Friday, April 14, 2006 3:42 PM
>To: monami6@ietf.org
>Subject: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
>
>
>Hello, everyone,
>          I am confused about a sentence in Analysis of Multihoming in
>Mobile IPv6. 
>The sentence is "The fact that a mobile node has multiple interfaces does
>not 
>imply that it has multiple HoAs and vice-versa" and located at the last
>paragragh on page 10.
>          I think one interface should have a corresponding address or more.
>So, if a mobile node is in its home, each of its interfaces has a address at
>least.
>
>Anyone can give me the detailed explaination or a scenario? Thanks.
>
>
>
>_______________________________________________
>Monami6 mailing list
>Monami6@ietf.org
>https://www1.ietf.org/mailman/listinfo/monami6
>
>
>_______________________________________________
>Monami6 mailing list
>Monami6@ietf.org
>https://www1.ietf.org/mailman/listinfo/monami6
>  
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 04:08:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW7je-0001fM-9i; Wed, 19 Apr 2006 04:08:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW7jc-0001fH-Lx
	for monami6@ietf.org; Wed, 19 Apr 2006 04:08:24 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW7ja-00058K-Nm
	for monami6@ietf.org; Wed, 19 Apr 2006 04:08:24 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 54904E28; 
	Wed, 19 Apr 2006 10:08:21 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 10:08:21 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 10:08:20 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id CF8C5236B;
	Wed, 19 Apr 2006 11:08:20 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 8880C95C6A;
	Wed, 19 Apr 2006 11:08:20 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 346F695C4A;
	Wed, 19 Apr 2006 11:08:20 +0300 (EEST)
Message-ID: <4445EFEC.9040100@ericsson.com>
Date: Wed, 19 Apr 2006 11:08:12 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 19 Apr 2006 08:08:21.0018 (UTC)
	FILETIME=[6C4AC7A0:01C66388]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Starry.Lin wrote:

> Any way, the key point is that multiple interfaces only imply that the MN
> has multiple CoA on each interface( if the interface is active), not the
> HoA.
>

I don't understand the part "multiple interfaces only imply that the MN 
has multiple CoAs on each interface". I think it should say "multiple 
(active) interfaces only imply that the MN has multiple CoAs. Each 
interface can have one or more CoAs (if the interface is active)." 
Moreover, the MN can have more than one HoA despite the number of 
interfaces (i.e. multihomed).

-- 
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 04:18:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW7tN-00035E-MQ; Wed, 19 Apr 2006 04:18:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW7tM-0002un-9A
	for monami6@ietf.org; Wed, 19 Apr 2006 04:18:28 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW7tK-0005YW-S0
	for monami6@ietf.org; Wed, 19 Apr 2006 04:18:28 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k3J8IMdD004292; Wed, 19 Apr 2006 10:18:22 +0200
Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr
	[192.44.77.3])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k3J8IIiT004280; Wed, 19 Apr 2006 10:18:18 +0200
Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0)
	by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k3J8II32017578
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Apr 2006 10:18:18 +0200
Message-ID: <4445F1ED.4080001@enst-bretagne.fr>
Date: Wed, 19 Apr 2006 10:16:45 +0200
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
	<4445EFEC.9040100@ericsson.com>
In-Reply-To: <4445EFEC.9040100@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Tero Kauppinen (JO/LMF) wrote:

> Starry.Lin wrote:
>
>> Any way, the key point is that multiple interfaces only imply that 
>> the MN
>> has multiple CoA on each interface( if the interface is active), not the
>> HoA.
>>
>
> I don't understand the part "multiple interfaces only imply that the 
> MN has multiple CoAs on each interface". I think it should say 
> "multiple (active) interfaces only imply that the MN has multiple CoAs.

Agree, but this is the text of Starry. Did you find something like this 
in the draft?

> Each interface can have one or more CoAs (if the interface is 
> active)." Moreover, the MN can have more than one HoA despite the 
> number of interfaces (i.e. multihomed).

This is what we wanted to say with the sentence mentioned in an earlier 
email:

"The fact that a mobile node has multiple interfaces does not imply that 
it has multiple HoAs and vice-versa"

Nicolas

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 04:26:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW81R-0006oU-Vu; Wed, 19 Apr 2006 04:26:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW81Q-0006oP-S7
	for monami6@ietf.org; Wed, 19 Apr 2006 04:26:48 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW81N-0005uN-2b
	for monami6@ietf.org; Wed, 19 Apr 2006 04:26:48 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4E1EC4F0002; Wed, 19 Apr 2006 10:26:44 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 10:26:44 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 10:26:43 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 73069236B;
	Wed, 19 Apr 2006 11:26:43 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3C37295C6A;
	Wed, 19 Apr 2006 11:26:43 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id D121C95C4A;
	Wed, 19 Apr 2006 11:26:42 +0300 (EEST)
Message-ID: <4445F43B.4020506@ericsson.com>
Date: Wed, 19 Apr 2006 11:26:35 +0300
From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02SpxAuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>	<4445EFEC.9040100@ericsson.com>
	<4445F1ED.4080001@enst-bretagne.fr>
In-Reply-To: <4445F1ED.4080001@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 19 Apr 2006 08:26:43.0581 (UTC)
	FILETIME=[FD788AD0:01C6638A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Nicolas Montavont wrote:
>> I don't understand the part "multiple interfaces only imply that the 
>> MN has multiple CoAs on each interface". I think it should say 
>> "multiple (active) interfaces only imply that the MN has multiple CoAs.
> 
> Agree, but this is the text of Starry. Did you find something like this 
> in the draft?

Nope, I was just referring to Starry's sentence.

> This is what we wanted to say with the sentence mentioned in an earlier 
> email:
> 
> "The fact that a mobile node has multiple interfaces does not imply that 
> it has multiple HoAs and vice-versa"
> 

Sure, I don't have problems in understanding the sentence, but maybe it 
should be written a little bit differently if some people find it 
confusing.

Cowardly escaping without posting a proposal...
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 05:15:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW8md-0000YY-V2; Wed, 19 Apr 2006 05:15:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW8mc-0000Wp-2k
	for monami6@ietf.org; Wed, 19 Apr 2006 05:15:34 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW8ma-00083r-7A
	for monami6@ietf.org; Wed, 19 Apr 2006 05:15:34 -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 <0IXY009QKPEFSL@szxga01-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 17:08:40 +0800 (CST)
Received: from huawei.com ([172.24.1.6])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IXY008RTPEFBW@szxga01-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 17:08:39 +0800 (CST)
Received: from l49442 ([10.70.67.114])
	by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IXY00LWDQ1EWO@szxml02-in.huawei.com> for
	monami6@ietf.org; Wed, 19 Apr 2006 17:22:26 +0800 (CST)
Date: Wed, 19 Apr 2006 17:08:26 +0800
From: "Starry.Lin" <linjing@huawei.com>
Subject: RE: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
In-reply-to: <4445EFEC.9040100@ericsson.com>
To: 'Monami6 WG' <monami6@ietf.org>
Message-id: <000201c66390$d18f0790$7243460a@china.huawei.com>
Organization: HW
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Thanks Tero's comments. I agree that his expression is more exactly. Each
interface can have more than one CoA(also in most condition, there is one).
And what's more, the MN can have more than one HoA if there are more than
one prefix on the link, even if the MN is not multihoming.



-----Original Message-----
From: Tero Kauppinen (JO/LMF) [mailto:tero.kauppinen@ericsson.com] 
Sent: Wednesday, April 19, 2006 4:08 PM
To: Monami6 WG
Cc: xiazhongqi@huawei.com
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile
IPv6


Starry.Lin wrote:

> Any way, the key point is that multiple interfaces only imply that the MN
> has multiple CoA on each interface( if the interface is active), not the
> HoA.
>

I don't understand the part "multiple interfaces only imply that the MN 
has multiple CoAs on each interface". I think it should say "multiple 
(active) interfaces only imply that the MN has multiple CoAs. Each 
interface can have one or more CoAs (if the interface is active)." 
Moreover, the MN can have more than one HoA despite the number of 
interfaces (i.e. multihomed).

-- 
Tero

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 14:31:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWHSg-0007BR-Cg; Wed, 19 Apr 2006 14:31:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWHSe-0007BM-TH
	for monami6@ietf.org; Wed, 19 Apr 2006 14:31:32 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWHSd-0000JG-Ec
	for monami6@ietf.org; Wed, 19 Apr 2006 14:31:32 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3JIVND8024515
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Apr 2006 11:31:24 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3JIUk66019359; Wed, 19 Apr 2006 11:31:22 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 11:30:59 -0700
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: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Wed, 19 Apr 2006 11:30:57 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00233C4E4@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Thread-Index: AcZjV1iphgvfZG41SL64c7q1IpuErAAh8VZw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>, <xiazhongqi@huawei.com>
X-OriginalArrivalTime: 19 Apr 2006 18:30:59.0420 (UTC)
	FILETIME=[67A289C0:01C663DF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

=20
 >=20
 > In my opinion, i think it's to say that some/all interfaces=20
 > of a MN may have
 > the same HA and HoA. For instance, you can image a MN have=20
 > both WLAN and
 > WCDMA interface, and the WLAN and WCDMA access services are=20
 > both provided by
 > the same Operator. Thus the MN's interface on the WLAN and=20
 > interface on the
 > WCDMA network may use the same HA and HoA provided by the=20
 > same Operator.=20

=3D> Correction, there is no link between the operator and the HoA
or the HA. whether different access networks belong to the same operator
or not, is not relevant to the number of HoAs that a MN might have.=20

To answer the original question, IPv6 allows any node to have multiple
addresses and associate them with the same interface. So whether the MN
has one HoA or several makes no statement about the number of interfaces

that it has.=20

Hesham




An
 > other scenario is that no matter how many access=20
 > capabilities the MN has,
 > the Mobile IP, as a service, is provided by one operator.
 > Any way, the key point is that multiple interfaces only=20
 > imply that the MN
 > has multiple CoA on each interface( if the interface is=20
 > active), not the
 > HoA.
 >=20
 >=20
 > -----Original Message-----
 > From: Sam Xia [mailto:xiazhongqi@huawei.com]=20
 > Sent: Friday, April 14, 2006 3:42 PM
 > To: monami6@ietf.org
 > Subject: [Monami6] a question about Analysis of Multihoming=20
 > in Mobile IPv6
 >=20
 >=20
 > Hello, everyone,
 >           I am confused about a sentence in Analysis of=20
 > Multihoming in
 > Mobile IPv6.=20
 > The sentence is "The fact that a mobile node has multiple=20
 > interfaces does
 > not=20
 > imply that it has multiple HoAs and vice-versa" and located=20
 > at the last
 > paragragh on page 10.
 >           I think one interface should have a corresponding=20
 > address or more.
 > So, if a mobile node is in its home, each of its interfaces=20
 > has a address at
 > least.
 >=20
 > Anyone can give me the detailed explaination or a scenario? Thanks.
 >=20
 >=20
 >=20
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 >=20
 >=20
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 >=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 16:45:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWJXc-0007Dk-6D; Wed, 19 Apr 2006 16:44:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWJXa-00077e-GV
	for monami6@ietf.org; Wed, 19 Apr 2006 16:44:46 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWJXa-0007de-EE
	for monami6@ietf.org; Wed, 19 Apr 2006 16:44:46 -0400
Received: from smtp02.uc3m.es ([163.117.136.122])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FWJGc-0000z8-Cf
	for monami6@ietf.org; Wed, 19 Apr 2006 16:27:17 -0400
Received: from smtp02.uc3m.es (localhost [127.0.0.1])
	by localhost.uc3m.es (Postfix) with ESMTP
	id CE947950F6; Wed, 19 Apr 2006 22:27:12 +0200 (CEST)
Received: from [163.117.203.112] (unknown [163.117.203.112])
	by smtp02.uc3m.es (Postfix) with ESMTP
	id 2E459950D3; Wed, 19 Apr 2006 22:27:12 +0200 (CEST)
In-Reply-To: <1487A357FD2ED544B8AD29E528FF9DF00233C4E4@NAEX06.na.qualcomm.com>
References: <1487A357FD2ED544B8AD29E528FF9DF00233C4E4@NAEX06.na.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <6edcffe5eae308297ac945bd8a3957ce@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Wed, 19 Apr 2006 23:27:11 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Hesham,


El 19/04/2006, a las 21:30, Soliman, Hesham escribi=F3:

>
>>
>> In my opinion, i think it's to say that some/all interfaces
>> of a MN may have
>> the same HA and HoA. For instance, you can image a MN have
>> both WLAN and
>> WCDMA interface, and the WLAN and WCDMA access services are
>> both provided by
>> the same Operator. Thus the MN's interface on the WLAN and
>> interface on the
>> WCDMA network may use the same HA and HoA provided by the
>> same Operator.
>
> =3D> Correction, there is no link between the operator and the HoA
> or the HA. whether different access networks belong to the same=20
> operator
> or not, is not relevant to the number of HoAs that a MN might have.
>

agree, multiple operators in the access network don't affect the number=20=

of hoas

but, if a MN has multiple HAs served by different ISPs, then it must=20
have multiple HoAs, right?

(this would be so, because since it would have different HAs, in=20
different Home Networks and since they are served by differetn ISPs,=20
they need to use differetn PA blocks)

In other words, the operator of the access netwrok has no influence in=20=

the number of Hoas, but the ISPs of the HAs/Home networks has a direct=20=

impact in the number of HoAs, agree?


> To answer the original question, IPv6 allows any node to have multiple
> addresses and associate them with the same interface. So whether the =
MN
> has one HoA or several makes no statement about the number of=20
> interfaces
>
> that it has.
>

indeed, there are other combinations, where there is a single ISP=20
serving all the HAs, that may result in multiple HoAs for other=20
reasons...

regards, marcelo


> Hesham
>
>
>
>
> An
>> other scenario is that no matter how many access
>> capabilities the MN has,
>> the Mobile IP, as a service, is provided by one operator.
>> Any way, the key point is that multiple interfaces only
>> imply that the MN
>> has multiple CoA on each interface( if the interface is
>> active), not the
>> HoA.
>>
>>
>> -----Original Message-----
>> From: Sam Xia [mailto:xiazhongqi@huawei.com]
>> Sent: Friday, April 14, 2006 3:42 PM
>> To: monami6@ietf.org
>> Subject: [Monami6] a question about Analysis of Multihoming
>> in Mobile IPv6
>>
>>
>> Hello, everyone,
>>           I am confused about a sentence in Analysis of
>> Multihoming in
>> Mobile IPv6.
>> The sentence is "The fact that a mobile node has multiple
>> interfaces does
>> not
>> imply that it has multiple HoAs and vice-versa" and located
>> at the last
>> paragragh on page 10.
>>           I think one interface should have a corresponding
>> address or more.
>> So, if a mobile node is in its home, each of its interfaces
>> has a address at
>> least.
>>
>> Anyone can give me the detailed explaination or a scenario? Thanks.
>>
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 16:47:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWJaK-0008VY-1K; Wed, 19 Apr 2006 16:47:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWJaJ-0008VT-8s
	for monami6@ietf.org; Wed, 19 Apr 2006 16:47:35 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWJaI-0007nP-TX
	for monami6@ietf.org; Wed, 19 Apr 2006 16:47:35 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3JKlGah016087
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Apr 2006 13:47:17 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k3JKlB0E020664; Wed, 19 Apr 2006 13:47:15 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Apr 2006 13:47:14 -0700
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: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Wed, 19 Apr 2006 13:47:11 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF00233C693@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Thread-Index: AcZj8i3k7/awTc6gRzyHtfDIV36OgwAABe5w
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Monami6 WG" <monami6@ietf.org>
X-OriginalArrivalTime: 19 Apr 2006 20:47:14.0150 (UTC)
	FILETIME=[70275860:01C663F2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


 > but, if a MN has multiple HAs served by different ISPs, then it must=20
 > have multiple HoAs, right?

=3D> sure.

 > In other words, the operator of the access netwrok has no=20
 > influence in=20
 > the number of Hoas, but the ISPs of the HAs/Home networks=20
 > has a direct=20
 > impact in the number of HoAs, agree?

=3D> Yes.=20

 >=20
 > indeed, there are other combinations, where there is a single ISP=20
 > serving all the HAs, that may result in multiple HoAs for other=20
 > reasons...

=3D> Agreed. That was easy :)

Hesham

 >=20
 > regards, marcelo
 >=20
 >=20
 > > Hesham
 > >
 > >
 > >
 > >
 > > An
 > >> other scenario is that no matter how many access
 > >> capabilities the MN has,
 > >> the Mobile IP, as a service, is provided by one operator.
 > >> Any way, the key point is that multiple interfaces only
 > >> imply that the MN
 > >> has multiple CoA on each interface( if the interface is
 > >> active), not the
 > >> HoA.
 > >>
 > >>
 > >> -----Original Message-----
 > >> From: Sam Xia [mailto:xiazhongqi@huawei.com]
 > >> Sent: Friday, April 14, 2006 3:42 PM
 > >> To: monami6@ietf.org
 > >> Subject: [Monami6] a question about Analysis of Multihoming
 > >> in Mobile IPv6
 > >>
 > >>
 > >> Hello, everyone,
 > >>           I am confused about a sentence in Analysis of
 > >> Multihoming in
 > >> Mobile IPv6.
 > >> The sentence is "The fact that a mobile node has multiple
 > >> interfaces does
 > >> not
 > >> imply that it has multiple HoAs and vice-versa" and located
 > >> at the last
 > >> paragragh on page 10.
 > >>           I think one interface should have a corresponding
 > >> address or more.
 > >> So, if a mobile node is in its home, each of its interfaces
 > >> has a address at
 > >> least.
 > >>
 > >> Anyone can give me the detailed explaination or a=20
 > scenario? Thanks.
 > >>
 > >>
 > >>
 > >> _______________________________________________
 > >> Monami6 mailing list
 > >> Monami6@ietf.org
 > >> https://www1.ietf.org/mailman/listinfo/monami6
 > >>
 > >>
 > >> _______________________________________________
 > >> Monami6 mailing list
 > >> Monami6@ietf.org
 > >> https://www1.ietf.org/mailman/listinfo/monami6
 > >>
 > >
 > > _______________________________________________
 > > Monami6 mailing list
 > > Monami6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/monami6
 > >
 >=20
 >=20
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 >=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 22:03:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWOW5-0000ok-Ie; Wed, 19 Apr 2006 22:03:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWOW4-0000ob-Qs
	for monami6@ietf.org; Wed, 19 Apr 2006 22:03:32 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWOW1-0006Os-25
	for monami6@ietf.org; Wed, 19 Apr 2006 22:03:32 -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 <0IY000B620CMK7@szxga01-in.huawei.com> for
	monami6@ietf.org; Thu, 20 Apr 2006 10:02:46 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IY0002S40CLJ1@szxga01-in.huawei.com> for
	monami6@ietf.org; Thu, 20 Apr 2006 10:02:46 +0800 (CST)
Received: from x49105 ([10.110.114.175])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IY00045115JJL@szxml01-in.huawei.com> for
	monami6@ietf.org; Thu, 20 Apr 2006 10:20:15 +0800 (CST)
Date: Thu, 20 Apr 2006 10:02:23 +0800
From: Sam Xia <xiazhongqi@huawei.com>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
In-reply-to: <E1FWF6L-0001lC-4b@megatron.ietf.org>
To: monami6@ietf.org
Message-id: <000001c6641e$7a098ac0$af726e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 715d0e6950aaebd45af78ef9318d0186
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi, all,
     Unitl now, I understand the meaning of the sentence for "The fact that
a mobile node has multiple interfaces does not imply that it has multiple
HoAs and vice-versa". But I have some other questions about this.
     In general, it is universal that multiple interfaces share the same one
address or more. But IMHO, the prerequisite is that the multiple interfaces
have the same the attributes about L1 and  L2. For example, as to ethernet
switch (including Cisco, 3Com, Huawei), multiple ethernet interfaces in the
same VLAN share the same IP address(s). I have not seen the fact that
different types of interfaces share the same IP address (I don't think it is
a good idea to have POS interface and ATM interface, or T1/C1 interface and
ethernet interface, or WCDMA interface and WLAN interface share the same IP
address). Can anyone give me the example for this? 
     As a matter of fact, if we do so like this, we will face many issues of
implementing aspect. For example, if different interfaces share the ip
address, then upper layer application will find it difficult to determine
the specific interface from which the packet should be sent. It is because
upper layer application can not specify the outbound interface based on the
service access points(i.e., socket) provided by TCP/UDP. 
    That's all. Thank you for your kind reply.


> -----Original Message-----
> From: monami6-request@ietf.org [mailto:monami6-request@ietf.org] 
> Sent: Thursday, April 20, 2006 12:00 AM
> To: monami6@ietf.org
> Subject: Monami6 Digest, Vol 14, Issue 17
> 
> 
> Send Monami6 mailing list submissions to
> 	monami6@ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www1.ietf.org/mailman/listinfo/monami6
> or, via email, send a message with subject or body 'help' to
> 	monami6-request@ietf.org
> 
> You can reach the person managing the list at
> 	monami6-owner@ietf.org
> 
> When replying, please edit your Subject line so it is more 
> specific than "Re: Contents of Monami6 digest..."
> 
> 
> Today's Topics:
> 
>    1. RE: a question about Analysis of Multihoming in Mobile IPv6
>       (Starry.Lin)
>    2. Re: a question about Analysis of Multihoming in Mobile IPv6
>       (Nicolas Montavont)
>    3. Re: a question about Analysis of Multihoming in Mobile IPv6
>       (Tero Kauppinen (JO/LMF))
>    4. Re: a question about Analysis of Multihoming in Mobile IPv6
>       (Nicolas Montavont)
>    5. Re: a question about Analysis of Multihoming in Mobile IPv6
>       (Tero Kauppinen (JO/LMF))
>    6. RE: a question about Analysis of Multihoming in Mobile IPv6
>       (Starry.Lin)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 19 Apr 2006 10:12:27 +0800
> From: "Starry.Lin" <linjing@huawei.com>
> Subject: RE: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: xiazhongqi@huawei.com
> Cc: 'Monami6 WG' <monami6@ietf.org>
> Message-ID:
> 	
> <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02Spx
> AuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
> 	
> Content-Type: text/plain; charset=us-ascii
> 
> In my opinion, i think it's to say that some/all interfaces 
> of a MN may have the same HA and HoA. For instance, you can 
> image a MN have both WLAN and WCDMA interface, and the WLAN 
> and WCDMA access services are both provided by the same 
> Operator. Thus the MN's interface on the WLAN and interface 
> on the WCDMA network may use the same HA and HoA provided by 
> the same Operator. An other scenario is that no matter how 
> many access capabilities the MN has, the Mobile IP, as a 
> service, is provided by one operator. Any way, the key point 
> is that multiple interfaces only imply that the MN has 
> multiple CoA on each interface( if the interface is active), 
> not the HoA.
> 
> 
> -----Original Message-----
> From: Sam Xia [mailto:xiazhongqi@huawei.com] 
> Sent: Friday, April 14, 2006 3:42 PM
> To: monami6@ietf.org
> Subject: [Monami6] a question about Analysis of Multihoming 
> in Mobile IPv6
> 
> 
> Hello, everyone,
>           I am confused about a sentence in Analysis of 
> Multihoming in Mobile IPv6. 
> The sentence is "The fact that a mobile node has multiple 
> interfaces does not 
> imply that it has multiple HoAs and vice-versa" and located 
> at the last paragragh on page 10.
>           I think one interface should have a corresponding 
> address or more. So, if a mobile node is in its home, each of 
> its interfaces has a address at least.
> 
> Anyone can give me the detailed explaination or a scenario? Thanks.
> 
> 
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 19 Apr 2006 10:04:19 +0200
> From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
> Subject: Re: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: Monami6 WG <monami6@ietf.org>
> Cc: xiazhongqi@huawei.com
> Message-ID: <4445EF03.7070904@enst-bretagne.fr>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hi,
> 
> Starry.Lin wrote:
> 
> >In my opinion, i think it's to say that some/all interfaces 
> of a MN may 
> >have the same HA and HoA. For instance, you can image a MN have both 
> >WLAN and WCDMA interface, and the WLAN and WCDMA access services are 
> >both provided by the same Operator. Thus the MN's interface 
> on the WLAN 
> >and interface on the WCDMA network may use the same HA and 
> HoA provided 
> >by the same Operator. An other scenario is that no matter how many 
> >access capabilities the MN has, the Mobile IP, as a service, is 
> >provided by one operator. Any way, the key point is that multiple 
> >interfaces only imply that the MN has multiple CoA on each 
> interface( 
> >if the interface is active), not the HoA.
> >  
> >
> This is a good interpretation of the sentence.
> A MN may have multiple interfaces (possibly bound to multiple 
> CoAs), and 
> ony one HoA.
> 
> Nicolas
> 
> >
> >-----Original Message-----
> >From: Sam Xia [mailto:xiazhongqi@huawei.com]
> >Sent: Friday, April 14, 2006 3:42 PM
> >To: monami6@ietf.org
> >Subject: [Monami6] a question about Analysis of Multihoming 
> in Mobile IPv6
> >
> >
> >Hello, everyone,
> >          I am confused about a sentence in Analysis of 
> Multihoming in 
> >Mobile IPv6. The sentence is "The fact that a mobile node 
> has multiple 
> >interfaces does not
> >imply that it has multiple HoAs and vice-versa" and located 
> at the last
> >paragragh on page 10.
> >          I think one interface should have a corresponding 
> address or more.
> >So, if a mobile node is in its home, each of its interfaces 
> has a address at
> >least.
> >
> >Anyone can give me the detailed explaination or a scenario? Thanks.
> >
> >
> >
> >_______________________________________________
> >Monami6 mailing list
> >Monami6@ietf.org https://www1.ietf.org/mailman/listinfo/monami6
> >
> >
> >_______________________________________________
> >Monami6 mailing list
> >Monami6@ietf.org https://www1.ietf.org/mailman/listinfo/monami6
> >  
> >
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Wed, 19 Apr 2006 11:08:12 +0300
> From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
> Subject: Re: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: Monami6 WG <monami6@ietf.org>
> Cc: xiazhongqi@huawei.com
> Message-ID: <4445EFEC.9040100@ericsson.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Starry.Lin wrote:
> 
> > Any way, the key point is that multiple interfaces only 
> imply that the 
> > MN has multiple CoA on each interface( if the interface is active), 
> > not the HoA.
> >
> 
> I don't understand the part "multiple interfaces only imply 
> that the MN 
> has multiple CoAs on each interface". I think it should say "multiple 
> (active) interfaces only imply that the MN has multiple CoAs. Each 
> interface can have one or more CoAs (if the interface is active)." 
> Moreover, the MN can have more than one HoA despite the number of 
> interfaces (i.e. multihomed).
> 
> -- 
> Tero
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 19 Apr 2006 10:16:45 +0200
> From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
> Subject: Re: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: Monami6 WG <monami6@ietf.org>
> Cc: xiazhongqi@huawei.com
> Message-ID: <4445F1ED.4080001@enst-bretagne.fr>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Tero Kauppinen (JO/LMF) wrote:
> 
> > Starry.Lin wrote:
> >
> >> Any way, the key point is that multiple interfaces only imply that
> >> the MN
> >> has multiple CoA on each interface( if the interface is 
> active), not the
> >> HoA.
> >>
> >
> > I don't understand the part "multiple interfaces only imply that the
> > MN has multiple CoAs on each interface". I think it should say 
> > "multiple (active) interfaces only imply that the MN has 
> multiple CoAs.
> 
> Agree, but this is the text of Starry. Did you find something 
> like this 
> in the draft?
> 
> > Each interface can have one or more CoAs (if the interface is
> > active)." Moreover, the MN can have more than one HoA despite the 
> > number of interfaces (i.e. multihomed).
> 
> This is what we wanted to say with the sentence mentioned in 
> an earlier 
> email:
> 
> "The fact that a mobile node has multiple interfaces does not 
> imply that 
> it has multiple HoAs and vice-versa"
> 
> Nicolas
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 19 Apr 2006 11:26:35 +0300
> From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
> Subject: Re: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: Monami6 WG <monami6@ietf.org>
> Cc: xiazhongqi@huawei.com
> Message-ID: <4445F43B.4020506@ericsson.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Nicolas Montavont wrote:
> >> I don't understand the part "multiple interfaces only 
> imply that the
> >> MN has multiple CoAs on each interface". I think it should say 
> >> "multiple (active) interfaces only imply that the MN has 
> multiple CoAs.
> > 
> > Agree, but this is the text of Starry. Did you find something like 
> > this
> > in the draft?
> 
> Nope, I was just referring to Starry's sentence.
> 
> > This is what we wanted to say with the sentence mentioned in an 
> > earlier
> > email:
> > 
> > "The fact that a mobile node has multiple interfaces does not imply 
> > that
> > it has multiple HoAs and vice-versa"
> > 
> 
> Sure, I don't have problems in understanding the sentence, 
> but maybe it 
> should be written a little bit differently if some people find it 
> confusing.
> 
> Cowardly escaping without posting a proposal...
> Tero
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Wed, 19 Apr 2006 17:08:26 +0800
> From: "Starry.Lin" <linjing@huawei.com>
> Subject: RE: [Monami6] a question about Analysis of Multihoming in
> 	Mobile IPv6
> To: 'Monami6 WG' <monami6@ietf.org>
> Cc: xiazhongqi@huawei.com
> Message-ID: <000201c66390$d18f0790$7243460a@china.huawei.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Thanks Tero's comments. I agree that his expression is more 
> exactly. Each interface can have more than one CoA(also in 
> most condition, there is one). And what's more, the MN can 
> have more than one HoA if there are more than one prefix on 
> the link, even if the MN is not multihoming.
> 
> 
> 
> -----Original Message-----
> From: Tero Kauppinen (JO/LMF) [mailto:tero.kauppinen@ericsson.com] 
> Sent: Wednesday, April 19, 2006 4:08 PM
> To: Monami6 WG
> Cc: xiazhongqi@huawei.com
> Subject: Re: [Monami6] a question about Analysis of 
> Multihoming in Mobile IPv6
> 
> 
> Starry.Lin wrote:
> 
> > Any way, the key point is that multiple interfaces only 
> imply that the 
> > MN has multiple CoA on each interface( if the interface is active), 
> > not the HoA.
> >
> 
> I don't understand the part "multiple interfaces only imply 
> that the MN 
> has multiple CoAs on each interface". I think it should say "multiple 
> (active) interfaces only imply that the MN has multiple CoAs. Each 
> interface can have one or more CoAs (if the interface is active)." 
> Moreover, the MN can have more than one HoA despite the number of 
> interfaces (i.e. multihomed).
> 
> -- 
> Tero
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 
> 
> End of Monami6 Digest, Vol 14, Issue 17
> ***************************************
> 



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 19 23:04:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWPTK-0007zw-Nz; Wed, 19 Apr 2006 23:04:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWPTJ-0007zo-FM
	for monami6@ietf.org; Wed, 19 Apr 2006 23:04:45 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWPTI-0001WX-2B
	for monami6@ietf.org; Wed, 19 Apr 2006 23:04:45 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k3K31xLT020139; Thu, 20 Apr 2006 06:01:59 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 06:04:32 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 06:04:32 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Thu, 20 Apr 2006 06:04:31 +0300
Message-ID: <615BD9B54CB01B41838C323DB9E91AAB407550@esebe100.NOE.Nokia.com>
In-Reply-To: <6edcffe5eae308297ac945bd8a3957ce@it.uc3m.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Thread-Index: AcZj8iydUgeGvZ7yTg+dkx80ieB2NwANMuXQ
From: <john.loughney@nokia.com>
To: <monami6@ietf.org>
X-OriginalArrivalTime: 20 Apr 2006 03:04:32.0812 (UTC)
	FILETIME=[25D906C0:01C66427]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: xiazhongqi@huawei.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Marcelo,


>but, if a MN has multiple HAs served by different ISPs, then it must=20
>have multiple HoAs, right?
>
>(this would be so, because since it would have different HAs, in=20
>different Home Networks and since they are served by differetn ISPs,=20
>they need to use differetn PA blocks)
>
>In other words, the operator of the access netwrok has no influence in=20
>the number of Hoas, but the ISPs of the HAs/Home networks has a direct=20
>impact in the number of HoAs, agree?

I essentially agree with this, with one small comment.  There probably
be some aggregators who provide a HA, aggregating a number of ISPs.

John

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 20 03:36:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWThv-0002lz-JW; Thu, 20 Apr 2006 03:36:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWThu-0002lp-AU
	for monami6@ietf.org; Thu, 20 Apr 2006 03:36:06 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWTht-0006Ki-0w
	for monami6@ietf.org; Thu, 20 Apr 2006 03:36:06 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 1BE72212C59
	for <monami6@ietf.org>; Thu, 20 Apr 2006 10:36:04 +0300 (EEST)
Received: from [193.234.219.40] (n40.nomadiclab.com [193.234.219.40])
	by n2.nomadiclab.com (Postfix) with ESMTP id AB41E212C44
	for <monami6@ietf.org>; Thu, 20 Apr 2006 10:36:03 +0300 (EEST)
Message-ID: <444739DC.7040403@iki.fi>
Date: Thu, 20 Apr 2006 10:35:56 +0300
From: Martti Kuparinen <martti.kuparinen@iki.fi>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: monami6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [Monami6] Why we really need bulk registration
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

We have just submitted the following draft. The link below is not a permanent
link and will disappear as soon as the draft appears on the official I-D pages...

http://users.piuha.net/martti/tmp/draft-kuparinen-monami6-mcoa-performance-00.txt

Martti

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 20 04:02:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWU7m-0002Dt-Lg; Thu, 20 Apr 2006 04:02:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWU73-0001em-OM
	for monami6@ietf.org; Thu, 20 Apr 2006 04:02:05 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWTsC-0006cu-6K
	for monami6@ietf.org; Thu, 20 Apr 2006 03:46:44 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 83111212C59
	for <monami6@ietf.org>; Thu, 20 Apr 2006 10:46:43 +0300 (EEST)
Received: from [193.234.219.40] (n40.nomadiclab.com [193.234.219.40])
	by n2.nomadiclab.com (Postfix) with ESMTP id 1877B212C44
	for <monami6@ietf.org>; Thu, 20 Apr 2006 10:46:43 +0300 (EEST)
Message-ID: <44473C5B.1010307@iki.fi>
Date: Thu, 20 Apr 2006 10:46:35 +0300
From: Martti Kuparinen <martti.kuparinen@iki.fi>
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Why we really need bulk registration
References: <444739DC.7040403@iki.fi>
In-Reply-To: <444739DC.7040403@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

When you read the numbers keep in mind that from a MN's point of view it's only
few bytes which can be saved, but from a large-scale operator's point of view
45% savings in signalling data makes a HUGE difference...

Martti

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Apr 20 21:53:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWkpO-0003kw-R5; Thu, 20 Apr 2006 21:52:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWkpN-0003km-Tb
	for monami6@ietf.org; Thu, 20 Apr 2006 21:52:57 -0400
Received: from f.csce.kyushu-u.ac.jp ([133.5.33.1])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FWkpL-0006co-9D
	for monami6@ietf.org; Thu, 20 Apr 2006 21:52:57 -0400
Received: (qmail 14203 invoked from network); 21 Apr 2006 01:46:13 -0000
Received: from unknown (HELO ?172.17.3.211?) (192.168.77.254)
	by 192.168.77.101 with SMTP; 21 Apr 2006 01:46:13 -0000
Date: Fri, 21 Apr 2006 10:46:13 +0900
From: Teruaki Kitasuka <kitasuka@f.csce.kyushu-u.ac.jp>
To: manet@ietf.org, mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org,
	monami6@ietf.org, nemo@ietf.org
Message-Id: <20060421104311.4A52.KITASUKA@f.csce.kyushu-u.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: 
Subject: [Monami6] Extended Deadline - CfP - 3rd Int. Conf. on Mobile
	Computing and Ubiquitous Networking (ICMU2006) at London, UK
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

(Apologies if you receive multiple copies of this message)

            !!!! Extended Deadline to May 9, ICMU2006 !!!!

========================================================================
                     C A L L   F O R   P A P E R S 
========================================================================

The Third International Conference on
Mobile Computing and Ubiquitous Networking (ICMU2006)

October 11-13, 2006
BCS London Office, London, UK
http://www.icmu.org/icmu2006/

Sponsored by:
  IPSJ SIG-MBL (Information Processing Society of Japan,
  Special Interest Group of Mobile Computing and Ubiquitous Networking)
Technically co-sponsored by:
  BCS (British Computer Society),
  IEE (Institution of Electrical Engineers), and
  IEEE ITS Society, Technical Committee on Mobile Communications &
  Applications
Supported by:
  ICF (International Communications Foundation) and
  SCAT (Support Center for Advanced Telecommunications Technology
  Research, Foundation)

SCOPE:

Mobile computing aims at ubiquitous user access to computer application.
To make it possible, networking technology
which enables Internet access anytime and everywhere,
i.e. ubiquitous networking is necessary. It is obvious that with the
accelerating trends towards mobile networks, ad-hoc networks,
and wireless networks, mobile computing and ubiquitous
networking will play an important role in future network.
This conference is aimed at providing researchers and practitioners
in this hot research area a forum for discussion and collaboration.
Authors are invited to submit papers addressing, but not
limited to, the following topics:

- Network management for ubiquitous networking 
- Data management for mobile computing
- Mobile device management 
- Performance evaluation for mobile computing and
 ubiquitous networking systems 
- Broadcast communications 
- Network architectures, protocols, or service models
 for ubiquitous networking 
- Security in mobile computing and ubiquitous networking 
- Mobile OS
- Wireless and mobile communications
- 4G wireless communications
- Mobile Internetworking 
- Ad-hoc networks
- Network mobility
- Mesh networks
- Sensor networks 
- Location-based services 

SUBMISSION INSTRUCTIONS:

Papers are solicited as full papers of no more than 8 pages,
each of which will be subject to a full review process.
Submission should already follow the author guidelines as specified
in the web site below.
An electronic, PDF-based submission of papers is mandatory.

Please check the web site of the conference
http://www.icmu.org/icmu2006/
for further submission instructions.

After the conference, a selected number of papers will be published
as special issues in IPSJ journal and IPSJ Digital Courier.
Please check the web site of IPSJ
http://www.ipsj.or.jp/08editt/dc/index.html
for the details of IPSJ Digital Coulier.


IMPORTANT DATES:

##########################################################
#        Deadline for submissions : May 9, 2006          #
#        Notification of acceptance: July 8, 2006        #
#        Camera ready due: July 31, 2006                 #
##########################################################


ORGANIZING COMMITTEE:

General Chair:
  Chai-Keong Toh (Queen Mary University of London, UK)
 
Technical Program Committee Co-Chairs:
  Susumu Ishihara (Shizuoka University, Japan)
  Eiji Kamioka (National Institute of Informatics, Japan)
 
Publication Co-Chairs:
  Gen Kitagata (Tohoku University, Japan)
  Yang Yang (University College London, UK)
 
Publicity Co-Chairs:
  Teruaki Kitasuka (Kyushu University, Japan)
  Kun Yang (University of Essex, UK)
 
Local Arrangement Chair:
  David Martland (Kingston University London, UK)
  Hiroshi Mineno (Shizuoka University, Japan)
 
Treasurers:
  David Martland (Kingston University London, UK)
  Tomohiko Yagyu (NEC, Japan)
 
Registration Co-Chairs:
  Jindong Hou (France Telecom, UK)
  Homare Murakami (NICT, Japan)

ICMU STEERING COMMITTEE:

  Tadanori Mizuno (Shizuoka University, Japan)
  Osamu Takahashi (Future University-Hakodate, Japan)
  Takashi Watanabe (Shizuoka University, Japan)
  Miki Yamamoto (Kansai University, Japan)


TECHNICAL PROGRAM COMMITTEE:

Mohammed Atiquzzaman (University of Oklahoma, USA)
Xiuzhen Cheng (George Washington University, USA)
We Duke Cho (Ajou University, Korea)
John Gardiner (Bradford University, UK)
Teruo Higashino (Osaka University, Japan)
Choong Seon Hong (Kyung Hee University, Korea)
Russell Hsing (Telcordia Technologies, USA)
Chung Ming Huang (National Cheng Kung University, Taiwan)
Joseph Hui (Arizona State University, USA)
Masugi Inoue (NICT, Japan)
Masahiro Ishiyama (Toshiba Corporation, Japan)
Holger Karl (University of Paderborn, Germany)
Hughes Kester (Qinetiq Ltd, UK)
Dongkyun Kim (Kyungpook National University, Korea)
Peter Langendoerfer (IHP Microelectronics, Germany)
Madjid Merabti (Liverpool John Moores University, UK)
Isabelle Moreau (Mitsubishi Electric ITE, France)
Hiroyuki Morikawa (University of Tokyo, Japan)
Yasuto Nakanishi (Keio University, Japan)
Ken Ohta (NTT DoCoMo, Japan)
Ryouji Ono (Mitsubishi Electric, Japan)
Mohamed Ould-Khaoua (University of Glasgow, UK)
Antonio Pescape (University of Napoli, Italy)
Petar Popovski (Aalborg University, Denmark)
Jeremy Randles (British Telecom, UK)
Ichiro Satoh (National Institute of Informatics, Japan)
Winston Seah (Institute for Infocomm Research, Singapore)
Hiroshi Shigeno (Keio University, Japan)
Biplab Sikdar (Rensselaer Polytechnic Institute, USA)
David Simplot-Ryl (University of Lille 1, France)
Tatsuya Suda (University of California Irvine, USA)
Shinta Sugimoto (Nippon Ericsson, Japan)
Keisuke Suwa (Musashi Institute of Technology, Japan)
Kevin W. Tsai (University of California, Irvine, USA)
Xin Wang (Fudan University, China)
Neil Williams (ERA Technology Ltd, UK)
Nik Van den Wingaert (University of Antwerp, Belgium)
Hirozumi Yamaguchi (Osaka University, Japan)
Kun Yang (Essex University, UK)
Yang Yang (University College London, UK)
Masashi Yano (Hitachi Ltd, Japan)
Hidetoshi Yokota (KDDI R&D Laboratories, Japan)
Ekio Yoneki (Cambridge University, UK)
Qing-An Zeng (University of Cincinnati, USA)

----
$BKL?\2l(B $B51L@(B <kitasuka@csce.kyushu-u.ac.jp>
TEL/FAX: 092-583-7625($B8&5f<<(B), FAX2: 092-583-1338($B>pJs;vL3<<(B)
$B6e=#Bg3X(B $BBg3X1!(B $B%7%9%F%`>pJs2J3X8&5f1!(B $B>pJs9)3XItLg(B($BC^;gCO6h(B) $BJ!ED!&Cf@>8&5f<<(B $B=u<j(B


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 21 03:23:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWpzH-00082P-OD; Fri, 21 Apr 2006 03:23:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWpzG-00082K-JO
	for monami6@ietf.org; Fri, 21 Apr 2006 03:23:30 -0400
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWpzC-0005u1-7A
	for monami6@ietf.org; Fri, 21 Apr 2006 03:23:30 -0400
Received: from dhcp-rocq-97.inria.fr (guest-rocq-135223.inria.fr
	[128.93.135.223])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id B3B5C4D850
	for <monami6@ietf.org>; Fri, 21 Apr 2006 16:23:24 +0900 (JST)
Date: Fri, 21 Apr 2006 09:24:06 +0200
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: ml-ietf-monami6 <monami6@ietf.org>
Message-Id: <20060421092406.256e2668.ernst@sfc.wide.ad.jp>
Organization: Keio University
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Monami6] CFP - WNEPT - Waterloo, August 2006.
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Dea all,

As chair of the MONAMI6 working group, I've refrained myself to post CFP
(due to past critics, etc), but other people do it, and it is acceptable
I think when the CFP does include network mobility. 

So, here is one that people on this list will have interest in as it
includes "Multiple access networks in public transport", "NEMO, "IPv6",
etc.

Workshop on Networking in Public Transport 
(WNEPT, http://www.wnept.org)

to be held in Waterloo, Ontario, Canada, on August 10, 2006.

(in conjunction with  the Third International Conference on Quality of
Service in Heterogeneous Wired/Wireless Networks [QShine] 2006,
http://www.qshine.org)

The workshop will provide a highly selective venue to present work
related to communication networks on public transport, ranging from
theoretical research to practical systems deployment. 

The full CFP is available on the web site http://www.wnept.org

Important Dates

Full Papers due: May 15, 2006
Notification of Acceptance: June 16, 2006
Camera-ready Manuscripts due: June 30, 2006
Workshop Date: August 10, 2006

Regards,
Thierry.


-- 
Thierry ERNST, PhD
INRIA Rocquencourt Projet IMARA
+33 1 39 63 59 30

-- 
Thierry ERNST, PhD
INRIA Rocquencourt Projet IMARA
+33 1 39 63 59 30


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 21 04:13:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWqlS-0003Gv-OM; Fri, 21 Apr 2006 04:13:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWqlS-0003Gq-2T
	for monami6@ietf.org; Fri, 21 Apr 2006 04:13:18 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWqlN-0007sY-Sw
	for monami6@ietf.org; Fri, 21 Apr 2006 04:13:17 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5C788212C59
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:13:12 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id 24F43212C44
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:13:12 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id A8EC6BDC40
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:13:11 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id 424C4BDC38
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:13:11 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <000001c6641e$7a098ac0$af726e0a@china.huawei.com>
References: <000001c6641e$7a098ac0$af726e0a@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <37fcb7b77db632e3a64c8505ca17261d@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Fri, 21 Apr 2006 11:13:10 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7b8e6f6ef974ecda19a6b57d59caeb7d
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Sam,

El 20/04/2006, a las 5:02, Sam Xia escribi=F3:

> Hi, all,
>      Unitl now, I understand the meaning of the sentence for "The fact=20=

> that
> a mobile node has multiple interfaces does not imply that it has=20
> multiple
> HoAs and vice-versa". But I have some other questions about this.
>

>      In general, it is universal that multiple interfaces share the=20
> same one
> address or more. But IMHO, the prerequisite is that the multiple=20
> interfaces
> have the same the attributes about L1 and  L2. For example, as to=20
> ethernet
> switch (including Cisco, 3Com, Huawei), multiple ethernet interfaces=20=

> in the
> same VLAN share the same IP address(s). I have not seen the fact that
> different types of interfaces share the same IP address (I don't think=20=

> it is
> a good idea to have POS interface and ATM interface, or T1/C1=20
> interface and
> ethernet interface, or WCDMA interface and WLAN interface share the=20
> same IP
> address). Can anyone give me the example for this?
>      As a matter of fact, if we do so like this, we will face many=20
> issues of
> implementing aspect. For example, if different interfaces share the ip
> address,


but you seem to imply from the fact that a node has a single HoA and=20
multiple interfaces that the HoA is associated with the multiple=20
interfaces, as if the Hoa was idrectly assigned to the multiple=20
interfaces, but i am not sure this is the case...

i mean the HoA is both a identifier and a locator. As a locator, the=20
HoA is assigned to a single interface i guess, to the interface that is=20=

used to connect to the home network ( i am assuming that in the common=20=

case, the multohomed node will have differetn technologies that it uses=20=

to obtain connectivity through different access technologies, but only=20=

one technology is used to connect to the home network)

However, as an identifier the HoA is associated to the MN as a whole,=20
so it can be bound to CoAs that belong to different interfaces.

So, in this case, is not the HoA that is assigned to the differetn=20
interfaces, but the HoA is associated with CoAs of different=20
interfaces.

Regards, marcelo


> then upper layer application will find it difficult to determine
> the specific interface from which the packet should be sent. It is=20
> because
> upper layer application can not specify the outbound interface based=20=

> on the
> service access points(i.e., socket) provided by TCP/UDP.
>     That's all. Thank you for your kind reply.
>
>
>> -----Original Message-----
>> From: monami6-request@ietf.org [mailto:monami6-request@ietf.org]
>> Sent: Thursday, April 20, 2006 12:00 AM
>> To: monami6@ietf.org
>> Subject: Monami6 Digest, Vol 14, Issue 17
>>
>>
>> Send Monami6 mailing list submissions to
>> 	monami6@ietf.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://www1.ietf.org/mailman/listinfo/monami6
>> or, via email, send a message with subject or body 'help' to
>> 	monami6-request@ietf.org
>>
>> You can reach the person managing the list at
>> 	monami6-owner@ietf.org
>>
>> When replying, please edit your Subject line so it is more
>> specific than "Re: Contents of Monami6 digest..."
>>
>>
>> Today's Topics:
>>
>>    1. RE: a question about Analysis of Multihoming in Mobile IPv6
>>       (Starry.Lin)
>>    2. Re: a question about Analysis of Multihoming in Mobile IPv6
>>       (Nicolas Montavont)
>>    3. Re: a question about Analysis of Multihoming in Mobile IPv6
>>       (Tero Kauppinen (JO/LMF))
>>    4. Re: a question about Analysis of Multihoming in Mobile IPv6
>>       (Nicolas Montavont)
>>    5. Re: a question about Analysis of Multihoming in Mobile IPv6
>>       (Tero Kauppinen (JO/LMF))
>>    6. RE: a question about Analysis of Multihoming in Mobile IPv6
>>       (Starry.Lin)
>>
>>
>> =
----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 19 Apr 2006 10:12:27 +0800
>> From: "Starry.Lin" <linjing@huawei.com>
>> Subject: RE: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: xiazhongqi@huawei.com
>> Cc: 'Monami6 WG' <monami6@ietf.org>
>> Message-ID:
>> =09
>> <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArhqnyUIk+02Spx
>> AuJMgAAMKAAAAQAAAAUQYzbGaAUEOh/mpzjLNuNQEAAAAA@huawei.com>
>> =09
>> Content-Type: text/plain; charset=3Dus-ascii
>>
>> In my opinion, i think it's to say that some/all interfaces
>> of a MN may have the same HA and HoA. For instance, you can
>> image a MN have both WLAN and WCDMA interface, and the WLAN
>> and WCDMA access services are both provided by the same
>> Operator. Thus the MN's interface on the WLAN and interface
>> on the WCDMA network may use the same HA and HoA provided by
>> the same Operator. An other scenario is that no matter how
>> many access capabilities the MN has, the Mobile IP, as a
>> service, is provided by one operator. Any way, the key point
>> is that multiple interfaces only imply that the MN has
>> multiple CoA on each interface( if the interface is active),
>> not the HoA.
>>
>>
>> -----Original Message-----
>> From: Sam Xia [mailto:xiazhongqi@huawei.com]
>> Sent: Friday, April 14, 2006 3:42 PM
>> To: monami6@ietf.org
>> Subject: [Monami6] a question about Analysis of Multihoming
>> in Mobile IPv6
>>
>>
>> Hello, everyone,
>>           I am confused about a sentence in Analysis of
>> Multihoming in Mobile IPv6.
>> The sentence is "The fact that a mobile node has multiple
>> interfaces does not
>> imply that it has multiple HoAs and vice-versa" and located
>> at the last paragragh on page 10.
>>           I think one interface should have a corresponding
>> address or more. So, if a mobile node is in its home, each of
>> its interfaces has a address at least.
>>
>> Anyone can give me the detailed explaination or a scenario? Thanks.
>>
>>
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 19 Apr 2006 10:04:19 +0200
>> From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
>> Subject: Re: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: Monami6 WG <monami6@ietf.org>
>> Cc: xiazhongqi@huawei.com
>> Message-ID: <4445EF03.7070904@enst-bretagne.fr>
>> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>>
>> Hi,
>>
>> Starry.Lin wrote:
>>
>>> In my opinion, i think it's to say that some/all interfaces
>> of a MN may
>>> have the same HA and HoA. For instance, you can image a MN have both
>>> WLAN and WCDMA interface, and the WLAN and WCDMA access services are
>>> both provided by the same Operator. Thus the MN's interface
>> on the WLAN
>>> and interface on the WCDMA network may use the same HA and
>> HoA provided
>>> by the same Operator. An other scenario is that no matter how many
>>> access capabilities the MN has, the Mobile IP, as a service, is
>>> provided by one operator. Any way, the key point is that multiple
>>> interfaces only imply that the MN has multiple CoA on each
>> interface(
>>> if the interface is active), not the HoA.
>>>
>>>
>> This is a good interpretation of the sentence.
>> A MN may have multiple interfaces (possibly bound to multiple
>> CoAs), and
>> ony one HoA.
>>
>> Nicolas
>>
>>>
>>> -----Original Message-----
>>> From: Sam Xia [mailto:xiazhongqi@huawei.com]
>>> Sent: Friday, April 14, 2006 3:42 PM
>>> To: monami6@ietf.org
>>> Subject: [Monami6] a question about Analysis of Multihoming
>> in Mobile IPv6
>>>
>>>
>>> Hello, everyone,
>>>          I am confused about a sentence in Analysis of
>> Multihoming in
>>> Mobile IPv6. The sentence is "The fact that a mobile node
>> has multiple
>>> interfaces does not
>>> imply that it has multiple HoAs and vice-versa" and located
>> at the last
>>> paragragh on page 10.
>>>          I think one interface should have a corresponding
>> address or more.
>>> So, if a mobile node is in its home, each of its interfaces
>> has a address at
>>> least.
>>>
>>> Anyone can give me the detailed explaination or a scenario? Thanks.
>>>
>>>
>>>
>>> _______________________________________________
>>> Monami6 mailing list
>>> Monami6@ietf.org https://www1.ietf.org/mailman/listinfo/monami6
>>>
>>>
>>> _______________________________________________
>>> Monami6 mailing list
>>> Monami6@ietf.org https://www1.ietf.org/mailman/listinfo/monami6
>>>
>>>
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 19 Apr 2006 11:08:12 +0300
>> From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
>> Subject: Re: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: Monami6 WG <monami6@ietf.org>
>> Cc: xiazhongqi@huawei.com
>> Message-ID: <4445EFEC.9040100@ericsson.com>
>> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>>
>> Starry.Lin wrote:
>>
>>> Any way, the key point is that multiple interfaces only
>> imply that the
>>> MN has multiple CoA on each interface( if the interface is active),
>>> not the HoA.
>>>
>>
>> I don't understand the part "multiple interfaces only imply
>> that the MN
>> has multiple CoAs on each interface". I think it should say "multiple
>> (active) interfaces only imply that the MN has multiple CoAs. Each
>> interface can have one or more CoAs (if the interface is active)."
>> Moreover, the MN can have more than one HoA despite the number of
>> interfaces (i.e. multihomed).
>>
>> --=20
>> Tero
>>
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 19 Apr 2006 10:16:45 +0200
>> From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
>> Subject: Re: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: Monami6 WG <monami6@ietf.org>
>> Cc: xiazhongqi@huawei.com
>> Message-ID: <4445F1ED.4080001@enst-bretagne.fr>
>> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>>
>> Tero Kauppinen (JO/LMF) wrote:
>>
>>> Starry.Lin wrote:
>>>
>>>> Any way, the key point is that multiple interfaces only imply that
>>>> the MN
>>>> has multiple CoA on each interface( if the interface is
>> active), not the
>>>> HoA.
>>>>
>>>
>>> I don't understand the part "multiple interfaces only imply that the
>>> MN has multiple CoAs on each interface". I think it should say
>>> "multiple (active) interfaces only imply that the MN has
>> multiple CoAs.
>>
>> Agree, but this is the text of Starry. Did you find something
>> like this
>> in the draft?
>>
>>> Each interface can have one or more CoAs (if the interface is
>>> active)." Moreover, the MN can have more than one HoA despite the
>>> number of interfaces (i.e. multihomed).
>>
>> This is what we wanted to say with the sentence mentioned in
>> an earlier
>> email:
>>
>> "The fact that a mobile node has multiple interfaces does not
>> imply that
>> it has multiple HoAs and vice-versa"
>>
>> Nicolas
>>
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Wed, 19 Apr 2006 11:26:35 +0300
>> From: "Tero Kauppinen (JO/LMF)" <tero.kauppinen@ericsson.com>
>> Subject: Re: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: Monami6 WG <monami6@ietf.org>
>> Cc: xiazhongqi@huawei.com
>> Message-ID: <4445F43B.4020506@ericsson.com>
>> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>>
>> Nicolas Montavont wrote:
>>>> I don't understand the part "multiple interfaces only
>> imply that the
>>>> MN has multiple CoAs on each interface". I think it should say
>>>> "multiple (active) interfaces only imply that the MN has
>> multiple CoAs.
>>>
>>> Agree, but this is the text of Starry. Did you find something like
>>> this
>>> in the draft?
>>
>> Nope, I was just referring to Starry's sentence.
>>
>>> This is what we wanted to say with the sentence mentioned in an
>>> earlier
>>> email:
>>>
>>> "The fact that a mobile node has multiple interfaces does not imply
>>> that
>>> it has multiple HoAs and vice-versa"
>>>
>>
>> Sure, I don't have problems in understanding the sentence,
>> but maybe it
>> should be written a little bit differently if some people find it
>> confusing.
>>
>> Cowardly escaping without posting a proposal...
>> Tero
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Wed, 19 Apr 2006 17:08:26 +0800
>> From: "Starry.Lin" <linjing@huawei.com>
>> Subject: RE: [Monami6] a question about Analysis of Multihoming in
>> 	Mobile IPv6
>> To: 'Monami6 WG' <monami6@ietf.org>
>> Cc: xiazhongqi@huawei.com
>> Message-ID: <000201c66390$d18f0790$7243460a@china.huawei.com>
>> Content-Type: text/plain; charset=3DISO-8859-1
>>
>> Thanks Tero's comments. I agree that his expression is more
>> exactly. Each interface can have more than one CoA(also in
>> most condition, there is one). And what's more, the MN can
>> have more than one HoA if there are more than one prefix on
>> the link, even if the MN is not multihoming.
>>
>>
>>
>> -----Original Message-----
>> From: Tero Kauppinen (JO/LMF) [mailto:tero.kauppinen@ericsson.com]
>> Sent: Wednesday, April 19, 2006 4:08 PM
>> To: Monami6 WG
>> Cc: xiazhongqi@huawei.com
>> Subject: Re: [Monami6] a question about Analysis of
>> Multihoming in Mobile IPv6
>>
>>
>> Starry.Lin wrote:
>>
>>> Any way, the key point is that multiple interfaces only
>> imply that the
>>> MN has multiple CoA on each interface( if the interface is active),
>>> not the HoA.
>>>
>>
>> I don't understand the part "multiple interfaces only imply
>> that the MN
>> has multiple CoAs on each interface". I think it should say "multiple
>> (active) interfaces only imply that the MN has multiple CoAs. Each
>> interface can have one or more CoAs (if the interface is active)."
>> Moreover, the MN can have more than one HoA despite the number of
>> interfaces (i.e. multihomed).
>>
>> --=20
>> Tero
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Monami6 mailing list
>> Monami6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/monami6
>>
>>
>> End of Monami6 Digest, Vol 14, Issue 17
>> ***************************************
>>
>
>
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 21 04:14:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWqmZ-00048p-5Q; Fri, 21 Apr 2006 04:14:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWqmY-00048k-PT
	for monami6@ietf.org; Fri, 21 Apr 2006 04:14:26 -0400
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWqmU-0007wi-A6
	for monami6@ietf.org; Fri, 21 Apr 2006 04:14:26 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id A1593212C59
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:14:21 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146])
	by n2.nomadiclab.com (Postfix) with ESMTP id 3EE83212C44
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:14:21 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1])
	by outside.nomadiclab.com (Postfix) with ESMTP id 0CC89BDC40
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:14:21 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179])
	by outside.nomadiclab.com (Postfix) with ESMTP id CEFD3BDC38
	for <monami6@ietf.org>; Fri, 21 Apr 2006 11:14:20 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v623)
In-Reply-To: <615BD9B54CB01B41838C323DB9E91AAB407550@esebe100.NOE.Nokia.com>
References: <615BD9B54CB01B41838C323DB9E91AAB407550@esebe100.NOE.Nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <a33cc2502c42a5d70161fc8d64b93991@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [Monami6] a question about Analysis of Multihoming in Mobile IPv6
Date: Fri, 21 Apr 2006 11:14:20 +0300
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


El 20/04/2006, a las 6:04, <john.loughney@nokia.com> escribi=F3:

> Marcelo,
>
>
>> but, if a MN has multiple HAs served by different ISPs, then it must
>> have multiple HoAs, right?
>>
>> (this would be so, because since it would have different HAs, in
>> different Home Networks and since they are served by differetn ISPs,
>> they need to use differetn PA blocks)
>>
>> In other words, the operator of the access netwrok has no influence =
in
>> the number of Hoas, but the ISPs of the HAs/Home networks has a =
direct
>> impact in the number of HoAs, agree?
>
> I essentially agree with this, with one small comment.  There probably
> be some aggregators who provide a HA, aggregating a number of ISPs.
>

I am not sure how this would work...
Are you assuming that there is an address blosk assigned to the=20
aggregators?
or the HoAs belong to one of the ISPs address blocks?

regards, marcelo


> John
>
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Apr 25 13:09:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYR1k-0000Yw-2c; Tue, 25 Apr 2006 13:08:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYR1i-0000Yo-MK
	for monami6@ietf.org; Tue, 25 Apr 2006 13:08:38 -0400
Received: from posti5.jyu.fi ([130.234.4.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYR1h-0002yE-8J
	for monami6@ietf.org; Tue, 25 Apr 2006 13:08:38 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3PH8MCw014722
	for <monami6@ietf.org>; Tue, 25 Apr 2006 20:08:22 +0300
Received: from posti5.jyu.fi ([127.0.0.1])
	by localhost (posti5.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 14680-03 for <monami6@ietf.org>;
	Tue, 25 Apr 2006 20:08:21 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti5.jyu.fi (8.13.6/8.13.6) with ESMTP id k3PH8JeL014717
	for <monami6@ietf.org>; Tue, 25 Apr 2006 20:08:21 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: [Monami6] multiplecoa-05 - CoA registration, wants/MUST
Date: Tue, 25 Apr 2006 20:08:01 +0300
User-Agent: KMail/1.9.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604252008.02338.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

In draft-wakikawa-mobileip-multiplecoa-05.txt in Section 3.1
it says:
  "Once a mobile node gets several IPv6 global addresses on distinct
   interfaces, it MUST register these addresses with its home agent
   (home registration).  If the mobile node wants to register multiple
   bindings to its home agent, it MUST generate a BID for each Care-of
   Address and record it into the binding update list entry.  ..."

So, does the MN have to ("MUST") register all its CoAs with its HA
or only "If the mobile node wants to register multiple bindings"?
It is not so clear from this text.

And why is the "on distinct interfaces" note needed?

Thanks,
Gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Apr 26 18:27:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYsTN-0000iG-8N; Wed, 26 Apr 2006 18:27:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYsTM-0000i6-7C
	for monami6@ietf.org; Wed, 26 Apr 2006 18:27:00 -0400
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYsTK-0003BI-LX
	for monami6@ietf.org; Wed, 26 Apr 2006 18:27:00 -0400
Received: from dhcp-143-221.sfc.wide.ad.jp.sfc.wide.ad.jp
	(dhcp-143-221.sfc.wide.ad.jp [203.178.143.221])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	k3QMQlUl030855; Thu, 27 Apr 2006 07:26:47 +0900
Date: Thu, 27 Apr 2006 07:26:37 +0900
Message-ID: <m2d5f4vuqq.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: =?ISO-8859-1?Q?G=E1bor?= Fekete <feketgai@index.hu>
Subject: Re: [Monami6] multiplecoa-05 - CoA registration, wants/MUST
In-Reply-To: <200604252008.02338.feketgai@index.hu>
References: <200604252008.02338.feketgai@index.hu>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50
	(i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi Gabor

At Tue, 25 Apr 2006 20:08:01 +0300,
G=E1bor Fekete wrote:
>=20
> Hi,
>=20
> In draft-wakikawa-mobileip-multiplecoa-05.txt in Section 3.1
> it says:
>   "Once a mobile node gets several IPv6 global addresses on distinct
>    interfaces, it MUST register these addresses with its home agent
>    (home registration).  If the mobile node wants to register multiple
>    bindings to its home agent, it MUST generate a BID for each Care-of
>    Address and record it into the binding update list entry.  ..."
>=20
> So, does the MN have to ("MUST") register all its CoAs with its HA
> or only "If the mobile node wants to register multiple bindings"?

If the mobile node wants to register multiple bindings.

> It is not so clear from this text.

OK, I will update the texts.

> And why is the "on distinct interfaces" note needed?

remove this phrase.

thanks for comments
ryuji

> Thanks,
> Gabor
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 28 00:49:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZKvD-0003Gq-05; Fri, 28 Apr 2006 00:49:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZKvC-0003G7-8F
	for monami6@ietf.org; Fri, 28 Apr 2006 00:49:38 -0400
Received: from smtp.mei.co.jp ([133.183.129.25] helo=smtp1.mei.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZKog-0004Eh-5P
	for monami6@ietf.org; Fri, 28 Apr 2006 00:42:55 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp1.mei.co.jp (8.12.11.20060308/3.7W/kings) with ESMTP id
	k3S4gp1g024855
	for <monami6@ietf.org>; Fri, 28 Apr 2006 13:42:51 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx1) with ESMTP id
	k3S4gp622904
	for <monami6@ietf.org>; Fri, 28 Apr 2006 13:42:51 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/expos) with ESMTP id
	k3S4go807594
	for <monami6@ietf.org>; Fri, 28 Apr 2006 13:42:50 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.11.6p2/3.7W/soml26) id k3S4gqY09789
	for monami6@ietf.org; Fri, 28 Apr 2006 13:42:52 +0900 (JST)
Received: from [10.68.136.44]
	by soml26.jp.panasonic.com (8.11.6p2/3.7W) with ESMTP id k3S4gp509727
	for <monami6@ietf.org>; Fri, 28 Apr 2006 13:42:51 +0900 (JST)
Date: Fri, 28 Apr 2006 13:42:51 +0900
From: Keigo Aso <asou.keigo@jp.panasonic.com>
To: Monami6 WG <monami6@ietf.org>
Message-Id: <20060428113426.2B6F.ASOU.KEIGO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Monami6] De-Registration BU in MCoA draft
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hello,

I have question about de-registration BU.

In section 5.5 "Using Alternate Care-of Address",
   "In these cases, the mobile node sends a Binding Update with both
   Alternate Care-of Address sub-option and Binding Unique Identifier
   sub-option. "

Does the De-Registration Binding Update have to contain 
Care-of Address to indicate the address which will be deleted 
by using Alternate Care-of Address sub-option or Source Address ? 
Containing both BID sub-option and "specified Care-of Address"
in De-Registartion BU seems to be redundant. 

Regards,
Keigo


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Apr 28 03:01:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZMyo-0000x4-1y; Fri, 28 Apr 2006 03:01:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZMym-0000wg-Gt
	for monami6@ietf.org; Fri, 28 Apr 2006 03:01:28 -0400
Received: from posti6.jyu.fi ([130.234.4.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZMxn-000424-R0
	for monami6@ietf.org; Fri, 28 Apr 2006 03:00:32 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3S70PWt006182
	for <monami6@ietf.org>; Fri, 28 Apr 2006 10:00:25 +0300
Received: from posti6.jyu.fi ([127.0.0.1])
	by localhost (posti6.jyu.fi [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 06143-03 for <monami6@ietf.org>;
	Fri, 28 Apr 2006 10:00:22 +0300 (EEST)
Received: from b19c.mylly.jyu.fi (b19c.mylly.jyu.fi [130.234.196.146])
	by posti6.jyu.fi (8.13.6/8.13.6) with ESMTP id k3S70KAP006177
	for <monami6@ietf.org>; Fri, 28 Apr 2006 10:00:22 +0300
From: =?iso-8859-1?q?G=E1bor_Fekete?= <feketgai@index.hu>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] De-Registration BU in MCoA draft
Date: Fri, 28 Apr 2006 10:00:07 +0300
User-Agent: KMail/1.9.1
References: <20060428113426.2B6F.ASOU.KEIGO@jp.panasonic.com>
In-Reply-To: <20060428113426.2B6F.ASOU.KEIGO@jp.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604281000.08754.feketgai@index.hu>
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Keigo and list,

On Friday 28 April 2006 07:42, Keigo Aso wrote:
> Hello,
>
> I have question about de-registration BU.
>
> In section 5.5 "Using Alternate Care-of Address",
>    "In these cases, the mobile node sends a Binding Update with both
>    Alternate Care-of Address sub-option and Binding Unique Identifier
>    sub-option. "
>
> Does the De-Registration Binding Update have to contain
> Care-of Address to indicate the address which will be deleted
> by using Alternate Care-of Address sub-option or Source Address ?
> Containing both BID sub-option and "specified Care-of Address"
> in De-Registartion BU seems to be redundant.
>

I agree. Actually section 5.3 "Sending De-Registration Binding Update" says
  "other hand, if the mobile node wants to remove multiple Care-of
   Addresses at once, it stores multiple Unique Binding Identifier sub-
   options and Alternate Care-of Address sub-options in a Binding
   Update.  The Care-of Addresses stored in the Alternate Care-of
   Address sub-options will be all removed."

It is not clear why the AltCoAs are needed. And it misses to mention wether
the B-flag must be set or not in this case (I guess yes).
And since two different BIDs may correspond to the same CoA, the last sentence
in section 5.3 is a bit misleading. For me it tells that
if the AltCoA contains CoA-A then every binding having CoA-A will be removed
no matter what their BIDs are.
So it is not clear whether a de-reg BU says "de-register this BID" or
"de-register this CoA".

Plus RFC3775 says that for de-reg the HoA must be equal to the CoA or the
lifetime be zero. And in this regard the de-reg in the multiplecoa draft is
a bit inconsistent with RFC3775.

Regards,
Gabor

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



