From monami6-bounces@ietf.org Thu Aug 02 07:38:17 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGZ0R-0006N1-8g; Thu, 02 Aug 2007 07:38:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGZ0P-0006Ms-HT
	for monami6@ietf.org; Thu, 02 Aug 2007 07:38:13 -0400
Received: from [2001:200:601:12:230:48ff:fe22:3a84] (helo=mandala.kddilabs.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGZ0M-0005Qx-3c
	for monami6@ietf.org; Thu, 02 Aug 2007 07:38:13 -0400
Received: from localhost (localhost [127.0.0.1])
	by mandala.kddilabs.jp (Postfix) with ESMTP
	id B84D8EC86F; Thu,  2 Aug 2007 20:38:07 +0900 (JST)
Received: from spears.ast.kddilabs.jp (unknown [2001:200:601:800::168])
	by mandala.kddilabs.jp (Postfix) with ESMTP
	id 079A9EC82F; Thu,  2 Aug 2007 20:38:07 +0900 (JST)
Received: from [IPv6?2001?200?601?800?f454?eab9?7c71?99a1] (unknown
	[IPv6:2001:200:601:800:f454:eab9:7c71:99a1])
	by spears.ast.kddilabs.jp (Postfix) with ESMTP id E9CB16903D6;
	Thu,  2 Aug 2007 20:38:06 +0900 (JST)
Message-ID: <46B1C273.7080009@kddilabs.jp>
Date: Thu, 02 Aug 2007 20:39:31 +0900
From: Kazuyuki Tasaka <ka-tasaka@kddilabs.jp>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Teco_Boot <teco@inf-net.nl>
Subject: Re: [Monami6] Monami6 Filter Rules
References: <000501c7d370$f35a5590$b500800a@Teco>
In-Reply-To: <000501c7d370$f35a5590$b500800a@Teco>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
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 Teco,

Thank you for your response.

As you say, it might serve as a reference to
define the protocol for policy exchange.

We will define the generic policy data set that can also use in
RSVP Filter_Spec, in our document, or "A Policy Data Set for Flow
Distribution". However, our document doesn't define protocol for
policy exchange.
I think that we should discuss the possibility of reusing of
RSVP Filter_Spec when we define the protocol for policy exchange.

Kazuyuki

Teco_Boot Wrote:
> Hi Kazuyuki,
> 
> I am not an RSVP expert. Here a snapshot for checking RSVP Filter_Spec:
> RFC2205: RSVP - APPENDIX A. Object Definitions
> RFC2746: RSVP Operation Over IP Tunnels
> RFC3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
> 
> I think RSVP-TE has a similar context as MONAMI6. 
> 
> Teco.
> 
>> -----Original Message-----
>> From: Kazuyuki Tasaka [mailto:ka-tasaka@kddilabs.jp]
>> Sent: dinsdag 31 juli 2007 14:01
>> To: Teco_Boot
>> Cc: 'Monami6 WG'
>> Subject: Re: [Monami6] Monami6 Filter Rules
>>
>> Hi Teco,
>>
>> Teco_Boot wrote:
>>> Hi Kazuyuki,
>>> I understand RSVP is to be used in a different context.
>>> Defining a protocol for classifying traffic is a common attribute.
>> I agree.
>>
>>> Using RSVP itself would add IntServ QoS for MIP tunnel, which could be
>>> needed also. So RSVP support could already be implemented and reuse the
>>> filter definition sub-protocol for BU looks an attractive option to me.
>> I think that we should consider reusing if filter definition
>> sub-protocol for BU does not depend on RSVP and it is generic. If it is
>> not so, we should modify it to define generic filter rules for MONAMI6
>> or newly define it.
>> Could you tell me documents that described filter definition
>> sub-protocol for BU?
>>
>> regards,
>> kazuyuki
>>
>>> Teco.
>>>
>>>> -----Original Message-----
>>>> From: Kazuyuki Tasaka [mailto:ka-tasaka@kddilabs.jp]
>>>> Sent: dinsdag 31 juli 2007 8:20
>>>> To: Monami6 WG
>>>> Subject: Re: [Monami6] Monami6 Filter Rules
>>>>
>>>> Hello Teco,
>>>>
>>>> Teco_Boot wrote:
>>>>> Hi,
>>>>> Have we evaluated using the RSVP filter mechanism (Filter_Spec) for
>>>> Monami6?
>>>>
>>>> I believe that we don't do it yet.
>>>>
>>>>> Classifying a flow for queue selection (RSVP) and interface selection
>>>>> (Monami6) looks very similar to me. I think we should try to use what
>> we
>>>>> already have.
>>>> I also think that classifying a flow for queue selection (RSVP)and
>>>> interface selection (Monami6) looks very similar and we should refer
>>>> to how to classify a flow and select the interface.
>>>>
>>>> However, there are differences between RSVP and Protocol to set filter
>>>> rules for Monami6. As one difference, RSVP is receiver-oriented, but
>>>> Protocol to set filter rules for Monami6 is user-oriented or
>>>> operator-oriented. User-oriented means MN(or MR)-oriented and
>>>> operator-oriented means HA-oriented.
>>>>
>>>> For example, when a user need to set up preferences (Section 3.3, 3.4
>>>> and 3.5 of Motivations and Scenarios for Using Multiple Interfaces and
>>>> Global Addresses), I think that MN or MR should not only set filter
>>>> rules for downlink from HA but also set filter rules for uplink.
>>>>
>>>> In the following draft, it is considered.
>>>> http://www.ietf.org/internet-drafts/draft-mitsuya-monami6-flow-
>>>> distribution-policy-03.txt
>>>>
>>>> regards,
>>>> kazuyuki
>>>>
>>>>> Teco.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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 Aug 02 15:54:12 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGgkN-0003q5-Jp; Thu, 02 Aug 2007 15:54:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGgkN-0003q0-0X
	for monami6@ietf.org; Thu, 02 Aug 2007 15:54:11 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGgkL-0000fn-9V
	for monami6@ietf.org; Thu, 02 Aug 2007 15:54:10 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with
	ESMTP id l72Js4vC027857
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:54:04 +0200
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr
	[192.44.77.4])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2007.03.20) with
	ESMTP id l72Js0Dh027847
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:54:00 +0200
Received: from [192.168.0.10] (lns-bzn-40-82-251-171-82.adsl.proxad.net
	[82.251.171.82]) (authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	l72JrqJv012380
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:53:58 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <398121FC-406B-4DFD-A9F6-60364E936F4E@enst-bretagne.fr>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Monami6 WG <monami6@ietf.org>
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Date: Thu, 2 Aug 2007 21:53:48 +0200
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: [Monami6] conclusion of the meeting
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

Dear all,

Let us drive the main conclusions of the last Monami6 meeting:

   - You will find the minutes and the slides of the Monami6 meeting  
on the IETF meeting materials page which is located at
https://datatracker.ietf.org/meeting/69/materials.html

    - We will issue a WGLC quite soon (around september 2007) on the
following I-D :
       - http://tools.ietf.org/id/draft-ietf-monami6-multihoming- 
motivation-scenario-02.txt
       - http://tools.ietf.org/id/draft-ietf-monami6-mipv6- 
analysis-03.txt
       - http://tools.ietf.org/id/draft-ietf-monami6-multiplecoa-03.txt

So if you have further comments on these, please submit them ASAP.

    - There was a rough consensus to accept
draft-soliman-flow-binding-04.txt as a WG document for the item 4
(transport of the flow filters) of our charter. We will send a separate
email to confirm this.

    - The working group is now open to accept contribution for the
generic format to describe the flows policies / filters. As for now, the
following documents have been submitted as individual contributions for
this item:

       - http://tools.ietf.org/id/draft-mitsuya-monami6-flow- 
distribution-policy-03.txt
       - http://tools.ietf.org/id/draft-larsson-monami6-filter- 
rules-02.txt

Teco also proposed to (re) use the RSVP filter mechanism  
(FILTER_SPEC), which method
needs to be considered.
We really encourage discussion on this topic, in order to make progress
and define which format we will adopt.

Regards,
Nicolas and Thierry

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



From monami6-bounces@ietf.org Thu Aug 02 15:54:56 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGgl5-0003wB-Pm; Thu, 02 Aug 2007 15:54:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGgl4-0003vw-VC
	for monami6@ietf.org; Thu, 02 Aug 2007 15:54:54 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGgl3-0000gf-HY
	for monami6@ietf.org; Thu, 02 Aug 2007 15:54:54 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with
	ESMTP id l72Jsqb5027900
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:54:52 +0200
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr
	[192.44.77.4])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2007.03.20) with
	ESMTP id l72Jsmv3027893
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:54:49 +0200
Received: from [192.168.0.10] (lns-bzn-40-82-251-171-82.adsl.proxad.net
	[82.251.171.82]) (authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	l72JrqJw012380
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <monami6@ietf.org>; Thu, 2 Aug 2007 21:54:47 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Monami6 WG <monami6@ietf.org>
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Date: Thu, 2 Aug 2007 21:54:43 +0200
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [Monami6] consensus call on
	draft-soliman-monami6-flow-binding-04.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

During the meeting, chairs asked the attendees if

draft-soliman-monami6-flow-binding-04.txt

shall be accepted for the transport of the policies as described in  
the 4th WG item

[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. The solution involves two  
specifications, one for the policy format and another for its  
transport [both Standard Track]

To this question, nobody voted against at the last Monami6 meeting.  
So, we would like to confirm this decision on the ML.

If you have a specific concern with this decision, please express  
your views until 12:01 am UTC Thursday, August the 16th, 2007

Regards,
the chairs

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



From monami6-bounces@ietf.org Fri Aug 03 01:21:34 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGpbR-0008Eg-0R; Fri, 03 Aug 2007 01:21:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGpbP-00086h-I0
	for monami6@ietf.org; Fri, 03 Aug 2007 01:21:31 -0400
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGpbO-0005Ux-V8
	for monami6@ietf.org; Fri, 03 Aug 2007 01:21:31 -0400
Received: from [192.168.1.117] (c-67-189-100-226.hsd1.or.comcast.net
	[67.189.100.226])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 27CF44D8A1;
	Fri,  3 Aug 2007 14:21:28 +0900 (JST)
In-Reply-To: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
References: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <50420C24-D620-45EF-9BFA-0D15E80FB73B@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Koshiro MITSUYA <mitsuya@sfc.wide.ad.jp>
Subject: Re: [Monami6] consensus call on
	draft-soliman-monami6-flow-binding-04.txt
Date: Thu, 2 Aug 2007 22:21:24 -0700
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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,

I was not at the last meeting, so I maybe missing some discussion.   
Sorry for the absence.

However:
Is it going to be the only solution draft for the transport?

Other question is:
Did the WG well study requirements for the transport? and draft- 
soliman meets the requirements?

thanks,
Koshiro



On 2007/08/02, at 12:54, Nicolas Montavont wrote:

> During the meeting, chairs asked the attendees if
>
> draft-soliman-monami6-flow-binding-04.txt
>
> shall be accepted for the transport of the policies as described in  
> the 4th WG item
>
> [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. The solution involves two  
> specifications, one for the policy format and another for its  
> transport [both Standard Track]
>
> To this question, nobody voted against at the last Monami6 meeting.  
> So, we would like to confirm this decision on the ML.
>
> If you have a specific concern with this decision, please express  
> your views until 12:01 am UTC Thursday, August the 16th, 2007
>
> Regards,
> the chairs
>
> _______________________________________________
> 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 Aug 03 05:06:06 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGt6i-0006sz-VG; Fri, 03 Aug 2007 05:06:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGt6h-0006ss-JH
	for monami6@ietf.org; Fri, 03 Aug 2007 05:06:03 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGt6h-00038k-1F
	for monami6@ietf.org; Fri, 03 Aug 2007 05:06:03 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with
	ESMTP id l7395xqv029029
	for <monami6@ietf.org>; Fri, 3 Aug 2007 11:05:59 +0200
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr
	[192.44.77.4])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2007.03.20) with
	ESMTP id l7395sex029014
	for <monami6@ietf.org>; Fri, 3 Aug 2007 11:05:54 +0200
Received: from [192.168.0.2] (lns-bzn-30-82-253-130-174.adsl.proxad.net
	[82.253.130.174]) (authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	l7395rYT019863
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <monami6@ietf.org>; Fri, 3 Aug 2007 11:05:54 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <50420C24-D620-45EF-9BFA-0D15E80FB73B@sfc.wide.ad.jp>
References: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
	<50420C24-D620-45EF-9BFA-0D15E80FB73B@sfc.wide.ad.jp>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CE05FFCD-8599-4848-B068-E7A1B9DBC9F3@enst-bretagne.fr>
Content-Transfer-Encoding: 7bit
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Subject: Re: [Monami6] consensus call on
	draft-soliman-monami6-flow-binding-04.txt
Date: Fri, 3 Aug 2007 11:13:07 +0200
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
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

Hi Koshiro,

On Aug 3, 2007, at 7:21 AM, Koshiro MITSUYA wrote:

> Hi,
>
> I was not at the last meeting, so I maybe missing some discussion.   
> Sorry for the absence.
>
> However:
> Is it going to be the only solution draft for the transport?

Yes

>
> Other question is:
> Did the WG well study requirements for the transport? and draft- 
> soliman meets the requirements?

Yes, we discussed this at IETF 68, and had a rough consensus on the  
solution proposed by draft-soliman. We said that a transport within  
the mobility messages was the most straight forward solution and can  
benefit from the security already in place by MIPv6.

Regards,

Nicolas

>
> thanks,
> Koshiro
>
>
>
> On 2007/08/02, at 12:54, Nicolas Montavont wrote:
>
>> During the meeting, chairs asked the attendees if
>>
>> draft-soliman-monami6-flow-binding-04.txt
>>
>> shall be accepted for the transport of the policies as described  
>> in the 4th WG item
>>
>> [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. The solution involves  
>> two specifications, one for the policy format and another for its  
>> transport [both Standard Track]
>>
>> To this question, nobody voted against at the last Monami6  
>> meeting. So, we would like to confirm this decision on the ML.
>>
>> If you have a specific concern with this decision, please express  
>> your views until 12:01 am UTC Thursday, August the 16th, 2007
>>
>> Regards,
>> the chairs
>>
>> _______________________________________________
>> 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 mext-bounces@ietf.org Sun Aug 05 15:28:20 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHllg-00013Y-7V; Sun, 05 Aug 2007 15:28:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHlle-00013R-GT
	for mext@ietf.org; Sun, 05 Aug 2007 15:27:58 -0400
Received: from amailer.gwdg.de ([134.76.10.18])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IHlld-0000Qa-NS
	for mext@ietf.org; Sun, 05 Aug 2007 15:27:58 -0400
Received: from p5b03af08.dip0.t-ipconnect.de ([91.3.175.8]
	helo=[192.168.0.183])
	by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66)
	(envelope-from <fu@cs.uni-goettingen.de>) id 1IHllc-0000TZ-2c
	for mext@ietf.org; Sun, 05 Aug 2007 21:27:56 +0200
Message-ID: <46B624B8.7090901@cs.uni-goettingen.de>
Date: Sun, 05 Aug 2007 21:27:52 +0200
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated: Id:xfu
X-Spam-Level: -
X-Virus-Scanned: (clean) by exiscan+sophie
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Subject: [MEXT] Call for participation: MobiArch'07
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Dear all,

Hope the following workshop call for participation be of interest for 
the group here.

Best regards,
Xiaoming
-------------------------------------------------------------------------------------------------------------------------
CALL FOR PARTICIPATION
---------------------------------------------------------------------------------------------------
MobiArch 2007 - The Second International Workshop on Mobility in the
Evolving Internet Architecture, August 27, 2007, Kyoto, Japan
sponsored by ACM SIGCOMM
in cooperation with ACM SIGMOBILE
http://www.sigcomm.org/sigcomm2007/mobiarch/

in conjunction with ACM SIGCOMM 2007, August 27-31, 2007
---------------------------------------------------------------------------------------------------

Two keynotes will be speaking on latest advances and selected topics in
the emerging and future wireless/mobile network architectures. They are:

     Krishan K. Sabnani (Bell Labs): Key Technologies and Architectures
for the Next-Generation Mobile Networks

     Victor Bahl (Microsoft Research): Are Self Managing Networks in Our
Future?

Further information please find in
http://user.informatik.uni-goettingen.de/~mobiarch/2007/keynote.html

Besides presentations and discussions of 11 technical papers selected
through a rigorous peer-review process, there will be a panel session on
the deployment issues of 4G and beyond, led by active researchers from
both the industry and academia.

Registration information is available at
http://www.sigcomm.org/sigcomm2007/registration.html

We look forward to seeing you at the MobiArch'07 workshop in three weeks!

- The MobiArch'07 organizating team
---------------------------------------------------------------------------------------------------
MobiArch'07 Program
http://user.informatik.uni-goettingen.de/~mobiarch/2007/#program

9:00 - 9:10 Welcome messages and introduction: Chairs

9:10 - 10:05 Session "Mobility Architectures"

     Mobility as an Integrated Service Through the Use of Naming
        Randall Atkinson (Extreme Networks, USA); Saleem Bhatti
(University of St Andrews, United Kingdom); Stephen Hailes (University
College London, United Kingdom)

     An Architecture for Seamless Mobility in Spontaneous Wireless Mesh
Networks
         Franck Rousseau (IMAG, France); Martin Heusse (LSR IMAG,
France); Yan Grunenberger (LSR Laboratory, France); Vincent Untz
(LSR-IMAG Laboratory, France); Eryk Schiller (INPG - Institut National
Politechnique, France); Paul Starzetz (LSR, France); Fabrice Theoleyre
(INP Grenoble, France); Olivier Alphand (INP Grenoble, France); Andrzej
Duda (INP Grenoble, LIG Laboratory, France)

     A Framework for Evolutionary Networking
         Gautam Gupta (Indian Institute of Technology Madras, India);
S.v. Raghavan (Indian Institute of Technology, Madras, Chennai, India)

10:05 - 11:00 Keynote speech 1

11:15 - 12:10 Session "Locator/Identifier Separation"

     Performance of Host Identity Protocol on Lightweight Hardware
         Andrey Khurri (HIIT, Finland); Ekaterina Vorobyeva (HIIT,
Finland); Andrei Gurtov (Helsinki Institute for Information Technology,
Finland)

     Evaluating the Benefits of the Locator/Identifier Separation
         Bruno Quoitin (Universite Catholique de Louvain, Belgium);
Luigi Iannone (Université Catholique de Louvain, Belgium); Cédric de
Launois (Université catholique de Louvain, Belgium); Olivier Bonaventure
(Université Catholique de Louvain, Belgium)

     Embedding Identity in Mobile Environments
         Rui Aguiar (Universidade de Aveiro, Portugal); Alfredo Matos
(Universidade de Aveiro, Portugal); Susana Sargento (Universidade de
Aveiro, Portugal, Portugal)

13:15 - 13:50 Session "Delay Tolerant Networks"

     Distributed Community Detection in Delay Tolerant Networks
         Pan Hui (Univeristy of Cambridge, United Kingdom); Eiko Yoneki
(University of Cambridge, United Kingdom); Shu-Yan Chan (University of
Cambridge, United Kingdom); Jon Crowcroft (University of Cambridge,
United Kingdom)

     Redundancy and Distributed Caching in Mobile DTNs
         Mikko Pitkanen (Helsinki Institute of Physics, Finland); Joerg
Ott (Helsinki University of Technology, Finland)

13:55 - 14:50 Keynote speech 2

15:05 - 16:00 Panel session: Stagnation of deployment of 4G and beyond?
Chair:  Ryuji Wakikawa (Keio University, JP)
Panelists:
         Lars Eggert (Nokia Research Center, FI)
         Yoshiro Ohba (Toshiba Research, US)
         Joerg Ott (Helsinki University of Technology, FI)
         K. K. Ramakrishnan (AT&T Labs, US)
         Jun Takei (Intel Corporation, JP)

16:05 - 17:00 Session "Handover, Multihoming and Data Management"

     Kerberized Handover Keying: A Media-Independent Handover Key
Management Architecture
         Yoshihiro Ohba (TARI, USA); Subir Das (Telcordia Technologies,
USA); Ashutosh Dutta (Telcordia Technologies, USA)

     A Policy Management Framework for Flow Distribution on Multihomed
End Nodes
         Koshiro Mitsuya (Keio University, Japan); Romain Kuntz (Louis
Pasteur University, France); Shinta Sugimoto (Keio University, Japan);
Ryuji Wakikawa (Keio University, Japan); Jun Murai (Keio University, Japan)

     The Case for a Unified Extensible Data-centric Mobility
Infrastructure
         Yun Mao (University of Pennsylvania, USA); Boon Thau Loo
(University of Pennsylvania, USA); Zachary Ives (University of
Pennsylvania, USA);  Jonathan Smith (University of Pennsylvania, USA)








_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From monami6-bounces@ietf.org Mon Aug 06 01:05:35 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHumY-0004Wa-V8; Mon, 06 Aug 2007 01:05:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHumX-0004WV-MG
	for monami6@ietf.org; Mon, 06 Aug 2007 01:05:30 -0400
Received: from mail.sfc.wide.ad.jp ([2001:200:0:8803:203:47ff:fedf:73a6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IHumW-0003cs-Ed
	for monami6@ietf.org; Mon, 06 Aug 2007 01:05:29 -0400
Received: from [192.168.1.117] (c-67-189-100-226.hsd1.or.comcast.net
	[67.189.100.226])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D14494D86B;
	Mon,  6 Aug 2007 14:05:25 +0900 (JST)
In-Reply-To: <CE05FFCD-8599-4848-B068-E7A1B9DBC9F3@enst-bretagne.fr>
References: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
	<50420C24-D620-45EF-9BFA-0D15E80FB73B@sfc.wide.ad.jp>
	<CE05FFCD-8599-4848-B068-E7A1B9DBC9F3@enst-bretagne.fr>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <31DF5A19-40D8-4BD1-891A-E1056C778EEA@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Koshiro MITSUYA <mitsuya@sfc.wide.ad.jp>
Subject: Re: [Monami6] consensus call on
	draft-soliman-monami6-flow-binding-04.txt
Date: Sun, 5 Aug 2007 22:05:23 -0700
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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 Nicolas,

Thank you for your quick response.
Please find my comments inline.


On 2007/08/03, at 2:13, Nicolas Montavont wrote:

> Hi Koshiro,
>
> On Aug 3, 2007, at 7:21 AM, Koshiro MITSUYA wrote:
>
>> Hi,
>>
>> I was not at the last meeting, so I maybe missing some  
>> discussion.  Sorry for the absence.
>>
>> However:
>> Is it going to be the only solution draft for the transport?
>
> Yes

OK, you mean the WG accepts only this draft as the transport solution  
and no other transport solutions will be published from the WG.  I  
then disagree, because draft-soliman does not provide a network- 
initiated filter transport, and because BU/BA needs to carry  
additional error handling for the policy exchange (e.g. In the case  
of error and MN want to try to send policy again, additional BU/BA  
will be required although CoA is successfully installed).


>>
>> Other question is:
>> Did the WG well study requirements for the transport? and draft- 
>> soliman meets the requirements?
>
> Yes, we discussed this at IETF 68, and had a rough consensus on the  
> solution proposed by draft-soliman. We said that a transport within  
> the mobility messages was the most straight forward solution and  
> can benefit from the security already in place by MIPv6.
>

Yes, I agree that a transport within the mobility messages can  
benefit from the security and it is good.

What about defining a new mobility message (not a mobility option as  
today) for filter rules transport?  If it's a mobility option, the  
option always needs to carry within BU/BA.  But if it an message, MN/ 
HA can exchange filter rules independently of BU/BA exchange, and  
still can benefit from security already in place by MIPv6.

regards,
Koshiro


> Regards,
>
> Nicolas
>
>>
>> thanks,
>> Koshiro
>>
>>
>>
>> On 2007/08/02, at 12:54, Nicolas Montavont wrote:
>>
>>> During the meeting, chairs asked the attendees if
>>>
>>> draft-soliman-monami6-flow-binding-04.txt
>>>
>>> shall be accepted for the transport of the policies as described  
>>> in the 4th WG item
>>>
>>> [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. The solution  
>>> involves two specifications, one for the policy format and  
>>> another for its transport [both Standard Track]
>>>
>>> To this question, nobody voted against at the last Monami6  
>>> meeting. So, we would like to confirm this decision on the ML.
>>>
>>> If you have a specific concern with this decision, please express  
>>> your views until 12:01 am UTC Thursday, August the 16th, 2007
>>>
>>> Regards,
>>> the chairs
>>>
>>> _______________________________________________
>>> 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 Mon Aug 13 03:56:07 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKUmU-0000qF-41; Mon, 13 Aug 2007 03:56:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKUmT-0000q9-25
	for monami6@ietf.org; Mon, 13 Aug 2007 03:56:05 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKUmS-0003jn-C7
	for monami6@ietf.org; Mon, 13 Aug 2007 03:56:04 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	l7D7tw7r002698
	for <monami6@ietf.org>; Mon, 13 Aug 2007 16:55:58 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	l7D7twT17907
	for <monami6@ietf.org>; Mon, 13 Aug 2007 16:55:58 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/dodgers) with ESMTP id
	l7D7tvY09602
	for <monami6@ietf.org>; Mon, 13 Aug 2007 16:55:58 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Aug 2007 15:55:24 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Mon, 13 Aug 2007 15:55:20 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Mon, 13 Aug 2007 15:55:20 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'Monami6 WG'" <monami6@ietf.org>
Date: Mon, 13 Aug 2007 15:55:14 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <007c01c7dd7f$48591050$d90b30f0$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcfdedLnRHWhX20LTOK2uaB8S7GsswAAlTpg
Content-Language: en-us
X-OriginalArrivalTime: 13 Aug 2007 07:55:24.0829 (UTC)
	FILETIME=[4E577CD0:01C7DD7F]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Monami6] CoA verification for HA
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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 have a comment for the monami6-mipv6 analysis draft.
 
RFC 3775 permits MN to have only a single CoA binding at HA at any given
time. So this means if MN (attacker) set ups a DoS on a victim (using
victim's address as CoA), MN can no longer communicate with other nodes
using his HoA. However, in simultaneous bindings, MN can set up DoS attack
on multiple victims, and yet retain one real CoA for communication with
other nodes (possibly HA, to alter filter settings to change victim's
address). 

Do we need to consider some form of CoA verification being performed by HA?
 
Regards,
Benjamin Lim



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



From monami6-bounces@ietf.org Thu Aug 16 05:35:35 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILblM-00009O-8J; Thu, 16 Aug 2007 05:35:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILblL-0008Vo-G7
	for monami6@ietf.org; Thu, 16 Aug 2007 05:35:31 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILblK-0008O0-IY
	for monami6@ietf.org; Thu, 16 Aug 2007 05:35:31 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMV00B3L14PFI@szxga02-in.huawei.com> for
	monami6@ietf.org; Thu, 16 Aug 2007 17:31:37 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMV008PP14P1E@szxga02-in.huawei.com> for
	monami6@ietf.org; Thu, 16 Aug 2007 17:31:37 +0800 (CST)
Received: from x49105 ([10.111.12.54])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JMV0005514KRT@szxml04-in.huawei.com> for
	monami6@ietf.org; Thu, 16 Aug 2007 17:31:36 +0800 (CST)
Date: Thu, 16 Aug 2007 17:31:33 +0800
From: Sam Xia <xiazhongqi@huawei.com>
In-reply-to: <E1IKcLE-0003ul-75@megatron.ietf.org>
To: benjamin.limck@sg.panasonic.com
Message-id: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcfdwxhW0Z6Qmci3TteUguSXC4yJ9gCJKYSA
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: monami6@ietf.org
Subject: [Monami6] RE:CoA verification for HA
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 have a comment for the monami6-mipv6 analysis draft.
>  
> RFC 3775 permits MN to have only a single CoA binding at HA 
> at any given time. So this means if MN (attacker) set ups a 
> DoS on a victim (using victim's address as CoA), MN can no 
> longer communicate with other nodes using his HoA. However, 
> in simultaneous bindings, MN can set up DoS attack on 
> multiple victims, and yet retain one real CoA for 
> communication with other nodes (possibly HA, to alter filter 
> settings to change victim's address). 
> 
> Do we need to consider some form of CoA verification being 
> performed by HA?

Sam.Xia> CoA binding has been authencticated by some other means, such as
IPsec or RFC4285.

>  
> Regards,
> Benjamin Lim
> 
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
> 
> 
> End of Monami6 Digest, Vol 30, Issue 4
> **************************************
> 



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



From monami6-bounces@ietf.org Thu Aug 16 05:59:27 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILc8P-00015S-Rd; Thu, 16 Aug 2007 05:59:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILc8P-00015M-0P
	for monami6@ietf.org; Thu, 16 Aug 2007 05:59:21 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILc8N-00014b-2W
	for monami6@ietf.org; Thu, 16 Aug 2007 05:59:20 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	l7G9xGgk000533; Thu, 16 Aug 2007 18:59:16 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	l7G9xGD13904; Thu, 16 Aug 2007 18:59:16 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/indians) with ESMTP id
	l7G9xGr17343; Thu, 16 Aug 2007 18:59:17 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 16 Aug 2007 17:58:40 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Thu, 16 Aug 2007 17:58:35 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Thu, 16 Aug 2007 17:58:35 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: <monami6@ietf.org>
References: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
In-Reply-To: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
Date: Thu, 16 Aug 2007 17:58:29 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcfdwxhW0Z6Qmci3TteUguSXC4yJ9gCJKYSAAADF1gA=
Content-Language: en-us
X-OriginalArrivalTime: 16 Aug 2007 09:58:40.0392 (UTC)
	FILETIME=[05AE1880:01C7DFEC]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 'Sam Xia' <xiazhongqi@huawei.com>
Subject: [Monami6] RE: CoA verification for HA
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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 have a comment for the monami6-mipv6 analysis draft.
> >
> > RFC 3775 permits MN to have only a single CoA binding at HA
> > at any given time. So this means if MN (attacker) set ups a
> > DoS on a victim (using victim's address as CoA), MN can no
> > longer communicate with other nodes using his HoA. However,
> > in simultaneous bindings, MN can set up DoS attack on
> > multiple victims, and yet retain one real CoA for
> > communication with other nodes (possibly HA, to alter filter
> > settings to change victim's address).
> >
> > Do we need to consider some form of CoA verification being
> > performed by HA?
> 
> Sam.Xia> CoA binding has been authencticated by some other means, such as
> IPsec or RFC4285.
[Ben] I am talking more on path verification. Yes HA can authenticate that
MN is a valid user to bind CoA at it. But HA cannot be sure if this MN is
binding 'fake' CoAs that does not belong to MN. If no path verification is
done by HA, MN can use these 'fake' CoAs to launch DoS attacks.

Regards,
Benjamin Lim



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



From monami6-bounces@ietf.org Thu Aug 16 16:25:31 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILluL-0003s7-BH; Thu, 16 Aug 2007 16:25:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILluJ-0003s1-Ix
	for monami6@ietf.org; Thu, 16 Aug 2007 16:25:27 -0400
Received: from wa-out-1112.google.com ([209.85.146.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILluI-0002VU-BP
	for monami6@ietf.org; Thu, 16 Aug 2007 16:25:27 -0400
Received: by wa-out-1112.google.com with SMTP id j37so486548waf
	for <monami6@ietf.org>; Thu, 16 Aug 2007 13:25:25 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=VDwZDPbFy97u16G7st3QH3xogy3Z9377cqZlbBK9V48CAeVx9mmxaKEJ/jMH8yuCxRjAf4lxB3FQ4uYYxlIooMt7sgeIYKUsaxnACb9JD8p9OXcZCeusrS6PqsPu1lcoWMVWy8OphgDlb9IELvgWjxE9OJ7WQTPxDsEJbCSZXoo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=cVcHvOAgIM86IVSCYo+TO6m6PE0F46u4JDpCYyLaW7ipKoUSIVfq27VLeZAp6riPi9dmCjQ1E3+0KM41gYHgj+71WHAiXSTTYAVAHK1r2vtPpkTo7XFG85W0ki3SPxXGPkpk6HWelUriBQxyhhA065pdF4b91O2r3pfmmLGc7L4=
Received: by 10.114.168.1 with SMTP id q1mr2357531wae.1187295925313;
	Thu, 16 Aug 2007 13:25:25 -0700 (PDT)
Received: from ?133.27.62.74? ( [133.27.62.74])
	by mx.google.com with ESMTPS id k26sm1846712waf.2007.08.16.13.25.23
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 16 Aug 2007 13:25:24 -0700 (PDT)
In-Reply-To: <005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
References: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
	<005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F602133F-66BE-4EE4-BE60-78EDE0D9BA2D@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Monami6] RE: CoA verification for HA
Date: Fri, 17 Aug 2007 05:25:11 +0900
To: benjamin.limck@sg.panasonic.com,
 Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 'Sam Xia' <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 Benjamin,

This problem is not specific to monami6, but more general issue of MIP6.
However, I'm not sure this is real scenario, because MN must establish
SA before sending BU... MN is always identified by HA before sending BU.

ryuji


On 2007/08/16, at 18:58, Benjamin Lim wrote:

> Hi,
>
>>> I have a comment for the monami6-mipv6 analysis draft.
>>>
>>> RFC 3775 permits MN to have only a single CoA binding at HA
>>> at any given time. So this means if MN (attacker) set ups a
>>> DoS on a victim (using victim's address as CoA), MN can no
>>> longer communicate with other nodes using his HoA. However,
>>> in simultaneous bindings, MN can set up DoS attack on
>>> multiple victims, and yet retain one real CoA for
>>> communication with other nodes (possibly HA, to alter filter
>>> settings to change victim's address).
>>>
>>> Do we need to consider some form of CoA verification being
>>> performed by HA?
>>
>> Sam.Xia> CoA binding has been authencticated by some other means,  
>> such as
>> IPsec or RFC4285.
> [Ben] I am talking more on path verification. Yes HA can  
> authenticate that
> MN is a valid user to bind CoA at it. But HA cannot be sure if this  
> MN is
> binding 'fake' CoAs that does not belong to MN. If no path  
> verification is
> done by HA, MN can use these 'fake' CoAs to launch DoS attacks.
>
> Regards,
> Benjamin Lim
>
>
>
> _______________________________________________
> 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 Aug 17 01:17:42 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILuDM-0005QN-V5; Fri, 17 Aug 2007 01:17:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILuDM-0005Px-03
	for monami6@ietf.org; Fri, 17 Aug 2007 01:17:40 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILuDL-0002GO-46
	for monami6@ietf.org; Fri, 17 Aug 2007 01:17:39 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/bulls) with ESMTP id
	l7H5HPgB000317; Fri, 17 Aug 2007 14:17:25 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	l7H5HQJ02948; Fri, 17 Aug 2007 14:17:26 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/whitesox) with ESMTP id
	l7H5HQm23408; Fri, 17 Aug 2007 14:17:26 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 17 Aug 2007 13:16:49 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Fri, 17 Aug 2007 13:16:36 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Fri, 17 Aug 2007 13:16:36 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'RYUJI WAKIKAWA'" <ryuji.wakikawa@gmail.com>
References: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
	<005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
	<F602133F-66BE-4EE4-BE60-78EDE0D9BA2D@gmail.com>
In-Reply-To: <F602133F-66BE-4EE4-BE60-78EDE0D9BA2D@gmail.com>
Subject: RE: [Monami6] RE: CoA verification for HA
Date: Fri, 17 Aug 2007 13:16:30 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <000a01c7e08d$c520f330$4f62d990$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcfgQ4J8yh6kqfdgR1OnfUhHYBhE5AAPrirA
Content-Language: en-us
X-OriginalArrivalTime: 17 Aug 2007 05:16:49.0815 (UTC)
	FILETIME=[D09A9270:01C7E08D]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 'Monami6 WG' <monami6@ietf.org>, 'Sam Xia' <xiazhongqi@huawei.com>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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,

[snip]
> This problem is not specific to monami6, but more general issue of MIP6.
[Ben] Not really. I feel the issue should be view as so:- 

1) Degree of threat. 
In MIP6, an attacker can only launch a single DoS attack. But in Monami6,
due to multiple CoA bindings support, an attacker can launch multiple DoS
attack.

2) Form of threat. 
In MIP6, once the attacker launch the DoS, the attacker loses communication
means (as the HoA, CoA binding is taken up for attack). However, in Monami6,
one of the multiple CoAs can be used by the attacker to control the DoS
attack for the other CoA bindings. (e.g. set filter rules at HA)

> However, I'm not sure this is real scenario, because MN must establish
> SA before sending BU... MN is always identified by HA before sending BU.
[Ben] The CoA used for binding at HA need not be the source address of the
BU. i.e. AltCoA option, BUI option. So does this means HA should trust the
CoAs in such options?

Regards,
Benjamin Lim

> 
> ryuji
> 
> 
> On 2007/08/16, at 18:58, Benjamin Lim wrote:
> 
> > Hi,
> >
> >>> I have a comment for the monami6-mipv6 analysis draft.
> >>>
> >>> RFC 3775 permits MN to have only a single CoA binding at HA
> >>> at any given time. So this means if MN (attacker) set ups a
> >>> DoS on a victim (using victim's address as CoA), MN can no
> >>> longer communicate with other nodes using his HoA. However,
> >>> in simultaneous bindings, MN can set up DoS attack on
> >>> multiple victims, and yet retain one real CoA for
> >>> communication with other nodes (possibly HA, to alter filter
> >>> settings to change victim's address).
> >>>
> >>> Do we need to consider some form of CoA verification being
> >>> performed by HA?
> >>
> >> Sam.Xia> CoA binding has been authencticated by some other means,
> >> such as
> >> IPsec or RFC4285.
> > [Ben] I am talking more on path verification. Yes HA can
> > authenticate that
> > MN is a valid user to bind CoA at it. But HA cannot be sure if this
> > MN is
> > binding 'fake' CoAs that does not belong to MN. If no path
> > verification is
> > done by HA, MN can use these 'fake' CoAs to launch DoS attacks.
> >
> > Regards,
> > Benjamin Lim
> >
> >
> >
> > _______________________________________________
> > 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 Aug 17 02:43:06 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILvY0-0002C7-Sj; Fri, 17 Aug 2007 02:43:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILvXz-0002C1-Gd
	for monami6@ietf.org; Fri, 17 Aug 2007 02:43:03 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILvXy-0005L6-Hq
	for monami6@ietf.org; Fri, 17 Aug 2007 02:43:03 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMW00GBPNYIVQ@szxga02-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 14:42:19 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMW00MX0NYIWO@szxga02-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 14:42:18 +0800 (CST)
Received: from x49105 ([10.111.12.54])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JMW00L43NYEJT@szxml04-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 14:42:18 +0800 (CST)
Date: Fri, 17 Aug 2007 14:42:14 +0800
From: Sam Xia <xiazhongqi@huawei.com>
Subject: RE: [Monami6] RE: CoA verification for HA
In-reply-to: <000a01c7e08d$c520f330$4f62d990$%limck@sg.panasonic.com>
To: benjamin.limck@sg.panasonic.com,
	'RYUJI WAKIKAWA' <ryuji.wakikawa@gmail.com>
Message-id: <000001c7e099$bf952830$360c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcfgQ4J8yh6kqfdgR1OnfUhHYBhE5AAPrirAAAV3ImA=
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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,
> 
> [snip]
> > This problem is not specific to monami6, but more general 
> issue of MIP6.
> [Ben] Not really. I feel the issue should be view as so:- 
> 
> 1) Degree of threat. 
> In MIP6, an attacker can only launch a single DoS attack. But 
> in Monami6, due to multiple CoA bindings support, an attacker 
> can launch multiple DoS attack.
> 
> 2) Form of threat. 
> In MIP6, once the attacker launch the DoS, the attacker loses 
> communication means (as the HoA, CoA binding is taken up for 
> attack). However, in Monami6, one of the multiple CoAs can be 
> used by the attacker to control the DoS attack for the other 
> CoA bindings. (e.g. set filter rules at HA)

Sam> Yes. In monami6, attacker can lauch more attack than in mip6. But I
think that it is a general issue for mobile IP.  The real question is that
even HA has authenticated with MN, how can HA believe the   
            CoA in BU is actually belonged to MN. I agree that it is a
issue, not solved by mip6.  Of course, if coa and hoa are both CGA,
verification could be performed.

> 
> > However, I'm not sure this is real scenario, because MN 
> must establish 
> > SA before sending BU... MN is always identified by HA 
> before sending BU.
> [Ben] The CoA used for binding at HA need not be the source 
> address of the BU. i.e. AltCoA option, BUI option. So does 
> this means HA should trust the CoAs in such options?

so, what do you want to do?

Regards,
Sam.Xia.



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



From monami6-bounces@ietf.org Fri Aug 17 04:21:26 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILx5A-00067x-QJ; Fri, 17 Aug 2007 04:21:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILx59-00067q-7w
	for monami6@ietf.org; Fri, 17 Aug 2007 04:21:23 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILx57-0005Bh-BL
	for monami6@ietf.org; Fri, 17 Aug 2007 04:21:23 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/bulls) with ESMTP id
	l7H8LEQ0006337; Fri, 17 Aug 2007 17:21:14 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	l7H8LF916410; Fri, 17 Aug 2007 17:21:15 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/phillies) with ESMTP id
	l7H8LEY15083; Fri, 17 Aug 2007 17:21:14 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 17 Aug 2007 16:20:39 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Fri, 17 Aug 2007 16:20:36 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Fri, 17 Aug 2007 16:20:36 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'Sam Xia'" <xiazhongqi@huawei.com>
References: <000001c7e099$bf952830$360c6f0a@china.huawei.com>
In-Reply-To: <000001c7e099$bf952830$360c6f0a@china.huawei.com>
Subject: RE: [Monami6] RE: CoA verification for HA
Date: Fri, 17 Aug 2007 16:20:29 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <001201c7e0a7$79258210$6b708630$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcfgQ4J8yh6kqfdgR1OnfUhHYBhE5AAPrirAAAV3ImAAASONUA==
Content-Language: en-us
X-OriginalArrivalTime: 17 Aug 2007 08:20:39.0173 (UTC)
	FILETIME=[7E9D0B50:01C7E0A7]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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,

> > [snip]
> > > This problem is not specific to monami6, but more general
> > issue of MIP6.
> > [Ben] Not really. I feel the issue should be view as so:-
> >
> > 1) Degree of threat.
> > In MIP6, an attacker can only launch a single DoS attack. But
> > in Monami6, due to multiple CoA bindings support, an attacker
> > can launch multiple DoS attack.
> >
> > 2) Form of threat.
> > In MIP6, once the attacker launch the DoS, the attacker loses
> > communication means (as the HoA, CoA binding is taken up for
> > attack). However, in Monami6, one of the multiple CoAs can be
> > used by the attacker to control the DoS attack for the other
> > CoA bindings. (e.g. set filter rules at HA)
> 
> Sam> Yes. In monami6, attacker can lauch more attack than in mip6. But I
> think that it is a general issue for mobile IP.  The real question is that
> even HA has authenticated with MN, how can HA believe the
>             CoA in BU is actually belonged to MN. I agree that it is a
> issue, not solved by mip6.  
[Ben] You seem to left out the fact that in Monami6, an attacker can still
be contactable via HoA. This by virtue is not something that cannot be
achieved in MIP6. I illustrate with an example.

An attacker initiates a download for a big file to his MIP6-MN.
Concurrently, MIP6-MN sends BU to HA changing the CoA to a victim's CoA.
Thus, victim is flooded with useless packets. Now to deny service to an
organization, the attacker needs an army of MIP6-MN to perform such attack
in order to shut the system down. Similarly, all MIP6-MN cannot use their
HoA for communication now as it is being used for the attack.

However, if the attacker was using a Monami6-MN, all the attacker needs to
do is to maintain 1 CoA binding with HA (to control where the flows go) and
create other CoA bindings that belong to victims. All this can be done by
just using a single MN as opposed to the army of MNs need when MIP6 is used.
Also, the attacker can still use HoA for communication with other nodes (as
it can setup up flow filtering rules at HA to direct the flows from other
nodes)

> Of course, if coa and hoa are both CGA,
> verification could be performed.
[Ben] I'm not really familiar with CGA, but I thought CGA was more for
address authenticity and not address reach-ability.

> 
> >
> > > However, I'm not sure this is real scenario, because MN
> > must establish
> > > SA before sending BU... MN is always identified by HA
> > before sending BU.
> > [Ben] The CoA used for binding at HA need not be the source
> > address of the BU. i.e. AltCoA option, BUI option. So does
> > this means HA should trust the CoAs in such options?
> 
> so, what do you want to do?
[Ben] Like I said in the first mail, I'm asking if such issue should be
documented into the analysis draft. Of course if the WG feels that such
issue needs to be addressed, solution discussion can be done via the ML.

Regards,
Benjamin Lim

> Regards,
> Sam.Xia.
> 




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



From monami6-bounces@ietf.org Fri Aug 17 05:46:17 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILyPG-0000zd-Dh; Fri, 17 Aug 2007 05:46:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILyPF-0000zX-23
	for monami6@ietf.org; Fri, 17 Aug 2007 05:46:13 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILyPC-0006o8-P8
	for monami6@ietf.org; Fri, 17 Aug 2007 05:46:13 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMW006OEWFQWA@szxga03-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 17:45:26 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JMW005WNWFOI5@szxga03-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 17:45:26 +0800 (CST)
Received: from x49105 ([10.111.12.54])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JMW00568WFLJH@szxml04-in.huawei.com> for
	monami6@ietf.org; Fri, 17 Aug 2007 17:45:24 +0800 (CST)
Date: Fri, 17 Aug 2007 17:45:21 +0800
From: Sam Xia <xiazhongqi@huawei.com>
Subject: RE: [Monami6] RE: CoA verification for HA
In-reply-to: <001201c7e0a7$79258210$6b708630$%limck@sg.panasonic.com>
To: benjamin.limck@sg.panasonic.com
Message-id: <000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcfgQ4J8yh6kqfdgR1OnfUhHYBhE5AAPrirAAAV3ImAAASONUAAFeg8A
X-Spam-Score: 1.2 (+)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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 Ben

> 
> Hi Sam,
> 
> > > [snip]
> > > > This problem is not specific to monami6, but more general
> > > issue of MIP6.
> > > [Ben] Not really. I feel the issue should be view as so:-
> > >
> > > 1) Degree of threat.
> > > In MIP6, an attacker can only launch a single DoS attack. But in 
> > > Monami6, due to multiple CoA bindings support, an attacker can 
> > > launch multiple DoS attack.
> > >
> > > 2) Form of threat.
> > > In MIP6, once the attacker launch the DoS, the attacker loses 
> > > communication means (as the HoA, CoA binding is taken up for 
> > > attack). However, in Monami6, one of the multiple CoAs 
> can be used 
> > > by the attacker to control the DoS attack for the other CoA 
> > > bindings. (e.g. set filter rules at HA)
> > 
> > Sam> Yes. In monami6, attacker can lauch more attack than 
> in mip6. But 
> > Sam> I
> > think that it is a general issue for mobile IP.  The real 
> question is 
> > that even HA has authenticated with MN, how can HA believe the
> >             CoA in BU is actually belonged to MN. I agree 
> that it is a 
> > issue, not solved by mip6.
> [Ben] You seem to left out the fact that in Monami6, an 
> attacker can still be contactable via HoA. This by virtue is 
> not something that cannot be achieved in MIP6. I illustrate 
> with an example.
> 
> An attacker initiates a download for a big file to his MIP6-MN.
> Concurrently, MIP6-MN sends BU to HA changing the CoA to a 
> victim's CoA.
> Thus, victim is flooded with useless packets. Now to deny 
> service to an organization, the attacker needs an army of 
> MIP6-MN to perform such attack in order to shut the system 
> down. Similarly, all MIP6-MN cannot use their HoA for 
> communication now as it is being used for the attack.
> 
> However, if the attacker was using a Monami6-MN, all the 
> attacker needs to do is to maintain 1 CoA binding with HA (to 
> control where the flows go) and create other CoA bindings 
> that belong to victims. All this can be done by just using a 
> single MN as opposed to the army of MNs need when MIP6 is used.
> Also, the attacker can still use HoA for communication with 
> other nodes (as it can setup up flow filtering rules at HA to 
> direct the flows from other
> nodes)

