
From teemu.savolainen@nokia.com  Mon Oct  5 14:27:43 2009
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8D733A6895 for <mif@core3.amsl.com>; Mon,  5 Oct 2009 14:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.332
X-Spam-Level: 
X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=0.267,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzzplvUdBSXt for <mif@core3.amsl.com>; Mon,  5 Oct 2009 14:27:42 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 933233A6407 for <mif@ietf.org>; Mon,  5 Oct 2009 14:27:42 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n95LTG5m006292; Mon, 5 Oct 2009 16:29:17 -0500
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 6 Oct 2009 00:28:42 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 6 Oct 2009 00:28:37 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Mon, 5 Oct 2009 23:28:36 +0200
From: <teemu.savolainen@nokia.com>
To: <marc.blanchet@viagenie.ca>
Date: Mon, 5 Oct 2009 23:27:05 +0200
Thread-Topic: [mif] [Fwd: I-D Action:draft-blanchet-mif-problem-statement-01.txt]
Thread-Index: AcnmD1UepZz1ywXmTK+LrF5J2f7yCANF/FeQFJrhTGA=
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F3EF0ED53E7@NOK-EUMSG-01.mgdnok.nokia.com>
References: <4A296A4F.5090407@viagenie.ca> <18034D4D7FE9AE48BF19AB1B0EF2729F3A6FBF8D54@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F3A6FBF8D54@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Oct 2009 21:28:37.0398 (UTC) FILETIME=[CCD6AB60:01CA4602]
X-Nokia-AV: Clean
Cc: mif@ietf.org
Subject: Re: [mif] [Fwd: I-D Action:draft-blanchet-mif-problem-statement-01.txt]
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 21:27:43 -0000

Marc,=20

While waiting for WG version of the problem statement to appear, I gave add=
itional review to the DNS section. I recalled the DNS64 and AAAA synthesis =
topic I discussed in last IETF with some people, and I also sent a related =
question to Behave WG.

According to discussion in behave list, the DNS64 draft will likely take a =
note of behavior in host multihoming case, but probably you should also add=
 some DNS64 specific notes to mif problem statement, like:
--
6. H1 requests AAAA record from a DNS server on a network that uses protoco=
l translators and DNS64 [DNS64]. If the H1 receives synthesized AAAA record=
, it is quaranteed to be valid only on the network it was learned from. If =
the H1 uses synthesized AAAA on an network interface it is not valid on, th=
e packets will be dropped by the network.=20

[DNS64] draft-ietf-behave-dns64-00
--

Best regards,

	Teemu

=20

>-----Original Message-----
>From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On=20
>Behalf Of Savolainen Teemu (Nokia-D-MSW/Tampere)
>Sent: 22 June, 2009 14:47
>To: marc.blanchet@viagenie.ca
>Cc: mif@ietf.org
>Subject: Re: [mif] [Fwd: I-D=20
>Action:draft-blanchet-mif-problem-statement-01.txt]
>
>Hi Marc,
>
>My opinion is for a) as well.
>
>Some comments to I-D:
>
>- Reference of [I-D.savolainen-6man-fqdn-based-if-selection]=20
>(in references and also in chapter 4) is to an old version,=20
>please change in next revision to:=20
>draft-savolainen-mif-dns-server-selection (February 2009).
>
>- 3.3. Says mobility etc. mechanisms are not required. Would=20
>it add clarity if this would describe that the host may=20
>implement mobility technologies, and for MIF those may or may=20
>not show as virtual interfaces? The particular case I'm=20
>thinking is that if a multi-homed host is running DSMIP6 it=20
>would result in one new interface (addresses) MIF needs to=20
>choose from. E.g. a new flow could be created from the=20
>physical IP address (the same DSMIP6 is using as CoA) or by=20
>using the HoA. Maybe:"If a host implements additional mobility=20
>or multihoming protocols, those may be seen as additional=20
>virtual interfaces, IP addresses, to choose from." ?
>
>- 4.1. 3-case: even if the IP address learned from S2 would be=20
>for "physically" correct destination server, the server may be=20
>configured to provide different set of services for=20
>connections coming from Internet or Intranet. I mean this=20
>problem may be a security problem, but it may also be service=20
>reachability problem.
>
>- What about following two additions to 4.1:
>
>4. S1 or S2 has been used to resolve "a.private.example.com"=20
>to an RFC1918 address. Both N1 and N2 are RFC1918 addressed=20
>networks. IPv4 source address selection may face challenges,=20
>as due address overlapping the source/destination IP addresses=20
>do not necessarily provide enough information for making=20
>proper address selection decisions.
>
>5. H1 has filled its DNS cache from information received from=20
>S1. H1 opens network connection to N2, which becomes more=20
>favored interface. However, the information learned from S1=20
>may not be valid on communications inititated over N2.=20
>
>Best regards,
>=09
>	Teemu
>
>>-----Original Message-----
>>From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of=20
>>ext Marc Blanchet
>>Sent: 05 June, 2009 21:56
>>To: mif
>>Subject: [mif] [Fwd: I-D
>>Action:draft-blanchet-mif-problem-statement-01.txt]
>>
>>Hello,
>> new version of the draft, _trying_ to capture most of the=20
>comments on=20
>>the mailing list, bof, etc... Please comment.
>>
>>one of the discussions among authors is the following:
>>- is MIF scope restricted to:
>>a) one or more administrative domains
>>b) more than one administrative domains.
>>
>>My own opinion is b), while my co-author is a).
>>
>>Marc.
>>
>>-------- Message original --------
>>Sujet : I-D Action:draft-blanchet-mif-problem-statement-01.txt
>>Date : Fri,  5 Jun 2009 11:45:01 -0700 (PDT) De :=20
>>Internet-Drafts@ietf.org R=E9pondre =E0 : internet-drafts@ietf.org Pour :=
=20
>>i-d-announce@ietf.org
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts=20
>>directories.
>>
>>	Title           : Multiple Interfaces Problem Statement
>>	Author(s)       : M. Blanchet, P. Seite
>>	Filename        : draft-blanchet-mif-problem-statement-01.txt
>>	Pages           : 12
>>	Date            : 2009-06-05
>>
>>A multihomed host receives node configuration information=20
>from each of=20
>>its access networks.  Some configuration objects are global to the=20
>>node, some are local to the interface.  Various issues arise when=20
>>multiple conflicting node-scoped configuration objects are=20
>received on=20
>>multiple interfaces.
>>Similar situations also happen with single interface host=20
>connected to=20
>>multiple networks.  This document describes these issues.
>>
>>A URL for this Internet-Draft is:
>>http://www.ietf.org/internet-drafts/draft-blanchet-mif-problem-
>>statement-01.txt
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>Below is the data which will enable a MIME compliant mail reader=20
>>implementation to automatically retrieve the ASCII version of the=20
>>Internet-Draft.
>>
>>
>>--
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca Stun/Turn=20
>>server for VoIP NAT-FW traversal:
>>http://numb.viagenie.ca DTN news service: http://reeves.viagenie.ca
>>
>>
>_______________________________________________
>mif mailing list
>mif@ietf.org
>https://www.ietf.org/mailman/listinfo/mif
>=

From msa@moth.iki.fi  Sat Oct 17 01:04:35 2009
Return-Path: <msa@moth.iki.fi>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 588C63A689A for <mif@core3.amsl.com>; Sat, 17 Oct 2009 01:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id biRLLirjE+kq for <mif@core3.amsl.com>; Sat, 17 Oct 2009 01:04:34 -0700 (PDT)
Received: from cs181073102.pp.htv.fi (unknown [212.16.99.49]) by core3.amsl.com (Postfix) with ESMTP id 3ED553A67A6 for <mif@ietf.org>; Sat, 17 Oct 2009 01:04:33 -0700 (PDT)
Received: from burp.tkv.asdf.org (localhost [127.0.0.1]) by cs181073102.pp.htv.fi (8.14.3/8.14.3/Debian-6) with ESMTP id n9H84axi005565 for <mif@ietf.org>; Sat, 17 Oct 2009 11:04:36 +0300
Received: (from msa@localhost) by burp.tkv.asdf.org (8.14.3/8.14.3/Submit) id n9H84aZE005562; Sat, 17 Oct 2009 11:04:36 +0300
Date: Sat, 17 Oct 2009 11:04:36 +0300
From: Markku Savela <msa@moth.iki.fi>
Message-Id: <200910170804.n9H84aZE005562@burp.tkv.asdf.org>
To: mif@ietf.org
Subject: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2009 08:04:35 -0000

I thought to repost my proposal from over 2 years ago on IPv6 mailing
list (21.8.2007). I got no feedback then, but I think this might be
relevant for the MIF topic. Maybe people now understand better what I
was trying to get through..?

-------

It's not difficult to find even home users with multiple ISP
links. Both ISP's send RA's with different prefixes (A=1).

Host sees now two default routers on link and will have multiple
global addresses. By current rules, host can use either router for
outgoing packets regardless of the selected source address.

I think it would be more sensible to pick the default router from the
set of routers that actually advertised the prefix matching the
selected source address?

This would be a simple way to avoid hitting the filters of the ISP's,
when wrong source address (for that ISP) is used.

The IPv6 architecture assumes all routers on link "co-operate", but I
think that is too much to expect from simple "home routers", the ISP
would be supplying... it's better to put some intelligence into host
requirements?

-- 
Markku Savela

From maxpassion@gmail.com  Mon Oct 19 00:23:10 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00D513A657C for <mif@core3.amsl.com>; Mon, 19 Oct 2009 00:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cyc854eshX4p for <mif@core3.amsl.com>; Mon, 19 Oct 2009 00:23:09 -0700 (PDT)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 3928B3A67FD for <mif@ietf.org>; Mon, 19 Oct 2009 00:23:09 -0700 (PDT)
Received: by pwi4 with SMTP id 4so529371pwi.29 for <mif@ietf.org>; Mon, 19 Oct 2009 00:23:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=NE58BXxPvubM8MJtIQhOze2NwV17ws5rNkKwf0aupDs=; b=uTvL/0wRrNBHm85nzBWyNtzBDVa1TZenONXsGvQUjfyfIfnTiZ/2YZHbUgI1JRDd1W dRN8hcCScf0j/8w7MDHmWP4h9abYdOFd75jPvkrKtUJ0/9jn0ho2EQw9vgl60qqP9BIN 8fDNRxitIIKDXKc+UUk3YQTAyIOP6PDtNlkps=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eogrhXUd5DI9KN/2Ho4XitrjfYAcg/wziuW0M/V61oHfQeJM8F5915ciZL8DF5wbfP TXLyeicBpnXDMWYj14xVNoKru6tw30Q/JYHBeY8llhCEUK4T95y0ct1IkHSiCaQ5CsJa MUeUKuQ/x1EZW2QoZiyDmYBIuih4AsZOHljtI=
MIME-Version: 1.0
Received: by 10.142.67.25 with SMTP id p25mr297094wfa.169.1255936991143; Mon,  19 Oct 2009 00:23:11 -0700 (PDT)
In-Reply-To: <200910170804.n9H84aZE005562@burp.tkv.asdf.org>
References: <200910170804.n9H84aZE005562@burp.tkv.asdf.org>
Date: Mon, 19 Oct 2009 15:23:11 +0800
Message-ID: <25e1aaa40910190023y3c409d8axf83963ec0c91cc1b@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Markku Savela <msa@moth.iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mif@ietf.org
Subject: Re: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 07:23:10 -0000

Hi Markku,
pls see my reply inline.
2009/10/17, Markku Savela <msa@moth.iki.fi>:
> I thought to repost my proposal from over 2 years ago on IPv6 mailing
> list (21.8.2007). I got no feedback then, but I think this might be
> relevant for the MIF topic. Maybe people now understand better what I
> was trying to get through..?
>
> -------
>
> It's not difficult to find even home users with multiple ISP
> links. Both ISP's send RA's with different prefixes (A=1).
>
> Host sees now two default routers on link and will have multiple
> global addresses. By current rules, host can use either router for
> outgoing packets regardless of the selected source address.
>
> I think it would be more sensible to pick the default router from the
> set of routers that actually advertised the prefix matching the
> selected source address?

You mean using source address selection to control the route selection?

BR,
Dapeng Liu

