From yonggeun.hong@gmail.com Mon Jul 13 22:51:02 2009 Return-Path: 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 8EEF33A6C06 for ; Mon, 13 Jul 2009 22:51:02 -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 fz5xfkrWAhRS for ; Mon, 13 Jul 2009 22:51:01 -0700 (PDT) Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id 93AF73A6A27 for ; Mon, 13 Jul 2009 22:51:01 -0700 (PDT) Received: by pzk36 with SMTP id 36so3191429pzk.29 for ; Mon, 13 Jul 2009 22:50:07 -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:cc:content-type; bh=8WQbdyIUpaJxPH326qJrvgBtNXpS6hJK3bu9prQ09WU=; b=I3aCZ3leONfE6RjxpoJ1ylP5rQ1y4jKCPRUYDgbDiRd9d8V7w+f1x9xspaSiK7ooW5 YHzZC7oH7tb1JDJi1KZMwGfWm9jx03LaGAu30eYUBzhHCJFLBTl8Oe875r6IsYdowuOW bGm5PatXbsCMSVmJZyyL6OlE+4ja7HSvy5ciA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=KqYBDz2SMVUYBOIpJ4elYLaUWWTKHu+Zq6lZEfIKS+tmEo6y+TAFCLKAw22teZP2cl /GuiVtb/9LVFWlMjOzZ20OaSKC96lT0m8FAp5UC55KTmKTTR/vXcTvd8opu1o9gHN6j8 aoGp/wDb8bakVDj+vnvMVvAPeoGsoWUO9mKNM= MIME-Version: 1.0 Received: by 10.142.233.9 with SMTP id f9mr1804800wfh.245.1247550606947; Mon, 13 Jul 2009 22:50:06 -0700 (PDT) Date: Tue, 14 Jul 2009 14:50:06 +0900 Message-ID: <5a95ea190907132250t50522910we3d5a4da22e1bca8@mail.gmail.com> From: Yong-Geun Hong To: mif Content-Type: multipart/alternative; boundary=000e0cd2e2f8c4362a046ea40255 Cc: trungtm2909@gmail.com Subject: [mif] FW: I-D Action:draft-hong-mif-analysis-scenario-01.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2009 05:51:02 -0000 --000e0cd2e2f8c4362a046ea40255 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, all. We update "Analysis and scenarios of multiple interfaces in a host" It is appreciate to comment. Best regards. Yong-Geun. -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, July 13, 2009 8:00 PM To: i-d-announce@ietf.org Subject: I-D Action:draft-hong-mif-analysis-scenario-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Analysis and scenarios of multiple interfaces in a host Author(s) : Y. Hong, et al. Filename : draft-hong-mif-analysis-scenario-01.txt Pages : 29 Date : 2009-07-13 This document includes an analysis of multiple interfaces in a host and a description of scenarios of multiple interfaces with the respect of the relationship between layer 2 connection and layer 3 connection. The current TCP/IP mechanism and networking methods are suitable for single network interface. When a host has multiple interfaces, the current TCP/IP mechanism and networking methods cannot directly be used for them. A network interface establishes layer 2 connection to layer 2 entity (e.g., WLAN Access Point) and it does not mean providing proper layer 3 connection. So every active network interfaces do not guarantee successful IP layer operations. In this document, we describe some problems for a host which has multiple interfaces as an aspect of host's operations and usage scenarios of multiple interfaces in a host. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hong-mif-analysis-scenario-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. --000e0cd2e2f8c4362a046ea40255 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, all.
=C2=A0
We update "Analysis and scenarios of multiple interfaces in a hos= t"
=C2=A0
It is appreciate to comment.
=C2=A0
Best regards.
=C2=A0
Yong-Geun.
=C2=A0
=C2=A0

-----Original Message-----
From: i-d-announce-bounces@ietf.org [m= ailto:i-d-announce-bounces= @ietf.org] On Behalf Of Int= ernet-Drafts@ietf.org
Sent: Monday, July 13, 2009 8:00 PM
To: i-d-announce@ietf.org
Subject: I-D Action:draft-hong-mif-an= alysis-scenario-01.txt

=C2=A0

A New Internet-Draft is available from the on-= line Internet-Drafts directories.