I know what you do mean. there is a bit difference between Monami6 and MIP6.
But I still think that it is a general issue that is how to authenticate
CoA. right?

> 
> > Of course, if coa and hoa are both CGA, verification could be 
> > performed.
> [Ben] I'm not really familiar with CGA, but I thought CGA was 
> more for address authenticity and not address reach-ability.

Sure, CGA can do this. When CoA is CGA, MN can not bind fake CoA to its HoA.

> 
> > 
> > >
> > > > However, I'm not sure this is real scenario, because MN
> > > must establish
> > > > SA before sending BU... MN is always identified by HA
> > > before sending BU.
> > > [Ben] The CoA used for binding at HA need not be the 
> source address 
> > > of the BU. i.e. AltCoA option, BUI option. So does this means HA 
> > > should trust the CoAs in such options?
> > 
> > so, what do you want to do?
> [Ben] Like I said in the first mail, I'm asking if such issue 
> should be documented into the analysis draft. Of course if 
> the WG feels that such issue needs to be addressed, solution 
> discussion can be done via the ML.
> 
> Regards,
> Benjamin Lim
> 
> > Regards,
> > Sam.Xia.
> > 
> 
> 
> 
> 



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



From monami6-bounces@ietf.org Sat Aug 18 02:33:37 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMHsN-00032c-9I; Sat, 18 Aug 2007 02:33:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMHsL-00032C-Q2
	for monami6@ietf.org; Sat, 18 Aug 2007 02:33:33 -0400