> This would be a simple way to avoid hitting the filters of the ISP's,
> when wrong source address (for that ISP) is used.
>
> The IPv6 architecture assumes all routers on link "co-operate", but I
> think that is too much to expect from simple "home routers", the ISP
> would be supplying... it's better to put some intelligence into host
> requirements?
>
> --
> Markku Savela
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From caozhenpku@gmail.com  Mon Oct 19 00:51:34 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7504B3A677C for <mif@core3.amsl.com>; Mon, 19 Oct 2009 00:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G59h+U5E497a for <mif@core3.amsl.com>; Mon, 19 Oct 2009 00:51:33 -0700 (PDT)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id B73CB28C0E3 for <mif@ietf.org>; Mon, 19 Oct 2009 00:51:33 -0700 (PDT)
Received: by pwi4 with SMTP id 4so531591pwi.29 for <mif@ietf.org>; Mon, 19 Oct 2009 00:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=e2d3mm1WjvSSk+m9/kUtmmF5leeOj7KMP1KFjCi+zro=; b=SyfNitngNqg/5xdZO2YxpD+16uAjBpsfoh3XYJRpTqDhVL/H7KvuHF17r3Flzk3A0Q lEfZKje/TdWvio7uv/cyIXEePjqpkaXUr+pSwDdUqgZPxA3uC1GJKSp2Dfa2+Dg0zW3z U09nISkmYz1u431jlMRbnNBeQlwx9mi1g5AhU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QKsRK04I9GVo2M1ayzMuU2SdZRol5gDabmySb1rhkCZbXFi4mAcKwJgLt4jfjUn5Zd phxO4QmiZ2cAR+MO2tYUqbZS/PyjMOgd0T9S3PRSQdvr2cChM8MY8yi6Q88yJazG7yxv +J6MactVxFehwGn5nbIyelAot8MPNUg/gu6Jo=
MIME-Version: 1.0
Received: by 10.142.247.38 with SMTP id u38mr291567wfh.349.1255938698174; Mon,  19 Oct 2009 00:51:38 -0700 (PDT)
In-Reply-To: <200910170804.n9H84aZE005562@burp.tkv.asdf.org>
References: <200910170804.n9H84aZE005562@burp.tkv.asdf.org>
Date: Mon, 19 Oct 2009 15:51:38 +0800
Message-ID: <a7c8d0a30910190051v56ff1c23s1ef2745e3f04e029@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Markku Savela <msa@moth.iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mif@ietf.org
Subject: Re: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 07:51:34 -0000

On Sat, Oct 17, 2009 at 4:04 PM, Markku Savela <msa@moth.iki.fi> wrote:
> I thought to repost my proposal from over 2 years ago on IPv6 mailing
> list (21.8.2007). I got no feedback then, but I think this might be
> relevant for the MIF topic. Maybe people now understand better what I
> was trying to get through..?
>
> -------
>
> It's not difficult to find even home users with multiple ISP
> links. Both ISP's send RA's with different prefixes (A=1).
>
> Host sees now two default routers on link and will have multiple
> global addresses. By current rules, host can use either router for
> outgoing packets regardless of the selected source address.

Not necessarily true. If the host implements the strong end system
model, it will choose the outgoing route regarding the selected source
address.

>
> I think it would be more sensible to pick the default router from the
> set of routers that actually advertised the prefix matching the
> selected source address?
>
> This would be a simple way to avoid hitting the filters of the ISP's,
> when wrong source address (for that ISP) is used.
>
> The IPv6 architecture assumes all routers on link "co-operate", but I
> think that is too much to expect from simple "home routers", the ISP
> would be supplying... it's better to put some intelligence into host
> requirements?
>
> --
> Markku Savela
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From root@core3.amsl.com  Mon Oct 19 13:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mif@ietf.org
Delivered-To: mif@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A0BC83A6960; Mon, 19 Oct 2009 13:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091019203001.A0BC83A6960@core3.amsl.com>
Date: Mon, 19 Oct 2009 13:30:01 -0700 (PDT)
X-Mailman-Approved-At: Mon, 19 Oct 2009 16:26:47 -0700
Cc: mif@ietf.org
Subject: [mif] I-D Action:draft-ietf-mif-current-practices-00.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 20:30:01 -0000

--NextPart

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


	Title           : Current Practices for Multiple Interface Hosts
	Author(s)       : M. Wasserman
	Filename        : draft-ietf-mif-current-practices-00.txt
	Pages           : 16
	Date            : 2009-10-19

An increasing number of hosts are operating in multiple-interface
environments, where different network interfaces are providing
unequal levels of service or connectivity.  This document summarizes
current practices in this area, and describes in detail how some
common operating systems cope with these challenges.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mif-current-practices-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-mif-current-practices-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-10-19131747.I-D@ietf.org>


--NextPart--

From teemu.savolainen@Nokia.com  Tue Oct 20 01:38:52 2009
Return-Path: <teemu.savolainen@Nokia.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF0003A6A08 for <mif@core3.amsl.com>; Tue, 20 Oct 2009 01:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aPUZriflgNc2 for <mif@core3.amsl.com>; Tue, 20 Oct 2009 01:38:52 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id A78873A6A07 for <mif@ietf.org>; Tue, 20 Oct 2009 01:38:51 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n9K8cTmL000354 for <mif@ietf.org>; Tue, 20 Oct 2009 11:38:56 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 20 Oct 2009 11:37:58 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 20 Oct 2009 11:37:58 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Tue, 20 Oct 2009 10:37:57 +0200
From: <teemu.savolainen@Nokia.com>
To: <mif@ietf.org>
Date: Tue, 20 Oct 2009 10:36:23 +0200
Thread-Topic: Update on draft-savolainen-mif-dns-server-selection
Thread-Index: AcpRYGgTuZ9j2E8RQ1ONcJqikWePUA==
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F3EF1090A7A@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Oct 2009 08:37:58.0464 (UTC) FILETIME=[A07B8400:01CA5160]
X-Nokia-AV: Clean
Subject: [mif] Update on draft-savolainen-mif-dns-server-selection
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2009 08:38:52 -0000

Hi all,

I just posted a small update to "DNS Server Selection on Multi-Homed Hosts"=
, http://www.ietf.org/id/draft-savolainen-mif-dns-server-selection-01.txt

In addition to few small changes, it now includes text about AAAA (NAT64) a=
nd A (Bump-In-the-Stack) record synthesis issues.

All comments continue be welcome,

	Teemu

From pierrick.seite@orange-ftgroup.com  Tue Oct 20 04:41:01 2009
Return-Path: <pierrick.seite@orange-ftgroup.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE3F33A68D4 for <mif@core3.amsl.com>; Tue, 20 Oct 2009 04:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qGJytKZ8iq7l for <mif@core3.amsl.com>; Tue, 20 Oct 2009 04:41:00 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id A16393A6809 for <mif@ietf.org>; Tue, 20 Oct 2009 04:40:59 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 20 Oct 2009 13:41:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Oct 2009 13:40:59 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C462653789@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: problem statement - clarifications on scenarios
Thread-Index: AcpRejGRiRIbgbUzTz+3mYKlriodxQ==
From: <pierrick.seite@orange-ftgroup.com>
To: <mif@ietf.org>
X-OriginalArrivalTime: 20 Oct 2009 11:41:03.0494 (UTC) FILETIME=[34121260:01CA517A]
Subject: [mif] problem statement - clarifications on scenarios
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2009 11:41:01 -0000

Hello,

During Stockholm meeting, we've decided to include scenarios from
section 3 of draft-williams within MIF problem statement draft.=20

After having discussed with authors of req and scenarios drafts, we
concluded that, _from problem statement perspective_, these scenarios
can be classified into two use-cases:
1. "Services shared between all provisioning domains" (corresponds to
draft-williams/scenario 3.1)=20
Or
2. "Services shared by a limited number of provisioning domain" (we've
considered that scenarios 3.3 to 3.5 lead to the same use-case when
considering the high-level description of the ps).


So we have simply updated the MIF host definition in
draft-ietf-problem-statement with the following statement:
" Communications using these IP addresses may be tied on all the
possible provisioning domains, or, at least, on a limited number of
provisioning domains."=20


Now, it may be not sufficient for a good understanding of the issue, so
before submitting a new version, we wish to have the feeling of the WG
on the following:=20
- Do you agree with the classification of the scenarios into two
use-cases, considering the high-level description of the ps?
- Do you think the statement in host definition is clear enough or do
you thing a dedicated section for scenarios is also required?



Comments are welcomed.=20

Best Regards,
Pierrick

From mglt.ietf@gmail.com  Wed Oct 21 01:29:51 2009
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0721B3A657C; Wed, 21 Oct 2009 01:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEmED9XS+1Qt; Wed, 21 Oct 2009 01:29:50 -0700 (PDT)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id 95D503A6804; Wed, 21 Oct 2009 01:29:46 -0700 (PDT)
Received: by fxm18 with SMTP id 18so7443043fxm.37 for <multiple recipients>; Wed, 21 Oct 2009 01:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=ZV0ctBgXTHjEqGpqYDJJMzGdk0Z25QyOfWSmzGfkbEw=; b=jtToMWyYXSLH7S/JFNklfTwJqiNn+Q/3skUsNEBGaVzf2NXrN0y9Udtk/6q6VmObq8 1q92Nf93471W8afmc860aJoqjeNEr2SWGbN3Z985llEZMTF3S2sDrglcSn/mFUjbHFuQ vmoxWfFjWW/qif9zkwhL8c2AlUG0ISMNWys3k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qXe0mz7fzObgmmDoT9v8dP9Bieh+zl81JCtXcxb2tiwXkxxl6AdO5ABI7iEOufq6Mv VgLo2ylSO10jjPTBp1ZaDN+EJzfNPol07muHoa896AwfjT3w/RWBLdLUDn+tDmKtUm/N W1D4N1H4h9ij5mRhpouu2Y8e7f441Yx9HD6ss=
MIME-Version: 1.0
Received: by 10.103.7.31 with SMTP id k31mr3356636mui.48.1256113790909; Wed,  21 Oct 2009 01:29:50 -0700 (PDT)
Date: Wed, 21 Oct 2009 10:29:50 +0200
Message-ID: <51eafbcb0910210129x60cf00eek4ee53df746e515a8@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: mif@ietf.org, ipsec@ietf.org, multipathtcp@ietf.org
Content-Type: multipart/alternative; boundary=0016364174854dfc5004766dc8df
Subject: [mif] IPsec multihoming and mobility
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 08:29:51 -0000

--0016364174854dfc5004766dc8df
Content-Type: text/plain; charset=ISO-8859-1

Hi folks,

We are currently working on IPsec issues and multihoming. Here are our
starting work with a presentation of scenarios and requirements we address,
as well as the design of an extension to MOBIKE.

Scenarios and Requirements :
http://tools.ietf.org/html/draft-mglt-ipsec-mm-requirements-00

Protocol Design :
http://tools.ietf.org/html/draft-mglt-ipsec-mm-mobikex-00

We are currently working implementing it, and looking on how other
multihoming protocol can benefit from it.

Feed backs  and comments are really appreciated.

Regards,

Daniel


-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58

--0016364174854dfc5004766dc8df
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi folks, <br><br>We are currently working on IPsec issues and multihoming.=
 Here are our starting work with a presentation of scenarios and requiremen=
ts we address, as well as the design of an extension to MOBIKE. <br><br>
Scenarios and Requirements :<br><a href=3D"http://tools.ietf.org/html/draft=
-mglt-ipsec-mm-requirements-00">http://tools.ietf.org/html/draft-mglt-ipsec=
-mm-requirements-00</a><br><br>Protocol Design :<br><a href=3D"http://tools=
.ietf.org/html/draft-mglt-ipsec-mm-mobikex-00">http://tools.ietf.org/html/d=
raft-mglt-ipsec-mm-mobikex-00</a><br>
<br>We are currently working implementing it, and looking on how other mult=
ihoming protocol can benefit from it.<br><br>Feed backs=A0 and comments are=
 really appreciated. <br><br>Regards, <br><br>Daniel<br><br clear=3D"all"><=
br>
-- <br>Daniel Migault<br>Orange Labs -- Security<br>+33 6 70 72 69 58<br>

--0016364174854dfc5004766dc8df--