=C2=A0

=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Title=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : Analysis= and scenarios of multiple interfaces in a host

=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Author(s)= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : Y. Hong, et al.=

=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Filename= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : draft-hong-mif-analysis= -scenario-01.txt

=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Pages=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 29

=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Date=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 20= 09-07-13

=C2=A0

This document includes an analysis of multiple= interfaces in a host and a description of scenarios of multiple interfaces= with the respect of the relationship between layer 2 connection and layer = 3 connection.=C2=A0 The current TC= P/IP mechanism and networking methods are suitable for single network inter= face.=C2=A0 When a host has multip= le interfaces, the current TCP/IP mechanism and networking methods cannot d= irectly be used for them.=C2=A0 A = network interface establishes layer 2 connection to layer 2 entity (e.g., W= LAN Access Point) and it does not mean providing proper layer 3 connection.= =C2=A0 So every active network int= erfaces do not guarantee successful IP layer operations.

In this document, we describe some problems fo= r a host which has multiple interfaces as an aspect of host's operation= s and usage scenarios of multiple interfaces in a host.

=C2=A0

A URL for this Internet-Draft is:

http://www.ietf.org/internet-draf= ts/draft-hong-mif-analysis-scenario-01.txt

=C2=A0

Internet-Drafts are also available by anonymou= s FTP at:

ftp://ftp.ietf.org/internet-drafts/

=C2=A0

Below is the data which will enable a MIME com= pliant mail reader implementation to automatically retrieve the ASCII versi= on of the Internet-Draft.