Received: from fk-out-0910.google.com ([209.85.128.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMHsK-0002HZ-9O
	for monami6@ietf.org; Sat, 18 Aug 2007 02:33:33 -0400
Received: by fk-out-0910.google.com with SMTP id z23so655274fkz
	for <monami6@ietf.org>; Fri, 17 Aug 2007 23:33:31 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=DI+WyhCsIVqn217KKGDR9lFMBVo+Zqlgp7EHarD+zc68i3Q4VTp0zIABIMHGU67nOyoZpCMgU1PsSd9he1zDiuJKjFL5yDkBPvQ3YVkHF5wPrgV/2yLaHdeiOVFyod8avnsYIiGNcRugJu+H3nQj2dLi4Up8PjS3YJqTJKiaVyU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=lTdIbQb0/e9TB23IdPjX5ymcHntdwplipPIxThgll8E3vbDRSxr8EPkTtRyf/O/pBbYAfJm8G6lnHNbOnQzY4mTvCkzOL5YS8neBJS+hspFMM+YPjWVOmAilGNVad8SANb+0OMOF4rza/xDPQNAa6uLmry9s72ysuVIy1Zepw2M=
Received: by 10.78.160.4 with SMTP id i4mr1231256hue.1187418811240;
	Fri, 17 Aug 2007 23:33:31 -0700 (PDT)
Received: from ?203.178.135.119? ( [203.178.135.119])
	by mx.google.com with ESMTPS id 32sm1141938hui.2007.08.17.23.33.23
	(version=TLSv1/SSLv3 cipher=OTHER);
	Fri, 17 Aug 2007 23:33:25 -0700 (PDT)
In-Reply-To: <000a01c7e08d$c520f330$4f62d990$@limck@sg.panasonic.com>
References: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
	<005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
	<F602133F-66BE-4EE4-BE60-78EDE0D9BA2D@gmail.com>
	<000a01c7e08d$c520f330$4f62d990$@limck@sg.panasonic.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C4AE04D2-1943-4DE7-BE95-E7659FDBCC70@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Monami6] RE: CoA verification for HA
Date: Sat, 18 Aug 2007 15:33:10 +0900
To: <benjamin.limck@sg.panasonic.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: 'Monami6 WG' <monami6@ietf.org>, 'Sam Xia' <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


On 2007/08/17, at 14:16, Benjamin Lim wrote:

> Hi Ryuji,
>
> [snip]
>> This problem is not specific to monami6, but more general issue of  
>> MIP6.
> [Ben] Not really. I feel the issue should be view as so:-
>
> 1) Degree of threat.
> In MIP6, an attacker can only launch a single DoS attack. But in  
> Monami6,
> due to multiple CoA bindings support, an attacker can launch  
> multiple DoS
> attack.
>
> 2) Form of threat.
> In MIP6, once the attacker launch the DoS, the attacker loses  
> communication
> means (as the HoA, CoA binding is taken up for attack). However, in  
> Monami6,
> one of the multiple CoAs can be used by the attacker to control the  
> DoS
> attack for the other CoA bindings. (e.g. set filter rules at HA)
>
>> However, I'm not sure this is real scenario, because MN must  
>> establish
>> SA before sending BU... MN is always identified by HA before  
>> sending BU.
> [Ben] The CoA used for binding at HA need not be the source address  
> of the
> BU. i.e. AltCoA option, BUI option. So does this means HA should  
> trust the
> CoAs in such options?