From remi.despres@free.fr  Wed Oct 21 01:39:34 2009
Return-Path: <remi.despres@free.fr>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94EA03A6767 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 01:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRGUy1autOzC for <mif@core3.amsl.com>; Wed, 21 Oct 2009 01:39:33 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id A21AC3A657C for <mif@ietf.org>; Wed, 21 Oct 2009 01:39:32 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 7450AE080EF; Wed, 21 Oct 2009 10:39:35 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 79921E080A3; Wed, 21 Oct 2009 10:39:33 +0200 (CEST)
In-Reply-To: <a7c8d0a30910190051v56ff1c23s1ef2745e3f04e029@mail.gmail.com>
References: <200910170804.n9H84aZE005562@burp.tkv.asdf.org> <a7c8d0a30910190051v56ff1c23s1ef2745e3f04e029@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <CF9F4AE7-9256-4070-AA7F-4F70533AA8D7@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Wed, 21 Oct 2009 10:39:28 +0200
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Cc: mif@ietf.org
Subject: Re: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 08:39:34 -0000

Le 19 oct. 09 =E0 09:51, Zhen Cao a =E9crit :

> On Sat, Oct 17, 2009 at 4:04 PM, Markku Savela <msa@moth.iki.fi> =20
> wrote:
>> I thought to repost my proposal from over 2 years ago on IPv6 mailing
>> list (21.8.2007). I got no feedback then, but I think this might be
>> relevant for the MIF topic. Maybe people now understand better what I
>> was trying to get through..?
>>
>> -------
>>
>> It's not difficult to find even home users with multiple ISP
>> links. Both ISP's send RA's with different prefixes (A=3D1).
>>
>> Host sees now two default routers on link and will have multiple
>> global addresses. By current rules, host can use either router for
>> outgoing packets regardless of the selected source address.
>
> Not necessarily true. If the host implements the strong end system
> model, it will choose the outgoing route regarding the selected source
> address.

Interesting.
Could you give a reference where a definition you are using of the =20
"strong end system model" is given?
Thanks.
RD


From dokaspar.ietf@gmail.com  Wed Oct 21 01:46:49 2009
Return-Path: <dokaspar.ietf@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25BF63A68BB for <mif@core3.amsl.com>; Wed, 21 Oct 2009 01:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbmtfkpaQAaN for <mif@core3.amsl.com>; Wed, 21 Oct 2009 01:46:48 -0700 (PDT)
Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id 94D233A67E7 for <mif@ietf.org>; Wed, 21 Oct 2009 01:46:47 -0700 (PDT)
Received: by bwz23 with SMTP id 23so199437bwz.29 for <mif@ietf.org>; Wed, 21 Oct 2009 01:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EGt8LyhIitZOZPodDKJBDjhA1OqkfJ24yBynCIxnNyI=; b=eX4z61Qx42HX5u3OLsmfREB9IBMIWC0PLI81vQ0Beu8YhDvb+6UWfIAa6SA4D50mtH pooXmQI4VVLc9i88/p4BhRgHeyD3G7iF2iLQkbQPR99dBU1SxWs/lQsjmpKvrc2VvpPS qyhspbDkInhw2La+QbyjpJy+OTAUr+5xtZJjQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Q8M7OKabgCwuGk1YzmEYWbCTdsf2+KfltIW3RF6HHibBXKSiHuPMV7RA57SjpnwHJ+ x67JhHAlS43xA32HLi+bdeRj/bEeCb5WaWyUclyq5aAn7X6AeeTNwFfBTyWHelPDw22g I6U6aB7e2FWHlrejeXndZKWmQwcmvNo2eAPUw=
MIME-Version: 1.0
Received: by 10.103.80.4 with SMTP id h4mr3177655mul.112.1256114810150; Wed,  21 Oct 2009 01:46:50 -0700 (PDT)
In-Reply-To: <CF9F4AE7-9256-4070-AA7F-4F70533AA8D7@free.fr>
References: <200910170804.n9H84aZE005562@burp.tkv.asdf.org> <a7c8d0a30910190051v56ff1c23s1ef2745e3f04e029@mail.gmail.com> <CF9F4AE7-9256-4070-AA7F-4F70533AA8D7@free.fr>
Date: Wed, 21 Oct 2009 10:46:50 +0200
Message-ID: <2a3692de0910210146q5d95786cw3b7c7bc78a10e8c4@mail.gmail.com>
From: Dominik Kaspar <dokaspar.ietf@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
Subject: Re: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 08:46:49 -0000

http://en.wikipedia.org/wiki/Host_model

On Wed, Oct 21, 2009 at 10:39 AM, R=E9mi Despr=E9s <remi.despres@free.fr> w=
rote:
>
> Le 19 oct. 09 =E0 09:51, Zhen Cao a =E9crit :
>
>> On Sat, Oct 17, 2009 at 4:04 PM, Markku Savela <msa@moth.iki.fi> wrote:
>>>
>>> I thought to repost my proposal from over 2 years ago on IPv6 mailing
>>> list (21.8.2007). I got no feedback then, but I think this might be
>>> relevant for the MIF topic. Maybe people now understand better what I
>>> was trying to get through..?
>>>
>>> -------
>>>
>>> It's not difficult to find even home users with multiple ISP
>>> links. Both ISP's send RA's with different prefixes (A=3D1).
>>>
>>> Host sees now two default routers on link and will have multiple
>>> global addresses. By current rules, host can use either router for
>>> outgoing packets regardless of the selected source address.
>>
>> Not necessarily true. If the host implements the strong end system
>> model, it will choose the outgoing route regarding the selected source
>> address.
>
> Interesting.
> Could you give a reference where a definition you are using of the "stron=
g
> end system model" is given?
> Thanks.
> RD
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From caozhenpku@gmail.com  Wed Oct 21 02:24:44 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51173A69F7 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 02:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lffOV+Zb4if2 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 02:24:44 -0700 (PDT)
Received: from mail-pz0-f176.google.com (mail-pz0-f176.google.com [209.85.222.176]) by core3.amsl.com (Postfix) with ESMTP id F27853A680A for <mif@ietf.org>; Wed, 21 Oct 2009 02:24:43 -0700 (PDT)
Received: by pzk6 with SMTP id 6so8376949pzk.29 for <mif@ietf.org>; Wed, 21 Oct 2009 02:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7QaL62g6ImBpNc74e2RafS1qprJObjhjO5OIYQhe39Q=; b=Zag3mlq8NjbmQvJaW/VePeU5a9svN05dBHvofWgrH5u6vH7lhoW4jXp5dRzQ9j4Nc0 mysM0fp2M4WhFiSNBKKomIRvE0hR7t8YsemHKUoWylUWDJpoSN01ZjCOfdCLYT/EYHGo ECj99wKAUySlft7/qki206OKliAL19+ycjJ5A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=eOWrShFS7wicz4Vew/GIvGE8tqMQfYWwBBoPAw1aMgdXSxMY3vWcDLhmeE66r73EXx zquJwUKWMy+NYHiH41A9FiOBPiELOuMGsVBVml47ZJ2gBs3yF7ctzvvPwVF6AV+iHuoU VAoykj4afvyf01ZCMgRpBO78fDQKhDuM+d0+Q=
MIME-Version: 1.0
Received: by 10.142.3.3 with SMTP id 3mr554343wfc.141.1256117089245; Wed, 21  Oct 2009 02:24:49 -0700 (PDT)
In-Reply-To: <2a3692de0910210146q5d95786cw3b7c7bc78a10e8c4@mail.gmail.com>
References: <200910170804.n9H84aZE005562@burp.tkv.asdf.org> <a7c8d0a30910190051v56ff1c23s1ef2745e3f04e029@mail.gmail.com> <CF9F4AE7-9256-4070-AA7F-4F70533AA8D7@free.fr> <2a3692de0910210146q5d95786cw3b7c7bc78a10e8c4@mail.gmail.com>
Date: Wed, 21 Oct 2009 17:24:49 +0800
Message-ID: <a7c8d0a30910210224j1d560dc6s9c13c120a6c6e146@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Dominik Kaspar <dokaspar.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
Subject: Re: [mif] What about changing [IPv6] default router rules a bit?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 09:24:44 -0000

Thanks for pointing this out. These concepts are defined in RFC1122,
searching for "Strong ES Model" there. They are also mentioned in the
mif-ps draft.

On Wed, Oct 21, 2009 at 4:46 PM, Dominik Kaspar <dokaspar.ietf@gmail.com> w=
rote:
> http://en.wikipedia.org/wiki/Host_model
>
> On Wed, Oct 21, 2009 at 10:39 AM, R=E9mi Despr=E9s <remi.despres@free.fr>=
 wrote:
>>
>> Le 19 oct. 09 =E0 09:51, Zhen Cao a =E9crit :
>>
>>> On Sat, Oct 17, 2009 at 4:04 PM, Markku Savela <msa@moth.iki.fi> wrote:
>>>>
>>>> I thought to repost my proposal from over 2 years ago on IPv6 mailing
>>>> list (21.8.2007). I got no feedback then, but I think this might be
>>>> relevant for the MIF topic. Maybe people now understand better what I
>>>> was trying to get through..?
>>>>
>>>> -------
>>>>
>>>> It's not difficult to find even home users with multiple ISP
>>>> links. Both ISP's send RA's with different prefixes (A=3D1).
>>>>
>>>> Host sees now two default routers on link and will have multiple
>>>> global addresses. By current rules, host can use either router for
>>>> outgoing packets regardless of the selected source address.
>>>
>>> Not necessarily true. If the host implements the strong end system
>>> model, it will choose the outgoing route regarding the selected source
>>> address.
>>
>> Interesting.
>> Could you give a reference where a definition you are using of the "stro=
ng
>> end system model" is given?
>> Thanks.
>> RD
>>
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>>
>

From caozhenpku@gmail.com  Wed Oct 21 02:36:17 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DEB43A6936 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 02:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.508
X-Spam-Level: **
X-Spam-Status: No, score=2.508 tagged_above=-999 required=5 tests=[AWL=-4.906,  BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_41=0.118, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DCaKcevfXDh1 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 02:36:16 -0700 (PDT)
Received: from mail-pz0-f204.google.com (mail-pz0-f204.google.com [209.85.222.204]) by core3.amsl.com (Postfix) with ESMTP id C8A533A6912 for <mif@ietf.org>; Wed, 21 Oct 2009 02:36:16 -0700 (PDT)
Received: by pzk42 with SMTP id 42so5470535pzk.31 for <mif@ietf.org>; Wed, 21 Oct 2009 02:36:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=idqO23yRFGStr47BVyiVtojXkbqC+3j7AjxyFL1VZaw=; b=q0wmPgyEtm31xSwI67F7fzmufSBNjOJAOQTviDWZm0gRAemZh0GAJwh20D7dRg9tx2 FAIdM6CNsIODA2/2XM8aUW1Er7p29f9ci6H91d7Y1rIiEBYbb4eU5SNxImf/CoEgQb36 Elpy7od3EeYpHQA7d0Kr4sqMWvX/Xb53Hra6A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Cx4pZyOGKkJYskpAi/KOqKsPmrna3uBtDmo7bhfhxoDabTaCPY3vaK3pvCejQDt1HT Eo2SN3QrL/jf/G2E1hOb6BUixQ7zPaPE21NA7mK8t13T+rkD/T02PALiaGve1Uisw9fo 5FN/T9JWwK1NctFj7gtRKVvfFpMeYI4k8E6Vo=
MIME-Version: 1.0
Received: by 10.142.61.25 with SMTP id j25mr503446wfa.320.1256117782975; Wed,  21 Oct 2009 02:36:22 -0700 (PDT)
In-Reply-To: <11659141.707861256003888349.JavaMail.coremail@bj163app32.163.com>
References: <11659141.707861256003888349.JavaMail.coremail@bj163app32.163.com>
Date: Wed, 21 Oct 2009 17:36:22 +0800
Message-ID: <a7c8d0a30910210236s63a7e760qdf260c556ea287df@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: =?GB2312?B?0rbO5LXP?= <wudiye_tc3@163.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] =?gb2312?b?V2hhdCBhYm91dCBjaGFuZ2luZyBbSVB2Nl0gZGVmYXVsdCBy?= =?gb2312?b?b3V0ZXIgcnVsZXMgYSBiaXSjvw==?=
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 09:36:17 -0000