--000e0cd2e2f8c4362a046ea40255-- From denghui02@gmail.com Wed Jul 15 08:19:50 2009 Return-Path: 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 736AB3A6E51 for ; Wed, 15 Jul 2009 08:19:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.511 X-Spam-Level: X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 Wu9t8eSNzcWB for ; Wed, 15 Jul 2009 08:19:49 -0700 (PDT) Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id BA5623A6CE9 for ; Wed, 15 Jul 2009 08:19:49 -0700 (PDT) Received: by mail-pz0-f198.google.com with SMTP id 36so4290110pzk.29 for ; Wed, 15 Jul 2009 08:20:22 -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:content-transfer-encoding; bh=zcCof45I/tN7rUN+2sWC6999bBQuc9SRSsLt6M/lSH0=; b=Bdb/qGOpnL+Qn7sWsdaEejS9bL3eDH7f268IZUYqC2dYp9P4k/u9kMvLxH30xUpqLj //OZ9M4oUMM99eN/fPiRGnZmpDCxjmfTRO+eqK/pupjkIiL9LYIaOtFGQjLyibmql1NG hAc4fCGqIdBOZlSAByiwqwweZKTIZBBJL71Zw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=khzOuyxkOUgAWIUhx+cRsvC0eYWzvIhjger4RK+ECjSWs7ro/L/RRif1Fd6ci8/U72 9OcgjLoadkZ+9FgHrq6mAcu+gQl4oz9mrtVCHZZirgiUW7e39JihsLOenIHfXcTOt6JY vpq/+9NnpNpApe5EmkH62ZrEg5+cnUovxCvRY= MIME-Version: 1.0 Received: by 10.143.15.11 with SMTP id s11mr1872530wfi.319.1247671222167; Wed, 15 Jul 2009 08:20:22 -0700 (PDT) Date: Wed, 15 Jul 2009 23:20:22 +0800 Message-ID: <1d38a3350907150820k329cf007ic0eacde89f9e65ab@mail.gmail.com> From: Hui Deng To: MIF Mailing List , Margaret Wasserman , Hui Deng Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [mif] draft mif agenda X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2009 15:19:50 -0000 Greeting all, We finally will have the 1st time working group meeting. the ML have a long time silence after the forming of the working group. We would like to encourage people to review MIF PS draft again. For the coming 75th meeting, we have to be careful about the current charter scope. The possible candidates for the time slot could be: 1) presentations of current practice, 2) discussion of requirements, 3) discussion of how existing IETF standards apply to the problem, etc. Under this consideration, the draft agenda will be: 1. Agenda, Greeting for 1st WG meeting (Chairs, 10 min) 2. MIF Problem Statement (Marc, 1 hour) 3. MIF Current Practices (Margaret, 15 min) 4. Other MIF related drafts (1 hour) 5. Questions & Next Steps (Chairs/ADs, 10 min) Thanks -Chairs From denghui02@hotmail.com Thu Jul 23 16:49:00 2009 Return-Path: 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 219B93A6C5A for ; Thu, 23 Jul 2009 16:49:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.105 X-Spam-Level: * X-Spam-Status: No, score=1.105 tagged_above=-999 required=5 tests=[AWL=0.369, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_OBFU_ONLINE_SUB=3.333] 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 tfmrzeynFY1C for ; Thu, 23 Jul 2009 16:48:59 -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 655EF3A696A for ; Thu, 23 Jul 2009 16:48:33 -0700 (PDT) Received: from COL118-W19 ([65.55.34.71]) by col0-omc2-s13.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 16:48:34 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_2c58370a-8a82-4f69-9384-ad1ea91750eb_" X-Originating-IP: [221.223.71.205] From: Hui Deng To: Date: Fri, 24 Jul 2009 07:48:34 +0800 Importance: Normal In-Reply-To: <20090723193046.7716D3A6A6A@core3.amsl.com> References: <20090723193046.7716D3A6A6A@core3.amsl.com> MIME-Version: 1.0 X-OriginalArrivalTime: 23 Jul 2009 23:48:34.0447 (UTC) FILETIME=[174D29F0:01CA0BF0] X-Mailman-Approved-At: Thu, 23 Jul 2009 16:59:30 -0700 Subject: [mif] FW: 75th IETF - Oneline Regsitration and Payment Cutoff X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2009 23:49:00 -0000 --_2c58370a-8a82-4f69-9384-ad1ea91750eb_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable =20 > From: ietf-secretariat@ietf.org > To: ietf-announce@ietf.org > Subject: 75th IETF - Oneline Regsitration and Payment Cutoff=20 > Date: Thu=2C 23 Jul 2009 12:30:46 -0700 > CC: irsg@isi.edu=3B 75all@ietf.org=3B bofchairs@ietf.org=3B wgchairs@ietf= .org >=20 > 75th IETF Meeting=20 > Stockholm=2C Sweden=20 > July 26-31=2C 2009=20 > Host: .SE=20 >=20 > Online registration and payment closes 17:00 PDT=2C Friday=2C 24 July 200= 9=20 > (24:00 UTC/GMT). After 24 July 2009=2C all payments (whether or not you=20 > have pre-registered) and registrations must be made on-site. A late fee=20 > will apply.=20 >=20 > Online registration for the IETF meeting is at:=20 > http://www.ietf.org/meeting/75/=20 >=20 > Only 3 days until the Stockholm IETF!=20 >=20 _________________________________________________________________ Drag n=92 drop=97Get easy photo sharing with Windows Live=99 Photos. http://www.microsoft.com/windows/windowslive/products/photos.aspx= --_2c58370a-8a82-4f69-9384-ad1ea91750eb_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
 =3B