No, but MN is authenticated at this point.
Why will MN try to cheat CoA even if it is authenticated by HA...
Will you do bank robber with your name tag-on? :-)

ryuji

> Regards,
> Benjamin Lim
>
>>
>> ryuji
>>
>>
>> On 2007/08/16, at 18:58, Benjamin Lim wrote:
>>
>>> Hi,
>>>
>>>>> I have a comment for the monami6-mipv6 analysis draft.
>>>>>
>>>>> RFC 3775 permits MN to have only a single CoA binding at HA
>>>>> at any given time. So this means if MN (attacker) set ups a
>>>>> DoS on a victim (using victim's address as CoA), MN can no
>>>>> longer communicate with other nodes using his HoA. However,
>>>>> in simultaneous bindings, MN can set up DoS attack on
>>>>> multiple victims, and yet retain one real CoA for
>>>>> communication with other nodes (possibly HA, to alter filter
>>>>> settings to change victim's address).
>>>>>
>>>>> Do we need to consider some form of CoA verification being
>>>>> performed by HA?
>>>>
>>>> Sam.Xia> CoA binding has been authencticated by some other means,
>>>> such as
>>>> IPsec or RFC4285.
>>> [Ben] I am talking more on path verification. Yes HA can
>>> authenticate that
>>> MN is a valid user to bind CoA at it. But HA cannot be sure if this
>>> MN is
>>> binding 'fake' CoAs that does not belong to MN. If no path
>>> verification is
>>> done by HA, MN can use these 'fake' CoAs to launch DoS attacks.
>>>
>>> Regards,
>>> Benjamin Lim
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 Sat Aug 18 02:37:44 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMHwN-0005dO-MF; Sat, 18 Aug 2007 02:37:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMHwM-0005cC-0L
	for monami6@ietf.org; Sat, 18 Aug 2007 02:37:42 -0400
Received: from mu-out-0910.google.com ([209.85.134.191])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMHwL-0002iW-BO
	for monami6@ietf.org; Sat, 18 Aug 2007 02:37:41 -0400
Received: by mu-out-0910.google.com with SMTP id w8so942033mue
	for <monami6@ietf.org>; Fri, 17 Aug 2007 23:37:40 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=PkUlq6fbFyEnQnpU7awp+hCunXLIIqjiZclELpDhn+l7froCLFmIrb9PJJQG3jwnXuyWjbvWPwf7UUJD487ll0Zye1gQBvm4w/Rlb8UFNxEvfgP63JsZT9R2MQ507T5M3AMBvbZlaVsczD1+lPS7bYQCikzWpr3v9r7Esoiauu8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=tIrSEU9uErvfxsd4Af/RwLEc4BPsR7J//XS9xuIbf3wssvkeOHrQV88WGtC1G2grYUSu8c2mGdqZFhHRDMNcWLqDPqWmJLK/tMaVCR71bJjcinH3IgOx37wYvRvfhgErYfCOwQVcINvcMfa/i/9csyedOGsXheKZbf+1aSJc4XQ=
Received: by 10.78.183.8 with SMTP id g8mr1228390huf.1187419060416;
	Fri, 17 Aug 2007 23:37:40 -0700 (PDT)
Received: from ?203.178.135.119? ( [203.178.135.119])
	by mx.google.com with ESMTPS id 35sm1149695huc.2007.08.17.23.37.27
	(version=TLSv1/SSLv3 cipher=OTHER);
	Fri, 17 Aug 2007 23:37:30 -0700 (PDT)
In-Reply-To: <000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
References: <000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5FBD4CFC-7649-459C-B5BA-DFAF4ED72DB7@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Monami6] RE: CoA verification for HA
Date: Sat, 18 Aug 2007 15:37:15 +0900
To: Sam Xia <xiazhongqi@huawei.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
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 Sam and Benjamin

On 2007/08/17, at 18:45, Sam Xia wrote:

> Hi Ben
>
>>
>> Hi Sam,
>>
>>>> [snip]
>>>>> This problem is not specific to monami6, but more general
>>>> issue of MIP6.
>>>> [Ben] Not really. I feel the issue should be view as so:-
>>>>
>>>> 1) Degree of threat.
>>>> In MIP6, an attacker can only launch a single DoS attack. But in
>>>> Monami6, due to multiple CoA bindings support, an attacker can
>>>> launch multiple DoS attack.
>>>>
>>>> 2) Form of threat.
>>>> In MIP6, once the attacker launch the DoS, the attacker loses
>>>> communication means (as the HoA, CoA binding is taken up for
>>>> attack). However, in Monami6, one of the multiple CoAs
>> can be used
>>>> by the attacker to control the DoS attack for the other CoA
>>>> bindings. (e.g. set filter rules at HA)
>>>
>>> Sam> Yes. In monami6, attacker can lauch more attack than
>> in mip6. But
>>> Sam> I
>>> think that it is a general issue for mobile IP.  The real
>> question is
>>> that even HA has authenticated with MN, how can HA believe the
>>>             CoA in BU is actually belonged to MN. I agree
>> that it is a
>>> issue, not solved by mip6.
>> [Ben] You seem to left out the fact that in Monami6, an
>> attacker can still be contactable via HoA. This by virtue is
>> not something that cannot be achieved in MIP6. I illustrate
>> with an example.
>>
>> An attacker initiates a download for a big file to his MIP6-MN.
>> Concurrently, MIP6-MN sends BU to HA changing the CoA to a
>> victim's CoA.
>> Thus, victim is flooded with useless packets. Now to deny
>> service to an organization, the attacker needs an army of
>> MIP6-MN to perform such attack in order to shut the system
>> down. Similarly, all MIP6-MN cannot use their HoA for
>> communication now as it is being used for the attack.
>>
>> However, if the attacker was using a Monami6-MN, all the
>> attacker needs to do is to maintain 1 CoA binding with HA (to
>> control where the flows go) and create other CoA bindings
>> that belong to victims. All this can be done by just using a
>> single MN as opposed to the army of MNs need when MIP6 is used.
>> Also, the attacker can still use HoA for communication with
>> other nodes (as it can setup up flow filtering rules at HA to
>> direct the flows from other
>> nodes)
>
> I know what you do mean. there is a bit difference between Monami6  
> and MIP6.
> But I still think that it is a general issue that is how to  
> authenticate
> CoA. right?