>>> It's not difficult to find even home users with multiple ISP
>>> links. Both ISP's send RA's with different prefixes (A=3D1).
>>>
>>> Host sees now two default routers on link and will have multiple
>>> global addresses. By current rules, host can use either router for
>>> outgoing packets regardless of the selected source address.
>>
>>Not necessarily true. If the host implements the strong end system
>>model, it will choose the outgoing route regarding the selected source
>>address.
> the host how to select the source address ,RFC3484 defines the source
> address select rules,
> but in generally it does not be implement in the pc os.

Section 3.2.1.2 of draft-ietf-mif-current-practices-00, "Windows
implements [RFC3484] for source address selection in IPv6 and, in
Windows Vista, for IPv4".

Thanks for discussion.

>>
>>>
>>> I think it would be more sensible to pick the default router from the
>>> set of routers that actually advertised the prefix matching the
>>> selected source address?
>>>
>>> This would be a simple way to avoid hitting the filters of the ISP's,
>>> when wrong source address (for that ISP) is used.
>>>
>>> The IPv6 architecture assumes all routers on link "co-operate", but I
>>> think that is too much to expect from simple "home routers", the ISP
>>> would be supplying... it's better to put some intelligence into host
>>> requirements?
>>>
>>> --
>>> Markku Savela
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>>
>
>
>
>
> ________________________________
> "=D1=A9=BC=FB"=D1=EE=C3=DD=D1=FB=C4=E3=B9=B2=C6=B73D=B9=FA=D4=CF=CD=F8=D3=
=CE=A1=B6=CC=EC=CF=C2=B7=A1=A1=B7=A3=AC=BA=A3=B1=A8=C3=E2=B7=D1=C1=EC

From Michael.Tuexen@lurchi.franken.de  Wed Oct 21 07:44:44 2009
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0C3E28C127; Wed, 21 Oct 2009 07:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.188
X-Spam-Level: **
X-Spam-Status: No, score=2.188 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HOST_EQ_DIP_TDIAL=2.144, HOST_MISMATCH_NET=0.311,  MIME_8BIT_HEADER=0.3, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ahv9OmtmFWSn; Wed, 21 Oct 2009 07:44:44 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id BA12E28C114; Wed, 21 Oct 2009 07:44:43 -0700 (PDT)
Received: from [192.168.1.100] (p508FD714.dip.t-dialin.net [80.143.215.20]) by mail-n.franken.de (Postfix) with ESMTP id AECE91C0B4627; Wed, 21 Oct 2009 16:44:49 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <51eafbcb0910210129x60cf00eek4ee53df746e515a8@mail.gmail.com>
Date: Wed, 21 Oct 2009 16:44:48 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <D42BF6E1-B415-4AA1-8537-6F84F9FD9C40@lurchi.franken.de>
References: <51eafbcb0910210129x60cf00eek4ee53df746e515a8@mail.gmail.com>
To: Daniel Migault <mglt.ietf@gmail.com>
X-Mailer: Apple Mail (2.1076)
X-Mailman-Approved-At: Wed, 21 Oct 2009 07:53:46 -0700
Cc: ipsec@ietf.org, multipathtcp@ietf.org, mif@ietf.org
Subject: Re: [mif] [multipathtcp] IPsec multihoming and mobility
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 14:44:45 -0000

Hi Daniel,

have you looked at
http://www.ietf.org/rfc/rfc3554.txt

Best regards
Michael

On Oct 21, 2009, at 10:29 AM, Daniel Migault wrote:

> Hi folks,
>
> We are currently working on IPsec issues and multihoming. Here are  
> our starting work with a presentation of scenarios and requirements  
> we address, as well as the design of an extension to MOBIKE.
>
> Scenarios and Requirements :
> http://tools.ietf.org/html/draft-mglt-ipsec-mm-requirements-00
>
> Protocol Design :
> http://tools.ietf.org/html/draft-mglt-ipsec-mm-mobikex-00
>
> We are currently working implementing it, and looking on how other  
> multihoming protocol can benefit from it.
>
> Feed backs  and comments are really appreciated.
>
> Regards,
>
> Daniel
>
>
> -- 
> Daniel Migault
> Orange Labs -- Security
> +33 6 70 72 69 58
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From maxpassion@gmail.com  Wed Oct 21 20:31:34 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A2903A6817 for <mif@core3.amsl.com>; Wed, 21 Oct 2009 20:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkNYfjcgY0lE for <mif@core3.amsl.com>; Wed, 21 Oct 2009 20:31:33 -0700 (PDT)
Received: from mail-pz0-f176.google.com (mail-pz0-f176.google.com [209.85.222.176]) by core3.amsl.com (Postfix) with ESMTP id 740443A6781 for <mif@ietf.org>; Wed, 21 Oct 2009 20:31:33 -0700 (PDT)
Received: by pzk6 with SMTP id 6so9218303pzk.29 for <mif@ietf.org>; Wed, 21 Oct 2009 20:31:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ayHTpj7aj5P9/0aIRH5ST1wOXU5ZSnEi33pSYn7vYwk=; b=SZSsqLAwRbFq3NBRGUDtbVmu7YsRuGYVKu+msURTQFPwHNFIFOJJiKGV2ROH3DxA/5 H3AHce0pvqu7KjbvyVvilHLz2EJL0tZKoqws0Fi8w3ptxsfOUu/lgyvsnDfBUcF8P7iw /RIwg7OQEH5TiyYtXo6Qcu2Xu57ahQgFlO8TY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fbKrjs231b+UR4VaTvCNckN/5ORNqByjYX3ZZGFrEafTpC1CYsYWnfXKeeLEc18n2h f2DE8bFFXO7o5MXLZgYOfiikhMK4/XhZwbLtDZHx3yMmtqT1wTaRF3X1r6v+mjK3Onfv F/ie91ie82SpibZwPEH1+27y6oQYjCecRjzJ4=
MIME-Version: 1.0
Received: by 10.142.61.35 with SMTP id j35mr655614wfa.52.1256182299073; Wed,  21 Oct 2009 20:31:39 -0700 (PDT)
In-Reply-To: <25e1aaa40910202007n3a2ef6cfk51c2c88c8b4f705a@mail.gmail.com>
References: <843DA8228A1BA74CA31FB4E111A5C462653789@ftrdmel0.rd.francetelecom.fr> <25e1aaa40910202007n3a2ef6cfk51c2c88c8b4f705a@mail.gmail.com>
Date: Thu, 22 Oct 2009 11:31:39 +0800
Message-ID: <25e1aaa40910212031n4af59854t7d2109c97c8b118@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: pierrick.seite@orange-ftgroup.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: mif@ietf.org
Subject: Re: [mif] problem statement - clarifications on scenarios
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2009 03:31:34 -0000

Hi Pierrick,

I personally prefer the idea of adding a dedicated section to describe
the scenarios, since the scenarios may help people to understand where
the problem is which is the goal of the PS document. Regarding to the
classification of the scenarios, I guess it is ok for me. thanks.

BR,
Dapeng Liu

> 2009/10/20, pierrick.seite@orange-ftgroup.com
> <pierrick.seite@orange-ftgroup.com>:
>>
>>
>>
>> Hello,
>>
>> During Stockholm meeting, we've decided to include scenarios from
>> section 3 of draft-williams within MIF problem statement draft.
>>
>> After having discussed with authors of req and scenarios drafts, we
>> concluded that, _from problem statement perspective_, these scenarios
>> can be classified into two use-cases:
>> 1. "Services shared between all provisioning domains" (corresponds to
>> draft-williams/scenario 3.1)
>> Or
>> 2. "Services shared by a limited number of provisioning domain" (we've
>> considered that scenarios 3.3 to 3.5 lead to the same use-case when
>> considering the high-level description of the ps).
>>
>>
>> So we have simply updated the MIF host definition in
>> draft-ietf-problem-statement with the following statement:
>> " Communications using these IP addresses may be tied on all the
>> possible provisioning domains, or, at least, on a limited number of
>> provisioning domains."
>>
>>
>> Now, it may be not sufficient for a good understanding of the issue, so
>> before submitting a new version, we wish to have the feeling of the WG
>> on the following:
>> - Do you agree with the classification of the scenarios into two
>> use-cases, considering the high-level description of the ps?
>> - Do you think the statement in host definition is clear enough or do
>> you thing a dedicated section for scenarios is also required?
>>
>>
>>
>> Comments are welcomed.
>>
>> Best Regards,
>> Pierrick
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>>
>

From caozhenpku@gmail.com  Thu Oct 22 04:13:10 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E004B3A69DC for <mif@core3.amsl.com>; Thu, 22 Oct 2009 04:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=0.801,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GC7CbF5hlBd for <mif@core3.amsl.com>; Thu, 22 Oct 2009 04:13:09 -0700 (PDT)
Received: from mail-pz0-f176.google.com (mail-pz0-f176.google.com [209.85.222.176]) by core3.amsl.com (Postfix) with ESMTP id E42973A699A for <mif@ietf.org>; Thu, 22 Oct 2009 04:13:09 -0700 (PDT)
Received: by pzk6 with SMTP id 6so9573852pzk.29 for <mif@ietf.org>; Thu, 22 Oct 2009 04:13:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vvgvkbW8PJnkODnXlAZNFn7NAZVxAIVOvKvo5frvyMs=; b=hqKjpFHU4rPIE9vK2pQD29ECVlfli8WBaWQoO6l3D2ZliBJFKXYY6jQpg/EYoS4M5u pyBN6KzY1sWFbX/PaLiPm2/FPhHfrBm4SWvolRekkbnEDahbmf6rKVYMwqQpZiELIH3z TEWkFg0Wy/HLscJmFzmgmb2TvHy6WvJdEeIQM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vrzGTDF5/FwSK2MMHkFSyEcp7F1HunuDtn/KZ1RPaXS9xld8eBYn/C1y5jT9d5PY/n xEzJHRr9tiuB/Z6xmxTmmFnJ1er2UpelSZwp/zOdfkuCCLvw2hSrV6QQ0EnRPa9HDXVN uTxEB5TD26SUx1c6bumaSCQhqPYyBqxHM2RZ0=
MIME-Version: 1.0
Received: by 10.142.59.5 with SMTP id h5mr598460wfa.24.1256209997164; Thu, 22  Oct 2009 04:13:17 -0700 (PDT)
In-Reply-To: <843DA8228A1BA74CA31FB4E111A5C462653789@ftrdmel0.rd.francetelecom.fr>
References: <843DA8228A1BA74CA31FB4E111A5C462653789@ftrdmel0.rd.francetelecom.fr>
Date: Thu, 22 Oct 2009 19:13:17 +0800
Message-ID: <a7c8d0a30910220413h73ad9b21s699133549efc0089@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: pierrick.seite@orange-ftgroup.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: mif@ietf.org
Subject: Re: [mif] problem statement - clarifications on scenarios
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2009 11:13:11 -0000

Hi Pierrick,

I have some concerns on the two scenarios. I believe MIF problems
occurs in two use cases, outbound communication and inbound
communication. But the current documents only discuss outbound
scenarios, that how a mif host handles all its available interfaces.
For inbound communication that how data traffic routes to the mif host
(mip is one example), it has not been touched.

Besides, I prefer a dedicated section for scenarios.

Thanks,
Zhen

On Tue, Oct 20, 2009 at 7:40 PM,  <pierrick.seite@orange-ftgroup.com> wrote:
>
>
>
> Hello,
>
> During Stockholm meeting, we've decided to include scenarios from
> section 3 of draft-williams within MIF problem statement draft.
>
> After having discussed with authors of req and scenarios drafts, we
> concluded that, _from problem statement perspective_, these scenarios
> can be classified into two use-cases:
> 1. "Services shared between all provisioning domains" (corresponds to
> draft-williams/scenario 3.1)
> Or
> 2. "Services shared by a limited number of provisioning domain" (we've
> considered that scenarios 3.3 to 3.5 lead to the same use-case when
> considering the high-level description of the ps).
>
>
> So we have simply updated the MIF host definition in
> draft-ietf-problem-statement with the following statement:
> " Communications using these IP addresses may be tied on all the
> possible provisioning domains, or, at least, on a limited number of
> provisioning domains."
>
>
> Now, it may be not sufficient for a good understanding of the issue, so
> before submitting a new version, we wish to have the feeling of the WG
> on the following:
> - Do you agree with the classification of the scenarios into two
> use-cases, considering the high-level description of the ps?
> - Do you think the statement in host definition is clear enough or do
> you thing a dedicated section for scenarios is also required?
>
>
>
> Comments are welcomed.
>
> Best Regards,
> Pierrick
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From root@core3.amsl.com  Mon Oct 26 03:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mif@ietf.org
Delivered-To: mif@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id DF6103A68B4; Mon, 26 Oct 2009 03:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091026103001.DF6103A68B4@core3.amsl.com>
Date: Mon, 26 Oct 2009 03:30:01 -0700 (PDT)
X-Mailman-Approved-At: Mon, 26 Oct 2009 04:53:13 -0700
Cc: mif@ietf.org
Subject: [mif] I-D Action:draft-ietf-mif-problem-statement-01.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 10:30:02 -0000