>=3B From: ietf-secretariat@ietf.org
>=3B To: ietf-a= nnounce@ietf.org
>=3B Subject: 75th IETF - Oneline Regsitration and Pa= yment Cutoff
>=3B Date: Thu=2C 23 Jul 2009 12:30:46 -0700
>=3B C= C: irsg@isi.edu=3B 75all@ietf.org=3B bofchairs@ietf.org=3B wgchairs@ietf.or= g
>=3B
>=3B 75th IETF Meeting
>=3B Stockholm=2C Sweden >=3B July 26-31=2C 2009
>=3B Host: .SE
>=3B
>=3B Onlin= e registration and payment closes 17:00 PDT=2C Friday=2C 24 July 2009
&= gt=3B (24:00 UTC/GMT). After 24 July 2009=2C all payments (whether or not y= ou
>=3B have pre-registered) and registrations must be made on-site. = A late fee
>=3B will apply.
>=3B
>=3B Online registration= for the IETF meeting is at:
>=3B http://www.ietf.org/meeting/75/ >=3B
>=3B Only 3 days until the Stockholm IETF!
>=3B
What can you do with the new Windows Live? Find out= = --_2c58370a-8a82-4f69-9384-ad1ea91750eb_-- From mrw@sandstorm.net Sat Jul 25 08:17:09 2009 Return-Path: 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 E0AFB3A686D for ; Sat, 25 Jul 2009 08:17:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.265 X-Spam-Level: X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] 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 0N0IDMoufWVd for ; Sat, 25 Jul 2009 08:17:09 -0700 (PDT) Received: from sirocco.sandstorm.net (sirocco.sandstorm.net [69.33.111.75]) by core3.amsl.com (Postfix) with ESMTP id 1825F3A67F2 for ; Sat, 25 Jul 2009 08:17:08 -0700 (PDT) Received: from [10.36.0.42] (pool-173-76-25-94.bstnma.fios.verizon.net [173.76.25.94]) (authenticated bits=0) by sirocco.sandstorm.net (8.13.8/8.13.3) with ESMTP id n6PFGBSj016283 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 25 Jul 2009 11:16:11 -0400 (EDT) (envelope-from mrw@sandstorm.net) Message-Id: <3E5D6193-730A-4FF5-9FB5-743013330C3C@sandstorm.net> From: Margaret Wasserman To: mif Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 25 Jul 2009 11:16:11 -0400 X-Mailer: Apple Mail (2.935.3) Subject: [mif] Updated Agenda with Drafts X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2009 15:17:10 -0000 Here is an updated draft of the MIF agenda for Tuesday, with the drafts listed. Please read the drafts before the meeting, so that we can have a meaningful discussion. If there is anything else that you would like to discuss in the meeting, please let us know. Thanks, Margaret MIF WG Agenda IETF75 - Stockholm, Sweden Tuesday, July 28, 2009 0900-1130, Large Stage ========================== 1. Agenda, Greeting for 1st WG meeting (Chairs, 10 min) 2. MIF Problem Statement (Marc, 1 hour) http://www.ietf.org/id/draft-blanchet-mif-problem-statement-01.txt http://www.ietf.org/id/draft-williams-mif-problem-scenarios-00.txt 3. MIF Current Practices (Margaret, 15 min) http://www.ietf.org/id/draft-mrw-mif-current-practices-02.txt 4. Other MIF related drafts (1 hour) http://www.ietf.org/id/draft-hong-mif-analysis-scenario-01.txt http://www.ietf.org/id/draft-ko-mif-security-considerations-00.txt http://www.ietf.org/id/draft-savolainen-mif-dns-server-selection-00.txt 5. Questions & Next Steps (Chairs/ADs, 10 min) From jeanmichel.combes@gmail.com Tue Jul 28 02:14:14 2009 Return-Path: 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 F2B1F3A6ADE for ; Tue, 28 Jul 2009 02:14:13 -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 dyHjSSvk77JP for ; Tue, 28 Jul 2009 02:14:13 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by core3.amsl.com (Postfix) with ESMTP id 450643A68E7 for ; Tue, 28 Jul 2009 02:14:08 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id e12so604319fga.18 for ; Tue, 28 Jul 2009 02:14:05 -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:content-transfer-encoding; bh=DtGOuuiF2jiE+XajqcpLK1KXDXf0kFN2XCSLBnOwwfU=; b=QxLSer0txYhTUaB5Dx4dAXHQlQ5rXZo0Tl9ihBksTgL/0TgjM/2EiXZgKsfI5+OZsZ WCcGhevO8xzvzJaV6V1kUXKSRS2WKIMUN/g4dDbGmsxUtEXNsEjZQHp9c1m0GOs8M51I p4JMAS6XsxZkyUDUsbBuEspphIUhIYPoDUmVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=OrkZCg+qoTND4vDzDeYRwZVWNUY3yHmNkt1SaGHyu6w6BI3m4Nhhvu0cXjS8/QMvJc ak/lFNFCrnbYRs77QM9wI8XhONjOem6gizfefJ+b/tq+lwsGV/weDPxfpnt0j2f6+IFI VXGuZgNW3Aw6qMxfhZbZss1S/EiMRSOaOJ+v4= MIME-Version: 1.0 Received: by 10.86.97.17 with SMTP id u17mr3439998fgb.55.1248772445783; Tue, 28 Jul 2009 02:14:05 -0700 (PDT) Date: Tue, 28 Jul 2009 11:14:05 +0200 Message-ID: <729b68be0907280214t31452badka4f11ab85d6b2f29@mail.gmail.com> From: Jean-Michel Combes To: mif@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [mif] Questions on the draft-ko-mif-security-considerations presentation during the IETF meeting X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 09:14:14 -0000 Hi, On the presentation slides, IIRC, it is said that "MIF must not prevent the leakage of confidential information from one interface to other interfaces.". But, in the draft, it is said the opposite (i.e. "MIF must prevent the leakage of confidential information from one interface to other interfaces."). What is the correct requirement (I assume the one in the draft but I would like to have a confirmation)? What are the reasons of such a requirement (e.g. a potential attack scenario)? Thanks in advance. Best regards. JMC. From william.d.ivancic@nasa.gov Tue Jul 28 02:26:47 2009 Return-Path: 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 1EA5C3A6CEF for ; Tue, 28 Jul 2009 02:26:47 -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 ZmIDp0Iu3oHz for ; Tue, 28 Jul 2009 02:26:46 -0700 (PDT) Received: from ndjsnpf03.ndc.nasa.gov (ndjsnpf03.ndc.nasa.gov [198.117.1.123]) by core3.amsl.com (Postfix) with ESMTP id 53E893A69E0 for ; Tue, 28 Jul 2009 02:26:46 -0700 (PDT) Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102]) by ndjsnpf03.ndc.nasa.gov (Postfix) with ESMTP id 397DB2D8093; Tue, 28 Jul 2009 04:26:01 -0500 (CDT) Received: from ndjshub01.ndc.nasa.gov (ndjshub01.ndc.nasa.gov [198.117.4.160]) by ndjsppt03.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id n6S9Q1iN001254; Tue, 28 Jul 2009 04:26:01 -0500 Received: from NDJSSCC03.ndc.nasa.gov ([198.117.4.170]) by ndjshub01.ndc.nasa.gov ([198.117.4.160]) with mapi; Tue, 28 Jul 2009 04:26:01 -0500 From: "Ivancic, William D. (GRC-RHN0)" To: Jean-Michel Combes , "mif@ietf.org" Date: Tue, 28 Jul 2009 04:25:58 -0500 Thread-Topic: [mif] Questions on the draft-ko-mif-security-considerations presentation during the IETF meeting Thread-Index: AcoPY9xe5uw1zKVOTJeNAW9rk1RQ1QAARZrA Message-ID: <3A5AA67A8B120B48825BFFCF544385614A608CBA3D@NDJSSCC03.ndc.nasa.gov> References: <729b68be0907280214t31452badka4f11ab85d6b2f29@mail.gmail.com> In-Reply-To: <729b68be0907280214t31452badka4f11ab85d6b2f29@mail.gmail.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-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4, 1.2.40, 4.0.166 definitions=2009-07-28_04:2009-07-24, 2009-07-28, 2009-07-27 signatures=0 Subject: Re: [mif] Questions on the draft-ko-mif-security-considerations presentation during the IETF meeting X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 09:26:47 -0000 >-----Original Message----- >From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of >Jean-Michel Combes >Sent: Tuesday, July 28, 2009 5:14 AM >To: mif@ietf.org >Subject: [mif] Questions on the draft-ko-mif-security-considerations >presentation during the IETF meeting > >Hi, > I believe the following is in error: >On the presentation slides, IIRC, it is said that "MIF must not >prevent the leakage of confidential information from one interface to >other interfaces.". I believe the following is correct, but my interpretation when reading is r= elated to data flow and not configuration. When I read the below I thought= this meant that if I have something like a split VPN that data to the corp= orate network should not leak to the public network and visa versa. >But, in the draft, it is said the opposite (i.e. "MIF must prevent the >leakage of confidential information from one interface to other >interfaces."). > -- will From denghui02@hotmail.com Wed Jul 29 01:04:43 2009 Return-Path: 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 347843A681A for ; Wed, 29 Jul 2009 01:04:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.615 X-Spam-Level: X-Spam-Status: No, score=0.615 tagged_above=-999 required=5 tests=[AWL=0.613, 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 p7UqT7jD19+U for ; Wed, 29 Jul 2009 01:04:42 -0700 (PDT) Received: from col0-omc2-s5.col0.hotmail.com (col0-omc2-s5.col0.hotmail.com [65.55.34.79]) by core3.amsl.com (Postfix) with ESMTP id 5AF493A6DA7 for ; Wed, 29 Jul 2009 01:04:42 -0700 (PDT) Received: from COL118-W35 ([65.55.34.71]) by col0-omc2-s5.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 01:04:43 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_36076cae-d873-4d39-9281-6c381255b4ed_" X-Originating-IP: [130.129.22.93] From: Hui Deng To: Date: Wed, 29 Jul 2009 16:04:44 +0800 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 29 Jul 2009 08:04:43.0991 (UTC) FILETIME=[3B65D670:01CA1023] Subject: [mif] MIF Slides updated X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 08:04:43 -0000 --_36076cae-d873-4d39-9281-6c381255b4ed_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 8bit Hello, all the slides has been updated, Please let us know if there is a mistake. thanks -Hui _________________________________________________________________ With Windows Live, you can organize, edit, and share your photos. http://www.microsoft.com/middleeast/windows/windowslive/products/photo-gallery-edit.aspx --_36076cae-d873-4d39-9281-6c381255b4ed_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: 8bit Hello, all
 