agree.

>>
>>> Of course, if coa and hoa are both CGA, verification could be
>>> performed.
>> [Ben] I'm not really familiar with CGA, but I thought CGA was
>> more for address authenticity and not address reach-ability.
>
> Sure, CGA can do this. When CoA is CGA, MN can not bind fake CoA to  
> its HoA.
>
>>
>>>
>>>>
>>>>> However, I'm not sure this is real scenario, because MN
>>>> must establish
>>>>> SA before sending BU... MN is always identified by HA
>>>> before sending BU.
>>>> [Ben] The CoA used for binding at HA need not be the
>> source address
>>>> of the BU. i.e. AltCoA option, BUI option. So does this means HA
>>>> should trust the CoAs in such options?
>>>
>>> so, what do you want to do?
>> [Ben] Like I said in the first mail, I'm asking if such issue
>> should be documented into the analysis draft. Of course if
>> the WG feels that such issue needs to be addressed, solution
>> discussion can be done via the ML.

I am not sure this is issue, but it may be useful to warn this  
scenario in analysis.
That's fine to me.

regards,
ryuji

>> Regards,
>> Benjamin Lim
>>
>>> Regards,
>>> Sam.Xia.
>>>
>>
>>
>>
>>
>
>


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



From monami6-bounces@ietf.org Sun Aug 19 22:08:07 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMwgR-00070F-Jh; Sun, 19 Aug 2007 22:07:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMwgQ-0006xq-HZ
	for monami6@ietf.org; Sun, 19 Aug 2007 22:07:58 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IMwgP-00005u-MR
	for monami6@ietf.org; Sun, 19 Aug 2007 22:07:58 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/bulls) with ESMTP id
	l7K27ovG015364; Mon, 20 Aug 2007 11:07:50 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx1) with ESMTP id
	l7K27qt19641; Mon, 20 Aug 2007 11:07:52 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/redsox) with ESMTP id
	l7K27pF11148; Mon, 20 Aug 2007 11:07:51 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 10:07:13 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Mon, 20 Aug 2007 10:07:10 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Mon, 20 Aug 2007 10:07:10 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'RYUJI WAKIKAWA'" <ryuji.wakikawa@gmail.com>