--NextPart

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


	Title           : Multiple Interfaces Problem Statement
	Author(s)       : M. Blanchet, P. Seite
	Filename        : draft-ietf-mif-problem-statement-01.txt
	Pages           : 13
	Date            : 2009-10-26

A multihomed host receives node configuration information from each
of its provisioning domain.  Some configuration objects are global to
the node, some are local to the interface.  Various issues arise when
multiple conflicting node-scoped configuration objects are received
on multiple interfaces.  Similar situations also happen with single
interface host connected to multiple networks.  This document
describes these issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mif-problem-statement-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-mif-problem-statement-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-10-26032028.I-D@ietf.org>


--NextPart--

From wudiyetc@gmail.com  Tue Oct 27 04:03:35 2009
Return-Path: <wudiyetc@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA7C93A6955 for <mif@core3.amsl.com>; Tue, 27 Oct 2009 04:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZTpZmtjKUyD for <mif@core3.amsl.com>; Tue, 27 Oct 2009 04:03:35 -0700 (PDT)
Received: from mail-yw0-f183.google.com (mail-yw0-f183.google.com [209.85.211.183]) by core3.amsl.com (Postfix) with ESMTP id 0C6B63A6942 for <mif@ietf.org>; Tue, 27 Oct 2009 04:03:34 -0700 (PDT)
Received: by ywh13 with SMTP id 13so15399ywh.29 for <mif@ietf.org>; Tue, 27 Oct 2009 04:03:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:x-mailer:mime-version:content-type; bh=A0v54Qepwl3Hr2LvZaR9Plp3VbAT6GOixgeAznDuwHI=; b=vu+cCV7h8B6GxF8wvPsVtCGNvVuxR5kR1CQ7EiqVIsXU9Jn3iRSB04wuAZHEu9HLZf euVEWhQNvYThSmU1Jmrj5tkr5J9nISycf/o78cTYNoswNZv8ce8XAG7aHPZsqbESLSsJ rIVIBeJEGAlEVJEhXRURzIU168R/fH1I2i1bs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:x-mailer:mime-version :content-type; b=F3NIdMuMlzWNZ05tOvujXwujooBj94cIKm+3WraZ+gvFOx50Clj+ALzkQk3yOeY1zB RhrJA+lNI3SUSj3XtRIdsCzGtVmM4S6v63xpyYsbUE900YsVC8U/8/XaRSzfOp51QdCa 82JH4l/YqEePlVMadrwFmmlfqO4lHNcYdIZ2Y=
Received: by 10.90.134.2 with SMTP id h2mr3858994agd.110.1256641425797; Tue, 27 Oct 2009 04:03:45 -0700 (PDT)
Received: from bupt-feng ([221.218.192.219]) by mx.google.com with ESMTPS id 15sm1630936yxh.40.2009.10.27.04.03.41 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Oct 2009 04:03:44 -0700 (PDT)
Date: Tue, 27 Oct 2009 19:03:53 +0800
From: "wudiyetc" <wudiyetc@gmail.com>
To: "liudapeng" <liudapeng@chinamobile.com>, "liudapeng" <liudapeng@chinamobile.com>, "liudapeng" <liudapeng@chinamobile.com>
Message-ID: <200910271903454689245@gmail.com>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon767420237606_====="
X-Mailman-Approved-At: Tue, 27 Oct 2009 06:33:09 -0700
Cc: mif <mif@ietf.org>
Subject: Re: [mif] draft-liu-mif-api-extension-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2009 11:03:35 -0000

This is a multi-part message in MIME format.

--=====003_Dragon767420237606_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit


hello ,liu
        In the struct GenericConnection,there is a pointer "sock" which points to a socket structure.
But in the section 6.1 , it maps two socket  to the *gconn, is it a mistake? 

Wudi ye

--=====003_Dragon767420237606_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR><LINK 
href="BLOCKQUOTE{margin-Top: 0px; margin-Bottom: 0px; margin-Left: 2em}" 
rel=stylesheet></HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>hello ,liu</FONT></DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the struct 
GenericConnection,there is a pointer "sock" which points 
to&nbsp;<EM><STRONG>a</STRONG></EM> socket structure.</DIV>
<DIV>But in the section 6.1&nbsp;, it maps two socket &nbsp;to the *gconn, is it 
a mistake? </DIV>
<DIV align=left><FONT face=Verdana color=#c0c0c0 size=2></FONT>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana color=#c0c0c0 size=2>Wudi 
ye</FONT></DIV></BODY></HTML>

--=====003_Dragon767420237606_=====--