the slides has been updated,
Please let us know if there is a mistake.
 
thanks
 
-Hui

With Windows Live, you can organize, edit, and share your photos. --_36076cae-d873-4d39-9281-6c381255b4ed_-- From miika.komu@hiit.fi Thu Jul 30 02:21:07 2009 Return-Path: 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 271D528C2A2 for ; Thu, 30 Jul 2009 02:21:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.274 X-Spam-Level: X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, 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 ien44wgAcAsu for ; Thu, 30 Jul 2009 02:21:06 -0700 (PDT) Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 44D7428C290 for ; Thu, 30 Jul 2009 02:21:06 -0700 (PDT) Received: from ip104.infrahip.net (81-225-222-227-no16.business.telia.com [81.225.222.227]) by argo.otaverkko.fi (Postfix) with ESMTP id BBA6125ED1B for ; Thu, 30 Jul 2009 12:21:07 +0300 (EEST) Message-ID: <4A716603.5060207@hiit.fi> Date: Thu, 30 Jul 2009 12:21:07 +0300 From: Miika Komu User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: mif@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [mif] multihoming APIs X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: miika.komu@hiit.fi List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2009 09:21:07 -0000 Hi, do you think that the following document is somewhat relevat to MIF? http://tools.ietf.org/html/draft-ietf-shim6-multihome-shim-api Abstract: This document specifies sockets API extensions for the multihoming shim layer. The API aims to enable interactions between applications and the multihoming shim layer for advanced locator management, and access to information about failure detection and path exploration. This document is based on an assumption that a multihomed host is equipped with a conceptual sub-layer (hereafter "shim") inside the IP layer that maintains mappings between identifiers and locators. Examples of the shim are SHIM6 and HIP. From ietf@montavont.net Thu Jul 30 04:59:36 2009 Return-Path: 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 62D853A6908 for ; Thu, 30 Jul 2009 04:59:36 -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 aOMTOW-SbUt7 for ; Thu, 30 Jul 2009 04:59:35 -0700 (PDT) Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id BB5DA28C193 for ; Thu, 30 Jul 2009 04:58:43 -0700 (PDT) Received: by bwz19 with SMTP id 19so534210bwz.37 for ; Thu, 30 Jul 2009 04:58:42 -0700 (PDT) Received: by 10.204.62.136 with SMTP id x8mr1123808bkh.36.1248955122259; Thu, 30 Jul 2009 04:58:42 -0700 (PDT) Received: from dhcp-15bf.meeting.ietf.org (pat39-intra.rennes.enst-bretagne.fr [192.44.77.39]) by mx.google.com with ESMTPS id c28sm5592220fka.49.2009.07.30.04.58.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 30 Jul 2009 04:58:41 -0700 (PDT) Message-Id: From: Nicolas Montavont To: mif@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 30 Jul 2009 13:58:35 +0200 X-Mailer: Apple Mail (2.935.3) Cc: Marc.Blanchet@viagenie.ca Subject: [mif] definition of a MIF host X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2009 11:59:36 -0000 Hi, (I'm only starting to follow this group, so I hope my question was not discussed before...) I'd like to come back on the discussion on a MIF host as defined in draft-blanchet-mif-problem-statement-00. In the former WG Monami6, we worked on the following document: http://tools.ietf.org/id/draft-ietf-monami6-multihoming-motivation-scenario-03.txt where we also proposed a definition for a multihomed node. We came up with the following definitions: Interface A node's point of attachment to a link (as defined in [5]) Multihomed Node A node (either a host or a router) is multihomed when it has several global IPv6 addresses to choose between, i.e. in the following cases when it is either: * multi-prefixed: multiple prefixes are advertised on the link(s) the node is attached to, or. * multi-interfaced: the node has multiple interfaces to choose between, on the same link or not. Basically it says that a node is multi-homed as soon as it has multiple addresses of the same scope, from which it can choose to send data packets. What was good IMHO in this definition, is that it is concise and does not try to cover all cases where you can end up in that case. So for the purpose of draft-blanchet-mif-problem-statement-00, I would suggest to keep the definition very short, and then have examples in another section that show how a host can be multi-homed / MIF (several interfaces, several administrative domains, etc). In the same sense, I think that the bullet "Communications using these IP addresses may happen simultaneous and independently." should not be in the definition, but again, in some explanations of scenarios. Regards, Nicolas From marc.blanchet@viagenie.ca Thu Jul 30 08:30:53 2009 Return-Path: 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 6015F3A6C6B for ; Thu, 30 Jul 2009 08:30:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.934 X-Spam-Level: X-Spam-Status: No, score=-0.934 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HELO_DYNAMIC_DHCP=1.398, 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 TFIiGX5FfAct for ; Thu, 30 Jul 2009 08:30:52 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 68FE028C2C4 for ; Thu, 30 Jul 2009 08:30:50 -0700 (PDT) Received: by jazz.viagenie.ca (Postfix, from userid 8) id 14D7B29E15E4; Thu, 30 Jul 2009 11:30:49 -0400 (EDT) Received: from dhcp-13d0.meeting.ietf.org (dhcp-13d0.meeting.ietf.org [130.129.19.208]) by jazz.viagenie.ca (Postfix) with ESMTP id 13E7629E15B5; Thu, 30 Jul 2009 11:30:44 -0400 (EDT) Message-ID: <4A71BC9E.40709@viagenie.ca> Date: Thu, 30 Jul 2009 17:30:38 +0200 From: Marc Blanchet User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Nicolas Montavont References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: mif@ietf.org Subject: Re: [mif] definition of a MIF host X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2009 15:30:53 -0000 - thanks. it is in fact very good input. the monami6 definition is however a bit v6 specific (eg. prefixes advertised on the link) where mif shall be af agnostic. I'll adapt it for mif. Marc. Nicolas Montavont a écrit : > Hi, > > (I'm only starting to follow this group, so I hope my question was not > discussed before...) > > I'd like to come back on the discussion on a MIF host as defined in > draft-blanchet-mif-problem-statement-00. > > In the former WG Monami6, we worked on the following document: > > http://tools.ietf.org/id/draft-ietf-monami6-multihoming-motivation-scenario-03.txt > > > where we also proposed a definition for a multihomed node. We came up > with the following definitions: > > Interface > > A node's point of attachment to a link (as defined in [5]) > > Multihomed Node > > A node (either a host or a router) is multihomed when it has > several global IPv6 addresses to choose between, i.e. in the > following cases when it is either: > > * multi-prefixed: multiple prefixes are advertised on the link(s) > the node is attached to, or. > > * multi-interfaced: the node has multiple interfaces to choose > between, on the same link or not. > > Basically it says that a node is multi-homed as soon as it has multiple > addresses of the same scope, from which it can choose to send data > packets. What was good IMHO in this definition, is that it is concise > and does not try to cover all cases where you can end up in that case. > > So for the purpose of draft-blanchet-mif-problem-statement-00, I would > suggest to keep the definition very short, and then have examples in > another section that show how a host can be multi-homed / MIF (several > interfaces, several administrative domains, etc). > > In the same sense, I think that the bullet "Communications using these > IP addresses may happen simultaneous and independently." should not be > in the definition, but again, in some explanations of scenarios. > > Regards, > Nicolas > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif -- ========= IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca DTN news service: http://reeves.viagenie.ca From ietf@montavont.net Thu Jul 30 08:33:18 2009 Return-Path: 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 B696928C2D4 for ; Thu, 30 Jul 2009 08:33:18 -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 5vkUx4u0Gv-W for ; Thu, 30 Jul 2009 08:33:17 -0700 (PDT) Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 679C528C2D2 for ; Thu, 30 Jul 2009 08:33:17 -0700 (PDT) Received: by bwz19 with SMTP id 19so665777bwz.37 for ; Thu, 30 Jul 2009 08:33:18 -0700 (PDT) Received: by 10.204.51.210 with SMTP id e18mr1351655bkg.69.1248967998642; Thu, 30 Jul 2009 08:33:18 -0700 (PDT) Received: from dhcp-15bf.meeting.ietf.org (pat39-intra.rennes.enst-bretagne.fr [192.44.77.39]) by mx.google.com with ESMTPS id f31sm6147671fkf.8.2009.07.30.08.33.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 30 Jul 2009 08:33:18 -0700 (PDT) Message-Id: From: Nicolas Montavont To: Marc Blanchet In-Reply-To: <4A71BC9E.40709@viagenie.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 30 Jul 2009 17:33:15 +0200 References: <4A71BC9E.40709@viagenie.ca> X-Mailer: Apple Mail (2.935.3) Cc: mif@ietf.org Subject: Re: [mif] definition of a MIF host X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2009 15:33:18 -0000 On Jul 30, 2009, at 5:30 PM, Marc Blanchet wrote: > - thanks. it is in fact very good input. the monami6 definition is > however a bit v6 specific (eg. prefixes advertised on the link) Yeah, you're right, definitely - I forgot to mention it Nicolas > where > mif shall be af agnostic. I'll adapt it for mif. > > Marc. > > Nicolas Montavont a =E9crit : >> Hi, >> >> (I'm only starting to follow this group, so I hope my question was =20= >> not >> discussed before...) >> >> I'd like to come back on the discussion on a MIF host as defined in >> draft-blanchet-mif-problem-statement-00. >> >> In the former WG Monami6, we worked on the following document: >> >> = http://tools.ietf.org/id/draft-ietf-monami6-multihoming-motivation-scenari= o-03.txt >> >> >> where we also proposed a definition for a multihomed node. We came up >> with the following definitions: >> >> Interface >> >> A node's point of attachment to a link (as defined in [5]) >> >> Multihomed Node >> >> A node (either a host or a router) is multihomed when it has >> several global IPv6 addresses to choose between, i.e. in the >> following cases when it is either: >> >> * multi-prefixed: multiple prefixes are advertised on the =20 >> link(s) >> the node is attached to, or. >> >> * multi-interfaced: the node has multiple interfaces to choose >> between, on the same link or not. >> >> Basically it says that a node is multi-homed as soon as it has =20 >> multiple >> addresses of the same scope, from which it can choose to send data >> packets. What was good IMHO in this definition, is that it is concise >> and does not try to cover all cases where you can end up in that =20 >> case. >> >> So for the purpose of draft-blanchet-mif-problem-statement-00, I =20 >> would >> suggest to keep the definition very short, and then have examples in >> another section that show how a host can be multi-homed / MIF =20 >> (several >> interfaces, several administrative domains, etc). >> >> In the same sense, I think that the bullet "Communications using =20 >> these >> IP addresses may happen simultaneous and independently." should not =20= >> be >> in the definition, but again, in some explanations of scenarios. >> >> Regards, >> Nicolas >> _______________________________________________ >> mif mailing list >> mif@ietf.org >> https://www.ietf.org/mailman/listinfo/mif > > > --=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D > IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca > Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca > DTN news service: http://reeves.viagenie.ca >