References: <000001c7dfe8$3c189840$360c6f0a@china.huawei.com>
	<005b01c7dfeb$ff2aeba0$fd80c2e0$@limck@sg.panasonic.com>
	<F602133F-66BE-4EE4-BE60-78EDE0D9BA2D@gmail.com>
	<000a01c7e08d$c520f330$4f62d990$@limck@sg.panasonic.com>
	<C4AE04D2-1943-4DE7-BE95-E7659FDBCC70@gmail.com>
In-Reply-To: <C4AE04D2-1943-4DE7-BE95-E7659FDBCC70@gmail.com>
Subject: RE: [Monami6] RE: CoA verification for HA
Date: Mon, 20 Aug 2007 10:07:04 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <00e101c7e2ce$cd9cbc90$68d635b0$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcfhYZ+nGWTBb+3hRHyKkP319GIQxQBa6+EA
Content-Language: en-us
X-OriginalArrivalTime: 20 Aug 2007 02:07:13.0518 (UTC)
	FILETIME=[D30AA8E0:01C7E2CE]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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,

[snip]

> No, but MN is authenticated at this point.
> Why will MN try to cheat CoA even if it is authenticated by HA...
> Will you do bank robber with your name tag-on? :-)
[Ben] Why not? Having your identity known does not preclude such action. An
authenticated MN could get infected by a virus that performs such action
unwitting. Furthermore, if an attacker is bent on creating trouble, having
his/her identity known does not really stop their personal agenda (as seen
by some real life events..;p)