From wudiyetc@gmail.com  Tue Oct 27 04:08:54 2009
Return-Path: <wudiyetc@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28DDD28C10C for <mif@core3.amsl.com>; Tue, 27 Oct 2009 04:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.354
X-Spam-Level: 
X-Spam-Status: No, score=-0.354 tagged_above=-999 required=5 tests=[AWL=0.355,  BAYES_00=-2.599, FR_IMPORT_CSS=1.889, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbM9bMuwTWqD for <mif@core3.amsl.com>; Tue, 27 Oct 2009 04:08:53 -0700 (PDT)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id 38ED23A69B8 for <mif@ietf.org>; Tue, 27 Oct 2009 04:08:53 -0700 (PDT)
Received: by yxe30 with SMTP id 30so18708yxe.29 for <mif@ietf.org>; Tue, 27 Oct 2009 04:09:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:x-mailer:mime-version:content-type; bh=i1ML9WChB1Wct4yYgmf7QzVlhQ7069Ob2TOSCyVgls0=; b=bk+BdY/yqId6p3xURp4y8fKVbxORd9JO4w2pVkAdxG/J+039FAWWcxVuu1Ht9RHJCR 1Is4ZNMUW/gojlJ43o2kBKU9ljf0EaKEQaY/n1Smlj0XznJQQK8F5vxABJbW//Dg8WJQ A9DPti0Zq8AhIc/uC1wUawnFmhUoCIve5ZjEQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:x-mailer:mime-version :content-type; b=R6x3RIFco7g7pNR8RaYdEvjkCu8WVfNMiUj3ol3wScLL53AII49XYfX9T0WQ3MhTYX sCPYc93ncqDzTQSJEJ9LeTdsS/uBxCh3e4wOLgCmd7snJh8VI7or7oXto6XZ+DOu89M1 nSXmHnYLdNZ/TLfhcpwRVOdZkbaxhglXQ9rf0=
Received: by 10.91.28.2 with SMTP id f2mr7840430agj.16.1256641743509; Tue, 27 Oct 2009 04:09:03 -0700 (PDT)
Received: from bupt-feng ([221.218.192.219]) by mx.google.com with ESMTPS id 9sm1623451yxf.5.2009.10.27.04.09.00 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Oct 2009 04:09:02 -0700 (PDT)
Date: Tue, 27 Oct 2009 19:09:12 +0800
From: "wudiyetc" <wudiyetc@gmail.com>
To: "liudapeng" <liudapeng@chinamobile.com>, "liudapeng" <liudapeng@chinamobile.com>, "liudapeng" <liudapeng@chinamobile.com>
Message-ID: <200910271909052036827@gmail.com>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon427711747818_====="
X-Mailman-Approved-At: Tue, 27 Oct 2009 06:33:09 -0700
Cc: mif <mif@ietf.org>
Subject: Re: [mif] draft-liu-mif-api-extension-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2009 11:08:54 -0000

This is a multi-part message in MIME format.

--=====003_Dragon427711747818_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit


hello ,liu
        In the struct GenericConnection,there is a pointer "sock" which points to a socket structure.
But in the section 6.1 , it maps two socket  to the *gconn, is it a mistake? 

Wudi ye

--=====003_Dragon427711747818_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<STYLE type=text/css>@import url( C:\Documents and Settings\feng\Local Settings\Temporary Internet Files\scrollbar.css );
</STYLE>

<META http-equiv=Content-Type content="text/html; charset=GB2312">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR><LINK 
href="BLOCKQUOTE{margin-Top: 0px; margin-Bottom: 0px; margin-Left: 2em}" 
rel=stylesheet></HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>hello ,liu</FONT></DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the struct 
GenericConnection,there is a pointer "sock" which points 
to&nbsp;<EM><STRONG>a</STRONG></EM> socket structure.</DIV>
<DIV>But in the section 6.1&nbsp;, it maps two socket &nbsp;to the *gconn, is it 
a mistake? </DIV>
<DIV align=left><FONT face=Verdana color=#c0c0c0 size=2></FONT>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana color=#c0c0c0 size=2>Wudi 
ye</FONT></DIV></BODY></HTML>

--=====003_Dragon427711747818_=====--


From caozhenpku@gmail.com  Tue Oct 27 06:42:52 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A547F3A68C4 for <mif@core3.amsl.com>; Tue, 27 Oct 2009 06:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[AWL=0.701,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQ2ov9jrhcY9 for <mif@core3.amsl.com>; Tue, 27 Oct 2009 06:42:48 -0700 (PDT)
Received: from mail-pz0-f204.google.com (mail-pz0-f204.google.com [209.85.222.204]) by core3.amsl.com (Postfix) with ESMTP id 22B013A67DF for <mif@ietf.org>; Tue, 27 Oct 2009 06:42:44 -0700 (PDT)
Received: by pzk42 with SMTP id 42so106911pzk.31 for <mif@ietf.org>; Tue, 27 Oct 2009 06:42:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CQAUeTptWze7RsgsAUg2kZwCgCxDvKQTPFOD9NRFSR4=; b=Ft4zQj2byE8RBV8BcVyPQIjESLxVBOU9JmWcgDGFWU2tA1P8B+ZrfLd+pAtW37E4xd UKsatZBFAbZG1AVS5FAhC2vnMsZ9uk3NMKdyqQl5LkYvYBiSLde189CjyT/zeBYmhQbY RPwFWOku0/uha3DiNTBSr8AxUf5hKkoNe6vnM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TQ6TiQ0oh3tBdoHbex9hPXQvj7CJw3Zt3eaM7kjlqzgVFW7St9p5KoGcu05CuYmWVk nwFj7E96xbHk6FDVEZ4v/VD0UA1XT707fYo5v0i5bj42WYdq/P75vTsEJid8OEYhheqb Hk0KrNkC7UbiybJ7zFe7UGD4WfGzHi1CkSGao=
MIME-Version: 1.0
Received: by 10.142.151.22 with SMTP id y22mr1222688wfd.100.1256650975770;  Tue, 27 Oct 2009 06:42:55 -0700 (PDT)
In-Reply-To: <200910271903454689245@gmail.com>
References: <200910271903454689245@gmail.com>
Date: Tue, 27 Oct 2009 21:42:55 +0800
Message-ID: <a7c8d0a30910270642y4613bf82jabd6d75e6caf88c5@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: wudiyetc <wudiyetc@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: liudapeng <liudapeng@chinamobile.com>, mif <mif@ietf.org>
Subject: Re: [mif] draft-liu-mif-api-extension-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2009 13:42:54 -0000

GenericConnection can construct a linked list. Each node on the link
has a pointer to a socket structure.

Thanks,
Zhen

2009/10/27 wudiyetc <wudiyetc@gmail.com>:
>
> hello ,liu
> =A0=A0=A0=A0=A0=A0=A0 In the struct GenericConnection,there is a pointer =
"sock" which
> points to=A0a socket structure.
> But in the section 6.1=A0, it maps two socket =A0to the *gconn, is it a m=
istake?
>
> Wudi ye
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
>

From wudiyetc@gmail.com  Tue Oct 27 17:56:34 2009
Return-Path: <wudiyetc@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688183A69F6 for <mif@core3.amsl.com>; Tue, 27 Oct 2009 17:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.229
X-Spam-Level: **
X-Spam-Status: No, score=2.229 tagged_above=-999 required=5 tests=[AWL=-2.583,  BAYES_00=-2.599, FR_IMPORT_CSS=1.889, HTML_FONT_FACE_BAD=0.884,  HTML_MESSAGE=0.001, HTTP_ESCAPED_HOST=0.134, MIME_8BIT_HEADER=0.3,  MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AbzpABIbODt0 for <mif@core3.amsl.com>; Tue, 27 Oct 2009 17:56:33 -0700 (PDT)
Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by core3.amsl.com (Postfix) with ESMTP id 1B03D3A69E6 for <mif@ietf.org>; Tue, 27 Oct 2009 17:56:32 -0700 (PDT)
Received: by ewy4 with SMTP id 4so310084ewy.37 for <mif@ietf.org>; Tue, 27 Oct 2009 17:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:references :subject:message-id:x-mailer:mime-version:content-type; bh=Jk2vNaVA56NRrgtsMYloakcnGktNpMle8AdT9KZkal4=; b=N+1vGguyiUaep5JgSyMIfDr/BZuq17NAgg2Dip5IRx/opA2L8p8ZbMC5CICa+iTH2X wBCuBYEFeCC9HegHEGu2qV9b/qKgDXV3yt0lSu0H2e9DTxJAi2BJsN8g52hwiEZTzcLT JQDPiRV9gyn7rJhepxS66Xhw/hin5nvvddg7I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:references:subject:message-id:x-mailer:mime-version :content-type; b=Ft72frAMctcEfhFHdVfGa/bOQwwkzIj5CF0jLv7XXu3DoGEBF3GL1Bts5q+K+KG+cB qCrQnKe1Insd7+M1+gkhKQ+IRQIISZ3ObVB642UQRHRafDcCd1HgTV+qkn4TOX7mbWLt UgDRVmALnJTTY4g2flt/BnwuqjkGjwgoQj5dA=
Received: by 10.216.89.14 with SMTP id b14mr2846765wef.76.1256691403291; Tue, 27 Oct 2009 17:56:43 -0700 (PDT)
Received: from bupt-feng ([221.218.192.219]) by mx.google.com with ESMTPS id p37sm1679154gvf.9.2009.10.27.17.56.38 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Oct 2009 17:56:42 -0700 (PDT)
Date: Wed, 28 Oct 2009 08:56:51 +0800
From: "wudiyetc" <wudiyetc@gmail.com>
To: "=?gb2312?B?wfW088X0?=" <liudapeng@chinamobile.com>
References: <200910271909052036827@gmail.com>
Message-ID: <200910280856472815292@gmail.com>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon655276678216_====="
Cc: mif <mif@ietf.org>
Subject: Re: [mif] draft-liu-mif-api-extension-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 00:56:34 -0000

This is a multi-part message in MIME format.

--=====003_Dragon655276678216_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGkgTGl1Og0KDQogICAgICAgSSBoYXZlIG1pc3VuZGVyc3Rvb2QsIEkgYWdyZWUgd2l0aCB5b3Vy
IGV4cGxhaW5hdGlvbi4NCg0KVGhhbmtzLA0KDQpXdWRpDQoNCg0KDQoNCg0Kt6K8/sjLo7ogwfW0
88X0IA0Kt6LLzcqxvOSjuiAyMDA5LTEwLTI3ICAyMDowNDo0NiANCsrVvP7Iy6O6ICd3dWRpeWV0
YycgDQqzrcvNo7ogJ21pZic7ICdDYW8sWmhlbicgDQrW98zio7ogUkU6IGRyYWZ0LWxpdS1taWYt
YXBpLWV4dGVuc2lvbi0wMSANCiANCkhpIFd1ZGksDQogDQpJIGd1ZXNzIHlvdXIgbWFpbCBkb2Vz
IG5vdCBwb3N0IG9uIHRoZSBsaXN0PyBUaGUgc3RydWN0IEdlbmVyaWNDb25uZWN0aW9uIGlzIGEg
bGluayBsaXN0IGFuZCBlYWNoIHNvY2tldCBtYXBzIHRvIG9uZSBub2RlIG9uIHRoZSBsaW5rIGxp
c3QuDQogDQpCUiwNCkRhcGVuZyBMaXUNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCkZyb206IHd1ZGl5ZXRjIFttYWlsdG86d3VkaXlldGNAZ21haWwuY29tXSANClNl
bnQ6IFR1ZXNkYXksIE9jdG9iZXIgMjcsIDIwMDkgNzowOSBQTQ0KVG86IGxpdWRhcGVuZzsgbGl1
ZGFwZW5nOyBsaXVkYXBlbmcNCkNjOiBtaWYNClN1YmplY3Q6IHJlOmRyYWZ0LWxpdS1taWYtYXBp
LWV4dGVuc2lvbi0wMQ0KIA0KIA0KaGVsbG8gLGxpdQ0KICAgICAgICBJbiB0aGUgc3RydWN0IEdl
bmVyaWNDb25uZWN0aW9uLHRoZXJlIGlzIGEgcG9pbnRlciAic29jayIgd2hpY2ggcG9pbnRzIHRv
IGEgc29ja2V0IHN0cnVjdHVyZS4NCkJ1dCBpbiB0aGUgc2VjdGlvbiA2LjEgLCBpdCBtYXBzIHR3
byBzb2NrZXQgIHRvIHRoZSAqZ2Nvbm4sIGlzIGl0IGEgbWlzdGFrZT8gDQogDQpXdWRpIHllDQo=

--=====003_Dragon655276678216_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4bWxu
czp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46c2No
ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczp4ID0gDQoidXJuOnNjaGVtYXMt
bWljcm9zb2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOnAgPSANCiJ1cm46c2NoZW1hcy1taWNy
b3NvZnQtY29tOm9mZmljZTpwb3dlcnBvaW50IiB4bWxuczpvYSA9IA0KInVybjpzY2hlbWFzLW1p
Y3Jvc29mdC1jb206b2ZmaWNlOmFjdGl2YXRpb24iIHhtbG5zOnN0MSA9IA0KInVybjpzY2hlbWFz
LW1pY3Jvc29mdC1jb206b2ZmaWNlOnNtYXJ0dGFncyI+PEhFQUQ+DQo8TUVUQSBodHRwLWVxdWl2
PUNvbnRlbnQtVHlwZSBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9R0IyMzEyIj4NCjxNRVRB
IGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjYwMDAuMTY4OTAiIG5hbWU9R0VORVJBVE9SPjxvOlNtYXJ0
VGFnVHlwZSANCm5hbWU9IlBlcnNvbk5hbWUiIA0KbmFtZXNwYWNldXJpPSJ1cm46c2NoZW1hcy1t
aWNyb3NvZnQtY29tOm9mZmljZTpzbWFydHRhZ3MiPjwvbzpTbWFydFRhZ1R5cGU+PCEtLVtpZiAh
bXNvXT4NCjxTVFlMRT5zdDFcOiogew0KCUJFSEFWSU9SOiB1cmwoI2RlZmF1bHQjaWVvb3VpKQ0K
fQ0KPC9TVFlMRT4NCjwhW2VuZGlmXS0tPg0KPFNUWUxFPkBpbXBvcnQgdXJsKCBmaWxlOi8vL0M6
JTBkb2N1bWVudHMlMjBhbmQlMjBTZXR0aW5nc1wwMEZFbmdMb2NhbCUyMFNldHRpbmdzVGVtcG9y
YXJ5JTIwSW50ZXJuZXQlMjBGaWxlc3Njcm9sbGJhci5jc3MgKTsNCjwvU1RZTEU+DQo8TElOSyBt
ZWRpYT1hbGwgDQpocmVmPSJCTE9DS1FVT1RFJTdibWFyZ2luLVRvcDolMjAwcHg7JTIwbWFyZ2lu
LUJvdHRvbTolMjAwcHg7JTIwbWFyZ2luLUxlZnQ6JTIwMmVtJTdkIiANCnR5cGU9dGV4dC9jc3Mg
cmVsPVN0eWxlc2hlZXQ+DQo8U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IMvOzOU7
DQp9DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWlseTogQMvOzOU7DQp9DQpAZm9udC1mYWNlIHsN
Cglmb250LWZhbWlseTogRGV2aWNlIEZvbnQgMTdjcGk7DQp9DQpAcGFnZSBTZWN0aW9uMSB7c2l6
ZTogNTk1LjNwdCA4NDEuOXB0OyBtYXJnaW46IDcyLjBwdCA5OC4xNXB0IDcyLjBwdCA5OC4xNXB0
OyB9DQpQLk1zb05vcm1hbCB7DQoJRk9OVC1TSVpFOiAxMnB0OyBNQVJHSU4tTEVGVDogMGNtOyBN
QVJHSU4tUklHSFQ6IDBjbTsgRk9OVC1GQU1JTFk6IMvOzOU7IG1zby1tYXJnaW4tdG9wLWFsdDog
YXV0bzsgbXNvLW1hcmdpbi1ib3R0b20tYWx0OiBhdXRvDQp9DQpMSS5Nc29Ob3JtYWwgew0KCUZP
TlQtU0laRTogMTJwdDsgTUFSR0lOLUxFRlQ6IDBjbTsgTUFSR0lOLVJJR0hUOiAwY207IEZPTlQt
RkFNSUxZOiDLzszlOyBtc28tbWFyZ2luLXRvcC1hbHQ6IGF1dG87IG1zby1tYXJnaW4tYm90dG9t
LWFsdDogYXV0bw0KfQ0KRElWLk1zb05vcm1hbCB7DQoJRk9OVC1TSVpFOiAxMnB0OyBNQVJHSU4t
TEVGVDogMGNtOyBNQVJHSU4tUklHSFQ6IDBjbTsgRk9OVC1GQU1JTFk6IMvOzOU7IG1zby1tYXJn
aW4tdG9wLWFsdDogYXV0bzsgbXNvLW1hcmdpbi1ib3R0b20tYWx0OiBhdXRvDQp9DQpBOmxpbmsg
ew0KCUNPTE9SOiBibHVlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BBTi5Nc29I
eXBlcmxpbmsgew0KCUNPTE9SOiBibHVlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0K
QTp2aXNpdGVkIHsNCglDT0xPUjogcHVycGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0K
fQ0KU1BBTi5Nc29IeXBlcmxpbmtGb2xsb3dlZCB7DQoJQ09MT1I6IHB1cnBsZTsgVEVYVC1ERUNP
UkFUSU9OOiB1bmRlcmxpbmUNCn0NClAuTXNvUGxhaW5UZXh0IHsNCglGT05ULVNJWkU6IDEwLjVw
dDsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1GQU1JTFk6IMvOzOUNCn0NCkxJLk1zb1BsYWlu
VGV4dCB7DQoJRk9OVC1TSVpFOiAxMC41cHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7IEZPTlQtRkFN
SUxZOiDLzszlDQp9DQpESVYuTXNvUGxhaW5UZXh0IHsNCglGT05ULVNJWkU6IDEwLjVwdDsgTUFS
R0lOOiAwY20gMGNtIDBwdDsgRk9OVC1GQU1JTFk6IMvOzOUNCn0NClNQQU4uRW1haWxTdHlsZTE5
IHsNCglGT05ULVdFSUdIVDogbm9ybWFsOyBDT0xPUjogYmxhY2s7IEZPTlQtU1RZTEU6IG5vcm1h
bDsgRk9OVC1GQU1JTFk6IMvOzOU7IFRFWFQtREVDT1JBVElPTjogbm9uZTsgbXNvLXN0eWxlLXR5
cGU6IHBlcnNvbmFsDQp9DQpESVYuU2VjdGlvbjEgew0KCXBhZ2U6IFNlY3Rpb24xDQp9DQo8L1NU
WUxFPg0KPCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQogPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0i
ZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KIDxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCiAgPG86aWRtYXAgdjpl
eHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQogPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0t
Pg0KPE1FVEEgY29udGVudD0iTVNIVE1MIDYuMDAuMjkwMC4yMTgwIiBuYW1lPUdFTkVSQVRPUj4N
CjxTVFlMRT5AZm9udC1mYWNlIHsNCglmb250LWZhbWlseTogy87M5TsNCn0NCkBmb250LWZhY2Ug
ew0KCWZvbnQtZmFtaWx5OiBWZXJkYW5hOw0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6
IEDLzszlOw0KfQ0KQHBhZ2UgU2VjdGlvbjEge3NpemU6IDU5NS4zcHQgODQxLjlwdDsgbWFyZ2lu
OiA3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7IGxheW91dC1ncmlkOiAxNS42cHQ7IH0NClAu
TXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6IGludGVyLWlkZW9ncmFwaDsgRk9OVC1TSVpFOiAx
MC41cHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFu
IjsgVEVYVC1BTElHTjoganVzdGlmeQ0KfQ0KTEkuTXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6
IGludGVyLWlkZW9ncmFwaDsgRk9OVC1TSVpFOiAxMC41cHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7
IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIjsgVEVYVC1BTElHTjoganVzdGlmeQ0KfQ0K
RElWLk1zb05vcm1hbCB7DQoJVEVYVC1KVVNUSUZZOiBpbnRlci1pZGVvZ3JhcGg7IEZPTlQtU0la
RTogMTAuNXB0OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVzIE5ldyBS
b21hbiI7IFRFWFQtQUxJR046IGp1c3RpZnkNCn0NCkE6bGluayB7DQoJQ09MT1I6IGJsdWU7IFRF
WFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6
IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpBOnZpc2l0ZWQgew0KCUNPTE9S
OiBwdXJwbGU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLk1zb0h5cGVybGlu
a0ZvbGxvd2VkIHsNCglDT0xPUjogcHVycGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0K
fQ0KU1BBTi5FbWFpbFN0eWxlMTcgew0KCUZPTlQtV0VJR0hUOiBub3JtYWw7IENPTE9SOiB3aW5k
b3d0ZXh0OyBGT05ULVNUWUxFOiBub3JtYWw7IEZPTlQtRkFNSUxZOiBWZXJkYW5hOyBURVhULURF
Q09SQVRJT046IG5vbmU7IG1zby1zdHlsZS10eXBlOiBwZXJzb25hbC1jb21wb3NlDQp9DQpESVYu
U2VjdGlvbjEgew0KCXBhZ2U6IFNlY3Rpb24xDQp9DQpVTktOT1dOIHsNCglGT05ULVNJWkU6IDEw
cHQNCn0NCkJMT0NLUVVPVEUgew0KCU1BUkdJTi1UT1A6IDBweDsgTUFSR0lOLUJPVFRPTTogMHB4
OyBNQVJHSU4tTEVGVDogMmVtDQp9DQpPTCB7DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4tQk9U
VE9NOiAwcHgNCn0NClVMIHsNCglNQVJHSU4tVE9QOiAwcHg7IE1BUkdJTi1CT1RUT006IDBweA0K
fQ0KPC9TVFlMRT4NCjwvSEVBRD4NCjxCT0RZIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IE1BUkdJ
TjogMTBweDsgRk9OVC1GQU1JTFk6IHZlcmRhbmEiPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEg
Y29sb3I9IzAwMDA4MCBzaXplPTI+SGkgTGl1OjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgY29s
b3I9IzAwMDA4MD48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwODA+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEkgaGF2ZSANCm1pc3VuZGVyc3Rv
b2QsIEkgYWdyZWUgd2l0aCB5b3VyIGV4cGxhaW5hdGlvbi48L0ZPTlQ+PC9ESVY+DQo8RElWPjxG
T05UIGNvbG9yPSMwMDAwODA+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0j
MDAwMDgwPlRoYW5rcyw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwODA+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMDgwPld1ZGk8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+
Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBjb2xvcj0jMDAwMDgwIHNpemU9
Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPg0KPEhSIGNvbG9yPSNiNWM0ZGYgU0laRT0xPg0K
PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBzaXplPTI+PFNUUk9ORz63orz+yMujujwv
U1RST05HPiDB9bTzxfQgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6
ZT0yPjxTVFJPTkc+t6LLzcqxvOSjujwvU1RST05HPiAyMDA5LTEwLTI3Jm5ic3A7IDIwOjA0OjQ2
IA0KPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6ZT0yPjxTVFJPTkc+
ytW8/sjLo7o8L1NUUk9ORz4gJ3d1ZGl5ZXRjJyA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZh
Y2U9VmVyZGFuYSBzaXplPTI+PFNUUk9ORz6zrcvNo7o8L1NUUk9ORz4gJ21pZic7ICdDYW8sWmhl
bicgDQo8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBzaXplPTI+PFNUUk9O
Rz7W98zio7o8L1NUUk9ORz4gUkU6IA0KZHJhZnQtbGl1LW1pZi1hcGktZXh0ZW5zaW9uLTAxIDwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hIHNpemU9Mj48L0ZPTlQ+IDwvRElW
Pg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6ZT0yPg0KPERJViBjbGFzcz1TZWN0aW9uMT4N
CjxQIGNsYXNzPU1zb1BsYWluVGV4dD48Rk9OVCBmYWNlPSJEZXZpY2UgRm9udCAxN2NwaSIgc2l6
ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMC41cHQ7IEZPTlQtRkFN
SUxZOiAnRGV2aWNlIEZvbnQgMTdjcGknIj5IaSANCld1ZGksPG86cD48L286cD48L1NQQU4+PC9G
T05UPjwvUD4NCjxQIGNsYXNzPU1zb1BsYWluVGV4dD48Rk9OVCBmYWNlPSJEZXZpY2UgRm9udCAx
N2NwaSIgc2l6ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMC41cHQ7
IEZPTlQtRkFNSUxZOiAnRGV2aWNlIEZvbnQgMTdjcGknIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BB
Tj48L0ZPTlQ+PC9QPg0KPFAgY2xhc3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9IkRldmljZSBG
b250IDE3Y3BpIiBzaXplPTI+PFNQQU4gbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEw
LjVwdDsgRk9OVC1GQU1JTFk6ICdEZXZpY2UgRm9udCAxN2NwaSciPkkgZ3Vlc3MgeW91ciBtYWls
IA0KZG9lcyBub3QgcG9zdCBvbiB0aGUgbGlzdD8gVGhlIHN0cnVjdCBHZW5lcmljQ29ubmVjdGlv
biBpcyBhIGxpbmsgbGlzdCBhbmQgZWFjaCANCnNvY2tldCBtYXBzIHRvIG9uZSBub2RlIG9uIHRo
ZSBsaW5rIGxpc3QuPG86cD48L286cD48L1NQQU4+PC9GT05UPjwvUD4NCjxQIGNsYXNzPU1zb1Bs
YWluVGV4dD48Rk9OVCBmYWNlPSJEZXZpY2UgRm9udCAxN2NwaSIgc2l6ZT0yPjxTUEFOIGxhbmc9
RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMC41cHQ7IEZPTlQtRkFNSUxZOiAnRGV2aWNlIEZv
bnQgMTdjcGknIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPg0KPFAgY2xhc3M9
TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9IkRldmljZSBGb250IDE3Y3BpIiBzaXplPTI+PFNQQU4g
bGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdDsgRk9OVC1GQU1JTFk6ICdEZXZp
Y2UgRm9udCAxN2NwaSciPkJSLDxvOnA+PC9vOnA+PC9TUEFOPjwvRk9OVD48L1A+DQo8UCBjbGFz
cz1Nc29QbGFpblRleHQ+PEZPTlQgZmFjZT0iRGV2aWNlIEZvbnQgMTdjcGkiIHNpemU9Mj48U1BB
TiBsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTAuNXB0OyBGT05ULUZBTUlMWTogJ0Rl
dmljZSBGb250IDE3Y3BpJyI+RGFwZW5nIA0KTGl1PG86cD48L286cD48L1NQQU4+PC9GT05UPjwv
UD4NCjxQIGNsYXNzPU1zb1BsYWluVGV4dD48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjxTUEFOIGxh
bmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMC41cHQiPl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPg0KPFAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9y87M5SBzaXplPTI+PFNQQU4gbGFuZz1FTi1VUyAN
CnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdCI+RnJvbTogd3VkaXlldGMgW21haWx0bzp3dWRpeWV0
Y0BnbWFpbC5jb21dIA0KPG86cD48L286cD48L1NQQU4+PC9GT05UPjwvUD4NCjxQIGNsYXNzPU1z
b1BsYWluVGV4dD48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHls
ZT0iRk9OVC1TSVpFOiAxMC41cHQiPlNlbnQ6IFR1ZXNkYXksIE9jdG9iZXIgMjcsIDIwMDkgNzow
OSANClBNPG86cD48L286cD48L1NQQU4+PC9GT05UPjwvUD4NCjxQIGNsYXNzPU1zb1BsYWluVGV4
dD48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1T
SVpFOiAxMC41cHQiPlRvOiA8c3QxOlBlcnNvbk5hbWUgDQp3OnN0PSJvbiI+bGl1ZGFwZW5nPC9z
dDE6UGVyc29uTmFtZT47IDxzdDE6UGVyc29uTmFtZSANCnc6c3Q9Im9uIj5saXVkYXBlbmc8L3N0
MTpQZXJzb25OYW1lPjsgPHN0MTpQZXJzb25OYW1lIA0KdzpzdD0ib24iPmxpdWRhcGVuZzwvc3Qx
OlBlcnNvbk5hbWU+PG86cD48L286cD48L1NQQU4+PC9GT05UPjwvUD4NCjxQIGNsYXNzPU1zb1Bs
YWluVGV4dD48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0i
Rk9OVC1TSVpFOiAxMC41cHQiPkNjOiBtaWY8bzpwPjwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPg0K
PFAgY2xhc3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9y87M5SBzaXplPTI+PFNQQU4gbGFuZz1F
Ti1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdCI+U3ViamVjdDogDQpyZTpkcmFmdC1saXUt
bWlmLWFwaS1leHRlbnNpb24tMDE8bzpwPjwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPg0KPFAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9y87M5SBzaXplPTI+PFNQQU4gbGFuZz1FTi1VUyAN
CnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdCI+PG86cD4mbmJzcDs8L286cD48L1NQQU4+PC9GT05U
PjwvUD4NCjxQIGNsYXNzPU1zb1BsYWluVGV4dD48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4i
IHNpemU9Mj48U1BBTiBsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTAuNXB0OyBGT05U
LUZBTUlMWTogJ1RpbWVzIE5ldyBSb21hbiciPiZuYnNwOzwvU1BBTj48L0ZPTlQ+PFNQQU4gDQps
YW5nPUVOLVVTPjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCjxQIGNsYXNzPU1zb1BsYWluVGV4dD48
Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpF
OiAxMC41cHQiPmhlbGxvICxsaXU8bzpwPjwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPg0KPFAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiIgc2l6ZT0yPjxTUEFO
IGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMC41cHQ7IEZPTlQtRkFNSUxZOiAnVGlt
ZXMgTmV3IFJvbWFuJyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
PC9TUEFOPjwvRk9OVD48U1BBTiANCmxhbmc9RU4tVVM+IEluIHRoZSBzdHJ1Y3QgR2VuZXJpY0Nv
bm5lY3Rpb24sdGhlcmUgaXMgYSBwb2ludGVyICJzb2NrIiB3aGljaCANCnBvaW50cyB0bzwvU1BB
Tj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0i
Rk9OVC1GQU1JTFk6ICdUaW1lcyBOZXcgUm9tYW4nIj4mbmJzcDs8L1NQQU4+PC9GT05UPjxTUEFO
IGxhbmc9RU4tVVM+YSANCnNvY2tldCBzdHJ1Y3R1cmUuPG86cD48L286cD48L1NQQU4+PC9QPg0K
PFAgY2xhc3M9TXNvUGxhaW5UZXh0PjxGT05UIGZhY2U9y87M5SBzaXplPTI+PFNQQU4gbGFuZz1F
Ti1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdCI+QnV0IGluIHRoZSBzZWN0aW9uIDYuMTwv
U1BBTj48L0ZPTlQ+PEZPTlQgDQpmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxTUEFOIGxhbmc9RU4t
VVMgDQpzdHlsZT0iRk9OVC1GQU1JTFk6ICdUaW1lcyBOZXcgUm9tYW4nIj4mbmJzcDs8L1NQQU4+
PC9GT05UPjxTUEFOIGxhbmc9RU4tVVM+LCBpdCANCm1hcHMgdHdvIHNvY2tldCA8L1NQQU4+PEZP
TlQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48U1BBTiBsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQt
RkFNSUxZOiAnVGltZXMgTmV3IFJvbWFuJyI+Jm5ic3A7PC9TUEFOPjwvRk9OVD48U1BBTiBsYW5n
PUVOLVVTPnRvIA0KdGhlICpnY29ubiwgaXMgaXQgYSBtaXN0YWtlPyA8bzpwPjwvbzpwPjwvU1BB
Tj48L1A+DQo8UCBjbGFzcz1Nc29QbGFpblRleHQ+PEZPTlQgZmFjZT0iVGltZXMgTmV3IFJvbWFu
IiBzaXplPTI+PFNQQU4gbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwLjVwdDsgRk9O
VC1GQU1JTFk6ICdUaW1lcyBOZXcgUm9tYW4nIj4mbmJzcDs8L1NQQU4+PC9GT05UPjxTUEFOIA0K
bGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQo8UCBjbGFzcz1Nc29QbGFpblRleHQ+
PEZPTlQgZmFjZT3LzszlIHNpemU9Mj48U1BBTiBsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0la
RTogMTAuNXB0Ij5XdWRpIA0KeWU8bzpwPjwvbzpwPjwvU1BBTj48L0ZPTlQ+PC9QPjwvRElWPjwv
Rk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--=====003_Dragon655276678216_=====--


From lars.eggert@nokia.com  Wed Oct 28 01:11:54 2009
Return-Path: <lars.eggert@nokia.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C29933A6895; Wed, 28 Oct 2009 01:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEYTk4ffKilt; Wed, 28 Oct 2009 01:11:54 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id BF04B3A67C1; Wed, 28 Oct 2009 01:11:53 -0700 (PDT)
Received: from [IPv6:2001:708:40:fff2:225:ff:fe45:eccf] (lars.local [IPv6:2001:708:40:fff2:225:ff:fe45:eccf] (may be forged)) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n9S8C1kA074942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 28 Oct 2009 10:12:01 +0200 (EET) (envelope-from lars.eggert@nokia.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: multipart/signed; boundary=Apple-Mail-19--762552916; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4A916DBC72536E419A0BD955EDECEDEC06363A01@E03MVB1-UKBR.domain1.systemhost.net>
Date: Wed, 28 Oct 2009 10:12:01 +0200
Message-Id: <99F507ED-FDC7-4468-BBF2-4EFE63718BD8@nokia.com>
References: <4A916DBC72536E419A0BD955EDECEDEC06363A01@E03MVB1-UKBR.domain1.systemhost.net>
To: mif <mif@ietf.org>
X-Mailer: Apple Mail (2.1076)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [IPv6:2001:708:40:fff1::1]); Wed, 28 Oct 2009 10:12:01 +0200 (EET)
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [mif] [multipathtcp] draft agenda for MPTCP WG Meeting
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 08:11:54 -0000

--Apple-Mail-19--762552916
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252;
	format=flowed;
	delsp=yes

Hi, MIF WG,

On 2009-10-27, at 20:15, philip.eardley@bt.com wrote:
> 8.  Host routing [10mins] =96 Mark Handley

I think this presentation (and draft draft-handley-mptcp-routing in =20
general) are interesting to you as well.

Lars=

--Apple-Mail-19--762552916
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw
ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X
uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY
Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB
6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT
VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr
ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu
ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt
I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H
5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80
QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT
BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg
Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG
A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA
A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK
MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw
QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl
ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl
TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M
Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq
BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP
6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTA5MTAyODA4MTIwMVowIwYJKoZIhvcNAQkEMRYEFJEcEYVf5qd6Q09i17nPg0mTfvg6MIGF
BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF
AASCAQDlA7M+GLWQahMDvGhWMg9X5N+js1MHJPz4XTELBMaRdrFPkvfZh3tNM3HRKGaAXrz5zEBl
/8dGDoKa/nzwHsuq/RiRJLVK6YSVcZzgIssnGu3MMEp50JRO7Vj/a3/t0US6Bwef+MJnjKlBKhaX
pVfHvB09wJeriwn2BKpuxxTw3y8slHJCFlymog97lKyV+5dz0jlPgkaVBv1Hdq44eqlhCWHI9mz7
EqZEgz40Yd5muyohsdZWCPwi4GVfUGWRxtaZinAwnKvBR40v5bHMZ/bik3Ww3X6+IVJR1mVCA8tl
38fMsy63KMmY4+zxqoAdJL/D0UCfC4u+4iqw+eZL5j1XAAAAAAAA

--Apple-Mail-19--762552916--

From caozhenpku@gmail.com  Wed Oct 28 07:06:53 2009
Return-Path: <caozhenpku@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D361328C148; Wed, 28 Oct 2009 07:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level: 
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[AWL=0.455,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gvDLEVZfEwj; Wed, 28 Oct 2009 07:06:53 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id 100913A67AB; Wed, 28 Oct 2009 07:06:53 -0700 (PDT)
Received: by pxi3 with SMTP id 3so589169pxi.29 for <multiple recipients>; Wed, 28 Oct 2009 07:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DW3PQPyl2ZjuuhbA7JgEsk67sqSIocDJceo6pRrEkVo=; b=hOma9qGfRv4H8UmTFc/ah37nCS7APgf7WunIV8ZSBhdejzVl2TpTYT/mlbITsNh3J/ B/+kd+QSOqnJ/EdXgRpQ/Ne+U4dkVmwzr6R22zAPLaOzqs1EbrN84kYQ6F8/ahiOYuUI yayrX40hzxc6kQkzeKpcI0vZ72nHXiLY6rJ4k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=cPrG4CsYxhGpOHaJIWuvUbsFUkgFC1+u3TNNjvPfaEq7WScf2i8pCniBcarHWUtT5I XfWMbbMfCU7lHAXmpaIlZxjBff2q3Vm/uF6agKrlbPu8WPOBPxyaUQ/DCeSAV+9VmOAr jarT6rcdTRCCVYsnVflshrkCFDrcNvul0GUd0=
MIME-Version: 1.0
Received: by 10.142.151.22 with SMTP id y22mr1382342wfd.100.1256738826626;  Wed, 28 Oct 2009 07:07:06 -0700 (PDT)
In-Reply-To: <99F507ED-FDC7-4468-BBF2-4EFE63718BD8@nokia.com>
References: <4A916DBC72536E419A0BD955EDECEDEC06363A01@E03MVB1-UKBR.domain1.systemhost.net> <99F507ED-FDC7-4468-BBF2-4EFE63718BD8@nokia.com>
Date: Wed, 28 Oct 2009 22:07:06 +0800
Message-ID: <a7c8d0a30910280707q1bb5f2d1kc27f38a96a14844@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Lars Eggert <lars.eggert@nokia.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, mif <mif@ietf.org>
Subject: Re: [mif] [multipathtcp] draft agenda for MPTCP WG Meeting
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 14:06:53 -0000

Thanks for your information.

Previously I thought mp-tcp might not touch the host routing stack and
would work under the assumption that host routing being solved. This
draft talks about how MP-TCP should interact with host routing
mechanism. It is an effective way to support a MIF host. But given the
potential diversity of host routing mechanisms, we may prefer do this
in a more general way. MIF is currently working on some informational
documents, but i believe there is a need of a specific host based
routing mechanisms?

On Wed, Oct 28, 2009 at 4:12 PM, Lars Eggert <lars.eggert@nokia.com> wrote:
> Hi, MIF WG,
>
> On 2009-10-27, at 20:15, philip.eardley@bt.com wrote:
>>
>> 8. =A0Host routing [10mins] =96 Mark Handley
>
> I think this presentation (and draft draft-handley-mptcp-routing in gener=
al)
> are interesting to you as well.
>
> Lars
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
>

From denghui02@gmail.com  Wed Oct 28 07:43:36 2009
Return-Path: <denghui02@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B91F63A682B for <mif@core3.amsl.com>; Wed, 28 Oct 2009 07:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxZFykAgJ8s5 for <mif@core3.amsl.com>; Wed, 28 Oct 2009 07:43:35 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by core3.amsl.com (Postfix) with ESMTP id 6C4B128C1C9 for <mif@ietf.org>; Wed, 28 Oct 2009 07:43:32 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 9so248537qwb.31 for <mif@ietf.org>; Wed, 28 Oct 2009 07:43:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=RG8msZwVfZd9gV6D+3U9DDK3E1jwAZuLQODAzFFgu2I=; b=GhSIeMWar8B/SjtAi3JTXzPvOwUS+3Hj5jPz5EQjcpElfKPcAdAgMfVjXACmhg94o6 wowxCitKCv/tb42gCpP91WyDYUJpzQy3hKxLJdoVliqdtjDTMyfX1kBh41VHw+6yGYmp 8IhkuiMbcDBdPFYwgWzg9BLzW1IHAjdFKiD+A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VVrv0L1gVjnDGLy/QKtOCXUJ3cPoD1EEza1LCP5dgDKzny26XqjjoX8pKeSv9z9HaA VLhWM8ubuQI9MxPxzVa6iEqohh8NVASkGivrOqYvA5KkVDe6RLjPqyJuXc2tuzm/mWpc Jxl1F2ERXsNQ71twGCZxzYNwp3EmpYXHrlE/k=
MIME-Version: 1.0
Received: by 10.224.29.75 with SMTP id p11mr9256748qac.88.1256741023182; Wed,  28 Oct 2009 07:43:43 -0700 (PDT)
Date: Wed, 28 Oct 2009 22:43:43 +0800
Message-ID: <1d38a3350910280743l6328a825q6df11ff6b0a63080@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, Margaret Wasserman <mrw@lilacglade.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [mif] MIF next meeting
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 14:43:36 -0000

Hello, all

If you would like to get a time slot for the coming MIF meeting.
Please feel free to let chairs know it,

thanks

-Hui

From denghui02@hotmail.com  Sat Oct 31 20:50:23 2009
Return-Path: <denghui02@hotmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22A223A6359 for <mif@core3.amsl.com>; Sat, 31 Oct 2009 20:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCecOj3w6AgY for <mif@core3.amsl.com>; Sat, 31 Oct 2009 20:50:22 -0700 (PDT)
Received: from col0-omc2-s13.col0.hotmail.com (col0-omc2-s13.col0.hotmail.com [65.55.34.87]) by core3.amsl.com (Postfix) with ESMTP id 5C1E83A67ED for <mif@ietf.org>; Sat, 31 Oct 2009 20:50:22 -0700 (PDT)
Received: from COL118-W52 ([65.55.34.71]) by col0-omc2-s13.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 31 Oct 2009 20:49:33 -0700
Message-ID: <COL118-W52DB972879F2B26C128F8EB1B40@phx.gbl>
Content-Type: multipart/alternative; boundary="_634998ac-3542-4205-bc27-3262d71d430f_"
X-Originating-IP: [222.129.39.245]
From: Hui Deng <denghui02@hotmail.com>
To: <mif@ietf.org>, <mrw@lilacglade.org>
Date: Sun, 1 Nov 2009 11:49:33 +0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Nov 2009 03:49:33.0963 (UTC) FILETIME=[532735B0:01CA5AA6]
Subject: [mif] Draft agenda posted
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2009 03:50:23 -0000

--_634998ac-3542-4205-bc27-3262d71d430f_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: 8bit


Hello ,all

 

The draft agenda has been posted, if you would like to have further

proposal for the time slot, feel free to let chairs know it,

 

thanks

 

-Hui
 		 	   		  
_________________________________________________________________
Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010
--_634998ac-3542-4205-bc27-3262d71d430f_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: 8bit

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hello ,all<BR>
&nbsp;<BR>
The draft agenda has been posted, if you would like to have further<BR>
proposal for the time slot, feel free to let chairs know it,<BR>
&nbsp;<BR>
thanks<BR>
&nbsp;<BR>
-Hui<BR> 		 	   		  <br /><hr />Windows Live:  <a href='http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010' target='_new'>Friends get your Flickr, Yelp, and Digg updates when they e-mail you.</a></body>
</html>
--_634998ac-3542-4205-bc27-3262d71d430f_--