Regards,
Benjamin Lim
> 
> ryuji



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



From monami6-bounces@ietf.org Sun Aug 19 22:22:02 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMwtz-0001Ss-N9; Sun, 19 Aug 2007 22:21:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMwty-0001Sk-RI
	for monami6@ietf.org; Sun, 19 Aug 2007 22:21:58 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMwtw-0006iR-Uy
	for monami6@ietf.org; Sun, 19 Aug 2007 22:21:58 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/jazz) with ESMTP id
	l7K2LqPq012020; Mon, 20 Aug 2007 11:21:52 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	l7K2Lr008987; Mon, 20 Aug 2007 11:21:53 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/dodgers) with ESMTP id
	l7K2Lrb20918; Mon, 20 Aug 2007 11:21:53 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.116]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 10:20:47 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Mon, 20 Aug 2007 10:20:44 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Mon, 20 Aug 2007 10:20:44 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'Sam Xia'" <xiazhongqi@huawei.com>
References: <001201c7e0a7$79258210$6b708630$%limck@sg.panasonic.com>
	<000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
In-Reply-To: <000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
Subject: RE: [Monami6] RE: CoA verification for HA
Date: Mon, 20 Aug 2007 10:20:38 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <00e201c7e2d0$b2f89920$18e9cb60$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcfgQ4J8yh6kqfdgR1OnfUhHYBhE5AAPrirAAAV3ImAAASONUAAFeg8AAIcQpYA=
Content-Language: en-us
X-OriginalArrivalTime: 20 Aug 2007 02:20:47.0518 (UTC)
	FILETIME=[B83933E0:01C7E2D0]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, 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,

[snip]
> I know what you do mean. there is a bit difference between Monami6 and
MIP6.
> But I still think that it is a general issue that is how to authenticate
> CoA. right?
[Ben] It could be seen that way. Although I feel that the degree of issue is
more specific to Monami6.

> 
> >
> > > Of course, if coa and hoa are both CGA, verification could be
> > > performed.
> > [Ben] I'm not really familiar with CGA, but I thought CGA was
> > more for address authenticity and not address reach-ability.
> 
> Sure, CGA can do this. When CoA is CGA, MN can not bind fake CoA to its
HoA.
[Ben] I understand now.

Regards,
Benjamin Lim



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



From monami6-bounces@ietf.org Sun Aug 19 22:39:40 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMxB1-00058B-1V; Sun, 19 Aug 2007 22:39:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMxAz-00057w-UO
	for monami6@ietf.org; Sun, 19 Aug 2007 22:39:33 -0400
Received: from mail.sfc.wide.ad.jp ([2001:200:0:8803:203:47ff:fedf:73a6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMxAy-00071i-Aa
	for monami6@ietf.org; Sun, 19 Aug 2007 22:39:33 -0400
Received: from [192.168.1.117] (c-67-189-100-226.hsd1.or.comcast.net
	[67.189.100.226])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D497D4D8C4;
	Mon, 20 Aug 2007 11:39:29 +0900 (JST)
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1IIPpu-0003xs-Mc@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=ISO-2022-JP; delsp=yes; format=flowed
Message-Id: <9A2144E9-BD3E-4CAB-B878-1DBA3E878190@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Koshiro MITSUYA <mitsuya@sfc.wide.ad.jp>
Date: Sun, 19 Aug 2007 19:39:27 -0700
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: 
Subject: [Monami6] Fwd: I-D
	ACTION:draft-mitsuya-monami6-flow-distribution-policy-04.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

Dear Monami6 WG,

We've submitted the new version of draft-mitsuya-monami6-flow- 
distribution-policy.  Any comments are highly welcome!

My request to this WG is to share a common view of a flow  
distribution architecture, as we don't have even common terminologies  
for example what's the difference between policy and filter rule?

What do you think?

regards,
Koshiro



Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 2007$BG/(B8$B7n(B7$BF|(B 7:15:02:PDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-mitsuya-monami6-flow-distribution- 
> policy-04.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: A Policy Data Set for Flow Distribution
> 	Author(s)	: K. Mitsuya, et al.
> 	Filename	: draft-mitsuya-monami6-flow-distribution-policy-04.txt
> 	Pages		: 13
> 	Date		: 2007-8-7
> 	
> The multiple care-of addresses registration protocol [1] allows a
>    mobile node to maintain, at the same time, multiple virtual paths
>    with its home agent or correspondent nodes.  This document  
> presents a
>    policy data set for flow distribution to be used with the multiple
>    care-of addresses registration protocol.  This policy data set
>    defines policies, in an OS-independant manner, for a mobile node  
> and
>    its home agent or correspondent node, from the point of view of one
>    of these nodes.  This data set is aimed to be processed by this  
> node
>    and the output is a set of filter rules to be used and exchanged  
> with
>    its correspondents.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-mitsuya-monami6-flow- 
> distribution-policy-04.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-mitsuya-monami6-flow-distribution-policy-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-mitsuya-monami6-flow-distribution- 
> policy-04.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2007-8-7093659.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


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



From monami6-bounces@ietf.org Sun Aug 19 22:48:32 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMxJf-0002eY-4T; Sun, 19 Aug 2007 22:48:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMxJe-0002eR-9w
	for monami6@ietf.org; Sun, 19 Aug 2007 22:48:30 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IMxJd-00010f-L1
	for monami6@ietf.org; Sun, 19 Aug 2007 22:48:30 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/jazz) with ESMTP id
	l7K2mQJB024809
	for <monami6@ietf.org>; Mon, 20 Aug 2007 11:48:26 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	l7K2mSh14251
	for <monami6@ietf.org>; Mon, 20 Aug 2007 11:48:28 +0900 (JST)
Received: from pslexc01.psl.local ([127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/bluejays) with ESMTP id
	l7K2mQb08321
	for <monami6@ietf.org>; Mon, 20 Aug 2007 11:48:26 +0900 (JST)
Received: from bach.sg.panasonic.com ([10.81.113.99]) by pslexc01.psl.local
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 10:47:49 +0800
Received: by bach.sg.panasonic.com (Postfix, from userid 1000)
	id 2E013D44A4; Mon, 20 Aug 2007 11:00:48 +0800 (SGT)
Subject: Re: [Monami6] RE: CoA verification for HA
From: Chan-Wah Ng <chanwah.ng@sg.panasonic.com>
To: Monami6 WG <monami6@ietf.org>
In-Reply-To: <5FBD4CFC-7649-459C-B5BA-DFAF4ED72DB7@gmail.com>
References: <000501c7e0b3$53fe48d0$360c6f0a@china.huawei.com>
	<5FBD4CFC-7649-459C-B5BA-DFAF4ED72DB7@gmail.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Mon, 20 Aug 2007 11:00:47 +0800
Message-Id: <1187578847.420.12.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.2 
X-OriginalArrivalTime: 20 Aug 2007 02:47:49.0377 (UTC)
	FILETIME=[7EED3F10:01C7E2D4]
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

On Sat, 2007-08-18 at 15:37 +0900, RYUJI WAKIKAWA wrote:
[snipped]
> >> [Ben] Like I said in the first mail, I'm asking if such issue
> >> should be documented into the analysis draft. Of course if
> >> the WG feels that such issue needs to be addressed, solution
> >> discussion can be done via the ML.
> 
> I am not sure this is issue, but it may be useful to warn this  
> scenario in analysis.
> That's fine to me.
> 

Speaking as co-author of the monami6-mip6-analysis draft, I also think
that it will be useful to add this consideration into the draft.

/rgds
/cwng



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



From mext-bounces@ietf.org Mon Aug 27 09:22:26 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPeWF-00073i-MF; Mon, 27 Aug 2007 09:20:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPeWE-00073Z-RY; Mon, 27 Aug 2007 09:20:38 -0400
Received: from ndjsbar01.ndc.nasa.gov ([198.120.25.38])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPeWD-0003U9-0W; Mon, 27 Aug 2007 09:20:37 -0400
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111])
	by ndjsbar01.ndc.nasa.gov (Spam Firewall) with ESMTP
	id 7F5394170F0; Mon, 27 Aug 2007 08:20:35 -0500 (CDT)
Received: from NDJSEVS23A.ndc.nasa.gov ([129.166.32.223]) by
	ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 08:20:35 -0500
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Aug 2007 08:20:26 -0500
Message-ID: <A3A356E39B867E4380966B0EB600C28F4EAC7A@NDJSEVS23A.ndc.nasa.gov>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RO requirements for aerospace
Thread-Index: AcforQgl0zcXVAMaRFucWKeOhCsozg==
From: "Ivancic, William D. (GRC-RCN0)" <william.d.ivancic@nasa.gov>
To: "IETF NEMO WG" <nemo@ietf.org>,
	<mext@ietf.org>
X-OriginalArrivalTime: 27 Aug 2007 13:20:35.0662 (UTC)
	FILETIME=[0D7CD6E0:01C7E8AD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: 
Subject: [MEXT] RO requirements for aerospace
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

We have updated the draft-eddy-nemo-aero-reqs-01 document," Route
Optimization Requirements for Operational Use in Aeronautics and Space
Exploration Mobile Networks,"  per feedback from the IETF69 meeting.

Changes from draft-eddy-nemo-aero-reqs-01

A diff file is available at the following URL:
http://roland.grc.nasa.gov/~ivancic/shared/ietf/draft-eddy-nemo-aero-req
-01-to-02.htm


   At the IETF69 nemo meeting, consensus was reached to have the
   aeronautics, car-to-car, electronics devices, and any other groups
   develop individual requirements documents.  At a later date, these
   individual requirements documents are likely to be combined into one
   document.  Thus, the draft-eddy-nemo-aero-req-01 document has been
   revised as follows:

      The document has been renamed as draft-eddy-nemo-aero-reqs-02.
      Once MEXT gets organized, this document will become an ietf-mext
      working document per IETF69 consensus.  However, in order to get
      this document out for comment during the transition period, it has
      been release at this time as an individual submission.

      In Req1 - Separability the wording has been changed such that
      selection is base on traffic types rather than applications.  It
      was noted during the IETF69 NEMO meeting that requiring a RO to
      determine separability by application is not practical but use of
      techniques such as traffic classification may be.

      Req5 - Integrity has been changed to Req5 - Packet Loss.  Within
      the IETF integrity has a different meaning than packet loss.
      Within the aviation community, integrity, as used here, refers to
      path integrity or data flow integrity.  Within the IETF, integrity
      implies good data rather than good path.  Thus, in order to
      improve clarity within the IETF, the wording has been changed.

      Req7 - Throughput has been changed to Req7 - Efficient Signaling.
      Overall throughput is relative to the bandwidth of the available
      links and is relatively independent of the RO implementation.
      Rather, the real requirement is for RO to be deployable over low
      bandwidth systems (e.g.  VHDL links of 8 kbps for today's
      aeronautical communication links).  Thus, the wording has been
      change to reflect the actual requirement.

      Acronyms have been defined the first time they are used.

      The requirements section has been re-written to read more like a
      contract.  Thus, we have requirements and rationale with the
      rationale being numbered paragraphs.  The idea is that, if so
      desired at a later date, this should enable combining of the
      various requirement documents into a single requirements document.
      In addition, we hope that the changes will make this document
      easier for an implementer to utilize.
                =20

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Lab 216-433-2620
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic=20

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From monami6-bounces@ietf.org Thu Aug 30 03:30:11 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQeSq-0001Qw-9g; Thu, 30 Aug 2007 03:29:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQeSp-0001Qq-84
	for monami6@ietf.org; Thu, 30 Aug 2007 03:29:15 -0400
Received: from discorde.inria.fr ([192.93.2.38])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQeSo-0005ST-LC
	for monami6@ietf.org; Thu, 30 Aug 2007 03:29:15 -0400
Received: from chokaisan.wiera.hu ([195.56.169.118]) (authenticated bits=0)
	by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l7U7TDxR021284
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 30 Aug 2007 09:29:13 +0200
Message-ID: <46D5E0DE.1090205@inria.fr>
Date: Wed, 29 Aug 2007 23:10:54 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
Organization: INRIA
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] consensus call
	on	draft-soliman-monami6-flow-binding-04.txt
References: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
In-Reply-To: <E115A842-5FE5-47A0-86A8-DC56C9DBA873@enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-j-chkmail-Score: MSGID : 46D671C9.000 on discorde : j-chkmail score : XX :
	5/20 0 0.000 -> 2
X-Miltered: at discorde with ID 46D671C9.000 by Joe's j-chkmail
	(http://j-chkmail . ensmp . fr)!
X-Spam-Score: 1.9 (+)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
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


Dear all,

On Aug. 2, we asked for consensus to confirm the acceptance of
draft-soliman-monami6-flow-binding-04.txt as MonAmi6 WG item for the
transport of flow filters (4th working group item on the charter). This 
is a  confirmation of the positive show of hands during the last IETF 
meeting in Chicago (see the MonAmi6 minutes)

Since then we got (only) one feedback from Koshiro Mitsuya who disagrees 
on this decision to accept this personal draft as a WG document (see his 
comments early August on this thread).

Note that during the discussion we had at IETF 68, we agreed that the 
Monami6 WG would define a solution which transports the filter rules 
within the mobility messages, especially to re-use the security 
association between the MN and its HA. Only draft-soliman meets this 
agreement.

So, unless other people express themselves on this list in the next few
days (thus, people who where on vacation in August still have the
opportunity to express their opinion), I think it's reasonable to say 
that we have rough consensus to 
adoptdraft-soliman-monami6-flow-binding-04.txt as WG document.

That document would then still be in a draft state and any input to 
improve the solution would be welcomed.

Regards,
MonAmi6 WG Chairs Nicolas Montavont & Thierry Ernst



Nicolas Montavont wrote:
> During the meeting, chairs asked the attendees if
> 
> draft-soliman-monami6-flow-binding-04.txt
> 
> shall be accepted for the transport of the policies as described in the 
> 4th WG item
> 
> [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. The solution involves two specifications, one for 
> the policy format and another for its transport [both Standard Track]
> 
> To this question, nobody voted against at the last Monami6 meeting. So, 
> we would like to confirm this decision on the ML.
> 
> If you have a specific concern with this decision, please express your 
> views until 12:01 am UTC Thursday, August the 16th, 2007
> 
> Regards,
> the chairs
> 
> _______________________________________________
> 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



