
From pierrick.seite@orange-ftgroup.com  Thu Apr  1 01:27:44 2010
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 852A43A6A0E for <mif@core3.amsl.com>; Thu,  1 Apr 2010 01:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.128
X-Spam-Level: 
X-Spam-Status: No, score=-1.128 tagged_above=-999 required=5 tests=[AWL=0.991,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-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 taH-x4iyzFIC for <mif@core3.amsl.com>; Thu,  1 Apr 2010 01:27:43 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id AB5413A69E2 for <mif@ietf.org>; Thu,  1 Apr 2010 01:27:42 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id E132E798009; Thu,  1 Apr 2010 10:28:14 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 90736760007; Thu,  1 Apr 2010 10:28:14 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 1 Apr 2010 10:27:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Apr 2010 10:27:57 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C462C38CD9@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mif] WG LC for MIF PS
Thread-Index: AcrPKipF5D2y1JLKTqe/PkdfkVt0RgBqpQcgAARsmBAAI6mycA==
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl><c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com><4BA8E714.80803@viagenie.ca><p2uc549bac51003290324yb5663e33ncf2a34be18272279@mail.gmail.com> <843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0.rd.francetelecom.fr> <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>
From: <pierrick.seite@orange-ftgroup.com>
To: <julienl@qualcomm.com>, <zehn.cao@gmail.com>, <marc.blanchet@viagenie.ca>
X-OriginalArrivalTime: 01 Apr 2010 08:27:58.0675 (UTC) FILETIME=[3C503A30:01CAD175]
Cc: mif@ietf.org
Subject: Re: [mif] WG LC for MIF PS
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, 01 Apr 2010 08:27:44 -0000

> -----Message d'origine-----
> De=A0: Laganier, Julien [mailto:julienl@qualcomm.com]
> Envoy=E9=A0: mercredi 31 mars 2010 17:27
> =C0=A0: SEITE Pierrick RD-RESA-REN; zehn.cao@gmail.com;
> marc.blanchet@viagenie.ca
> Cc=A0: mif@ietf.org
> Objet=A0: RE: [mif] WG LC for MIF PS
>=20
> Hello,
>=20
> pierrick.seite@orange-ftgroup.com wrote:
> >
> > Hi Zhen,
> >
> > >
> > > >> 3.4 Address selection
> > > >> It is good to mention that some OS like OSX does not implement
> > > >> 3484-like policy table.
> > > > This belongs to the current-practices doc.
> > > >> Default behavior of the 3484 policy table is
> > > >> to prefer IPv6 over IPv4, but this behavior in some situations =
are
> > not
> > > >> optimal and need to be changed.
> > > >
> > > > How much this comment related to MIF? Can you describe a =
specific
> > > scenario?
> > >
> > > If the host has two interfaces, one connects to the IPv6-only and =
one
> > > connection to IPv4, and a dual stack application may be restricted =
by
> > > the address selection policy.
> >
> > Ok, the PS text can be updated to state that default selection, as =
per
> > RFC3484, is not always optimal.
>=20
> RFC 3484 address selection not being optimal seems like an orthogonal
> problem to a host being attached to multiple network domains since the
> issue can also occurs when a host is attached to a single domain. So I
> don't think we should list this in the PS.
>=20

It makes sense to focus on issues specific to MIF.

Thanks,
Pierrick

> --julien

From zehn.cao@gmail.com  Mon Apr  5 05:42:13 2010
Return-Path: <zehn.cao@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 B926F3A697A for <mif@core3.amsl.com>; Mon,  5 Apr 2010 05:42: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 M6oA-T8Qtakm for <mif@core3.amsl.com>; Mon,  5 Apr 2010 05:42:13 -0700 (PDT)
Received: from mail-yx0-f202.google.com (mail-yx0-f202.google.com [209.85.210.202]) by core3.amsl.com (Postfix) with ESMTP id EFC5E3A6978 for <mif@ietf.org>; Mon,  5 Apr 2010 05:42:12 -0700 (PDT)
Received: by yxe40 with SMTP id 40so613936yxe.31 for <mif@ietf.org>; Mon, 05 Apr 2010 05:42:08 -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:received:message-id:subject:from:to:cc:content-type; bh=7aSioABRJNdzE7PHTXo4/Eh4lnikEwf60EoVWRKtUcE=; b=AvK+kIuLNKRPzQqlLQ3cWJGtkB2l6e6KsiTXIYOq1NKtUZl67dGDS4BY0Bt6zar7hY ngGjABw1bkSQUbVYI9+5GHjX3fhaFSgiJj4cYWs/ku2rvjGInW+/K8huT5bh0nIgh3LQ MF/kLAiIYVgV5mFAP4AIxazXVjAZB19Ra2Epo=
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=IFWgURljUuei6dRDLTCPeDnZUt7u48s2o1lVBTNCUpb+CkFyhNSk40G8fchwqM/TFN rJnpp+IKhygIuePsHUSJkPOvKzuzdxakqIZpVpbQBorGKmohF1kWEBqXGMAxQWxrfYGF /YOnDAitbxKl3jzTJ5Xsix4MYmXaoFUgdIZtY=
MIME-Version: 1.0
Received: by 10.100.12.11 with HTTP; Mon, 5 Apr 2010 05:42:01 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl> <c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com> <4BA8E714.80803@viagenie.ca> <p2uc549bac51003290324yb5663e33ncf2a34be18272279@mail.gmail.com> <843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0.rd.francetelecom.fr> <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>
Date: Mon, 5 Apr 2010 20:42:01 +0800
Received: by 10.101.176.18 with SMTP id d18mr12786048anp.242.1270471321493;  Mon, 05 Apr 2010 05:42:01 -0700 (PDT)
Message-ID: <m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] WG LC for MIF PS
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 Apr 2010 12:42:13 -0000

On Wed, Mar 31, 2010 at 11:27 PM, Laganier, Julien <julienl@qualcomm.com> wrote:
>
> RFC 3484 address selection not being optimal seems like an orthogonal problem to a host being attached to multiple network domains since the issue can also occurs when a host is attached to a single domain. So I don't think we should list this in the PS.
>

If one interface is IPv6 and another interface is IPv4, which one to
choose is directly related to the mif. That's not covered by RFC3484.
And i am thinking of if the "domain selection" can cover this problem.

-Zhen

From julienl@qualcomm.com  Mon Apr  5 08:07:21 2010
Return-Path: <julienl@qualcomm.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 57CC028C147 for <mif@core3.amsl.com>; Mon,  5 Apr 2010 08:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 QJGihAQQZL8g for <mif@core3.amsl.com>; Mon,  5 Apr 2010 08:07:19 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 9912328C145 for <mif@ietf.org>; Mon,  5 Apr 2010 08:07:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1270480037; x=1302016037; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Zhen=20Cao=20<zehn.cao@gmail.com>|CC:=20"pierrick. seite@orange-ftgroup.com"=20<pierrick.seite@orange-ftgrou p.com>,=0D=0A=09"marc.blanchet@viagenie.ca"=20<marc.blanc het@viagenie.ca>,=20"mif@ietf.org"=0D=0A=09<mif@ietf.org> |Date:=20Mon,=205=20Apr=202010=2008:07:13=20-0700 |Subject:=20RE:=20[mif]=20WG=20LC=20for=20MIF=20PS |Thread-Topic:=20[mif]=20WG=20LC=20for=20MIF=20PS |Thread-Index:=20AcrUvWjb0j1b4gJiT+KHtNRmJzPTrAAE4Xmw |Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C6AA56F9 3@NALASEXMB04.na.qualcomm.com>|References:=20<COL118-W43D 1A92D6FAECE336508C6B1310@phx.gbl>=0D=0A=09=20<c549bac5100 3192246t62c91c1cw925afa82aae62d30@mail.gmail.com>=0D=0A =09=20<4BA8E714.80803@viagenie.ca>=0D=0A=09=20<p2uc549bac 51003290324yb5663e33ncf2a34be18272279@mail.gmail.com>=0D =0A=09=20<843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0 .rd.francetelecom.fr>=0D=0A=09=20<BF345F63074F8040B58C00A 186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>=0D=0A=20 <m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@mail.gma il.com>|In-Reply-To:=20<m2qc549bac51004050542t3028ac28j7d 0c1b28d037ff1b@mail.gmail.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=uYvI5OiVQNQDVdVOS40eHeR384RdQu3IINtb8bzHCcE=; b=LyZJgIvwYYOi3WOMG4eRiatKJLNxpv96MDoRMD1bIRS/9k4WsBmY6qsU j9mLf+WlqQtVKpUOwDWkR/zIMy7wAHQ8iFEuk2fQrGLquxdEqrgpCHCxv GK46EF+gFoCXhqOZ6Z1BIPvTsEudcLPzZZlSaOCOkHoG4sxvK58oy3u2f Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,5942"; a="38016021"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine01.qualcomm.com with ESMTP; 05 Apr 2010 08:07:17 -0700
X-IronPort-AV: E=Sophos;i="4.51,365,1267430400";  d="scan'208";a="8195590"
Received: from nasanexhub04.qualcomm.com (HELO nasanexhub04.na.qualcomm.com) ([129.46.134.222]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 05 Apr 2010 08:07:16 -0700
Received: from nalasexhub02.na.qualcomm.com (10.47.130.89) by nasanexhub04.na.qualcomm.com (129.46.134.222) with Microsoft SMTP Server (TLS) id 8.2.234.1; Mon, 5 Apr 2010 08:07:15 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhub02.na.qualcomm.com ([10.47.130.89]) with mapi; Mon, 5 Apr 2010 08:07:15 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Zhen Cao <zehn.cao@gmail.com>
Date: Mon, 5 Apr 2010 08:07:13 -0700
Thread-Topic: [mif] WG LC for MIF PS
Thread-Index: AcrUvWjb0j1b4gJiT+KHtNRmJzPTrAAE4Xmw
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AA56F93@NALASEXMB04.na.qualcomm.com>
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl> <c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com> <4BA8E714.80803@viagenie.ca> <p2uc549bac51003290324yb5663e33ncf2a34be18272279@mail.gmail.com> <843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0.rd.francetelecom.fr> <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com> <m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@mail.gmail.com>
In-Reply-To: <m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@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
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] WG LC for MIF PS
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 Apr 2010 15:07:21 -0000

Zhen Cao wrote:
>=20
> On Wed, Mar 31, 2010 at 11:27 PM, Laganier, Julien
> <julienl@qualcomm.com> wrote:
> >
> > RFC 3484 address selection not being optimal seems like an orthogonal
> > problem to a host being attached to multiple network domains since the
> > issue can also occurs when a host is attached to a single domain. So I
> > don't think we should list this in the PS.
>=20
> If one interface is IPv6 and another interface is IPv4, which one to
> choose is directly related to the mif. That's not covered by RFC3484.
> And i am thinking of if the "domain selection" can cover this problem.

The generic problem of how to best choose between IPv4 and IPv6 to reach a =
given destination exists already with a single interface and a single admin=
istrative domain and is thus not specific to MIF. A solution to this proble=
m would work in MIF too and thus I do not think we should list this in the =
problem statement.

--julien

From scott.brim@gmail.com  Mon Apr  5 08:26:10 2010
Return-Path: <scott.brim@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 D144928C164 for <mif@core3.amsl.com>; Mon,  5 Apr 2010 08:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207,  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 Y4ThmUDTPZOF for <mif@core3.amsl.com>; Mon,  5 Apr 2010 08:26:09 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id AF53428C15F for <mif@ietf.org>; Mon,  5 Apr 2010 08:26:09 -0700 (PDT)
Received: by vws15 with SMTP id 15so1055vws.31 for <mif@ietf.org>; Mon, 05 Apr 2010 08:26:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=Ljeqxd8gLvqULbR8/FHFWVDVQ4HTAJfZrTgHYyia97M=; b=aWu4fTE8jXruDPYs8Vv7Gs33DPB6LUsK5H3ergcoscSZBvS/KljQDKrEjg2wjc42tS OKJ7F7Kvo5dpQ9IctI0n2iDZuzZI2AWO58k4h7xXX/PaWTDV7L/ksElETjaG2bd1p7tJ 93gI14pjIOlweWJjQ5ZiE8jMChEMIJNM7m+to=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=gTvukdS0ukLQqXy/CvSlxiGrd+HkQs3wI9j9eek9VMRyACVDWFdRGkixFC2ZucFbFm 6ZfOfJrYrMFy0SYyHUjZk4jAUULAdjejYNk4bgG/fnC+NKbToxrQF9SRpJolSb1sEIyM d36W7/4vaD/Dw7uEr4wqLromSDNC0eljCtEvU=
Received: by 10.220.3.230 with SMTP id 38mr2588707vco.172.1270481164898; Mon, 05 Apr 2010 08:26:04 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 33sm27948293vws.10.2010.04.05.08.26.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 05 Apr 2010 08:26:04 -0700 (PDT)
Message-ID: <4BBA0109.2030402@gmail.com>
Date: Mon, 05 Apr 2010 11:26:01 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Laganier, Julien" <julienl@qualcomm.com>
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl>	<c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com>	<4BA8E714.80803@viagenie.ca>	<p2uc549bac51003290324yb5663e33ncf2a34be18272279@mail.gmail.com>	<843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0.rd.francetelecom.fr>	<BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com>	<m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AA56F93@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56F93@NALASEXMB04.na.qualcomm.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] WG LC for MIF PS
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 Apr 2010 15:26:10 -0000

Laganier, Julien allegedly wrote on 04/05/2010 11:07 EDT:
> Zhen Cao wrote:
>> 
>> On Wed, Mar 31, 2010 at 11:27 PM, Laganier, Julien 
>> <julienl@qualcomm.com> wrote:
>>> 
>>> RFC 3484 address selection not being optimal seems like an
>>> orthogonal problem to a host being attached to multiple network
>>> domains since the issue can also occurs when a host is attached
>>> to a single domain. So I don't think we should list this in the
>>> PS.
>> 
>> If one interface is IPv6 and another interface is IPv4, which one
>> to choose is directly related to the mif. That's not covered by
>> RFC3484. And i am thinking of if the "domain selection" can cover
>> this problem.
> 
> The generic problem of how to best choose between IPv4 and IPv6 to
> reach a given destination exists already with a single interface and
> a single administrative domain and is thus not specific to MIF. A
> solution to this problem would work in MIF too and thus I do not
> think we should list this in the problem statement.
> 
> --julien

IMHO: The MIF scope is that once you get your answers back from those
other mechanisms for determining what works (v6 vs v4 .. and TCP vs SCTP
and so on), those answers may be spread across multiple interfaces, and
you have to use the right one in the right way.

Scott

From denghui02@gmail.com  Mon Apr  5 19:39:58 2010
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 BCB653A6819 for <mif@core3.amsl.com>; Mon,  5 Apr 2010 19:39:58 -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 ilQhJsNXwtZO for <mif@core3.amsl.com>; Mon,  5 Apr 2010 19:39:57 -0700 (PDT)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id 0C4DD3A67EC for <mif@ietf.org>; Mon,  5 Apr 2010 19:39:55 -0700 (PDT)
Received: by gxk9 with SMTP id 9so3370353gxk.8 for <mif@ietf.org>; Mon, 05 Apr 2010 19:39:51 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JHm0aUcRZxuPK56Ot5Ti9FD+93ejrVWYYBVGCSBc/VE=; b=AonaAgQQ2kmThWODOYBe8ebuunZthjprYhXKXI64dTgDHofpB2pFl/zOOow2qOW1ZX oBMW5UT7e4vSQPOrYRgorWcjfgo7vW81rcJyMuYZFlCLlguIl4my7pG+3e9VixPEz/oe Xd9oTfqUykWvTHRv7l2KYBrcNEZq/lh79hwF0=
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=cA+tNEcoStM0EAvt3CEYMpi4u1Yqi7WWEurlhBh6pgw/AuVZgbq5sFYxNePHIPdYT7 Ei7Po29DD5+C1uXuPMjQRhH3LR4FKuV8X/hCIol4GUN3ERB+qHK9QX1vOrdKsRkHcOp+ Wby4ylOBy+LxmE/iCPDVqeCdeEOSsz6jCAAv4=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Mon, 5 Apr 2010 19:39:51 -0700 (PDT)
In-Reply-To: <044f01cad05d$22cdd090$c6f0200a@cisco.com>
References: <AcrQXSIWX7VrtDK7SBKyEB9Yj26v2Q==> <044f01cad05d$22cdd090$c6f0200a@cisco.com>
Date: Tue, 6 Apr 2010 10:39:51 +0800
Received: by 10.101.211.15 with SMTP id n15mr15763644anq.64.1270521591095;  Mon, 05 Apr 2010 19:39:51 -0700 (PDT)
Message-ID: <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Dan Wing <dwing@cisco.com>, Gabriel Montenegro <gmonte@microsoft.com>,  Dave Thaler <dthaler@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 02:39:58 -0000

DNS server always has specific interface related information,
but the final DNS server will still be host based, I wouldn't say it
is not correct.

one example would be you have internet connection and vpn connection
at the same time,
good VPN implementation will always rely on VPN DNS server information
for Internet connection.

-Hui

2010/3/31 Dan Wing <dwing@cisco.com>:
> Section 3.2.1.3 of describes the DNS configuration of Windows, and says:
>
> =A0"Interface specific DNS configuration can be input via static
> =A0 configuration or via DHCP. =A0It includes:
>
> =A0 o =A0An interface-specific suffix list.
>
> =A0 o =A0A list of DNS server IP addresses."
>
> It is curious that the first bullet repeats "interface specific", but the
> second bullet does not repeat it. =A0A reasonable interpretation is that =
the
> second bullet is not interface-specific, but the lead-in sentence says th=
is is
> interface-specific. =A0I was hoping draft-montenegro-mif-multihoming-00 w=
ould
> clarify, but it doesn't.
>
> -d
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From zehn.cao@gmail.com  Mon Apr  5 19:52:25 2010
Return-Path: <zehn.cao@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 4E4EB3A6819 for <mif@core3.amsl.com>; Mon,  5 Apr 2010 19:52:25 -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 fZ5fh-xNZ-l4 for <mif@core3.amsl.com>; Mon,  5 Apr 2010 19:52:24 -0700 (PDT)
Received: from mail-yx0-f190.google.com (mail-yx0-f190.google.com [209.85.210.190]) by core3.amsl.com (Postfix) with ESMTP id 3B8893A67EC for <mif@ietf.org>; Mon,  5 Apr 2010 19:52:24 -0700 (PDT)
Received: by yxe28 with SMTP id 28so2001604yxe.6 for <mif@ietf.org>; Mon, 05 Apr 2010 19:52:19 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=plP0ccie3hdFgLCpVs93iiIDPLfZ98ZjORTpzbZJQMw=; b=mGmtb0IdR7LjDu7ScI7lcHo14+zBf8Kot4W+26Y/LSBwaU3EpwIkPgKn6TFBg4ob3v U+keODB9EuLLYG2V3b+4QC6ZxWIiQ/7gRlBIsV7gYszqq0tSzJ+wceRriem3Q/7iT1cP pG3V8q9xgQ/SQygV4cPonMCe8QNqFVFI58sF8=
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=P0ieluNCUeaCffpAjdkBYxQ77XLO9uswrqg2w3s6LIR/ZMrcSCLKNkrRlMG7lvAgxm 5oV0uIuFSjQI+3nV+k3dogoJAJWvdplmyWPZsGs6JtJ654CDb/d+1cr3Suy4dvrRmOi/ VJMYpo7Dyn9SQvO9JNtAhflb5zIL8gaxY08Ow=
MIME-Version: 1.0
Received: by 10.100.12.11 with HTTP; Mon, 5 Apr 2010 19:52:19 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56F93@NALASEXMB04.na.qualcomm.com>
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl> <c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com> <4BA8E714.80803@viagenie.ca> <p2uc549bac51003290324yb5663e33ncf2a34be18272279@mail.gmail.com> <843DA8228A1BA74CA31FB4E111A5C462C38B3A@ftrdmel0.rd.francetelecom.fr> <BF345F63074F8040B58C00A186FCA57F1C6AA56CD0@NALASEXMB04.na.qualcomm.com> <m2qc549bac51004050542t3028ac28j7d0c1b28d037ff1b@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AA56F93@NALASEXMB04.na.qualcomm.com>
Date: Tue, 6 Apr 2010 10:52:19 +0800
Received: by 10.101.191.32 with SMTP id t32mr15385536anp.87.1270522339226;  Mon, 05 Apr 2010 19:52:19 -0700 (PDT)
Message-ID: <j2mc549bac51004051952o20fe7d04h8d04427666953cc9@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] WG LC for MIF PS
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, 06 Apr 2010 02:52:25 -0000

On Mon, Apr 5, 2010 at 11:07 PM, Laganier, Julien <julienl@qualcomm.com> wr=
ote:
> Zhen Cao wrote:
>>
>> On Wed, Mar 31, 2010 at 11:27 PM, Laganier, Julien
>> <julienl@qualcomm.com> wrote:
>> >
>> > RFC 3484 address selection not being optimal seems like an orthogonal
>> > problem to a host being attached to multiple network domains since the
>> > issue can also occurs when a host is attached to a single domain. So I
>> > don't think we should list this in the PS.
>>
>> If one interface is IPv6 and another interface is IPv4, which one to
>> choose is directly related to the mif. That's not covered by RFC3484.
>> And i am thinking of if the "domain selection" can cover this problem.
>
> The generic problem of how to best choose between IPv4 and IPv6 to reach =
a given destination exists already with a single interface and a single adm=
inistrative domain and is thus not specific to MIF. A solution to this prob=
lem would work in MIF too and thus I do not think we should list this in th=
e problem statement.

Yes, I agree this problem flows into the address selection bullet.
Considering Scott's comments, we will have to take care of the result
delivered from the solution to a single domain when applied to
multiple domains. Thanks for the discussion.

From g_e_montenegro@yahoo.com  Tue Apr  6 09:13:46 2010
Return-Path: <g_e_montenegro@yahoo.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 6FB3B3A68B6 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 09:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 aON7Keeqn1Ah for <mif@core3.amsl.com>; Tue,  6 Apr 2010 09:13:45 -0700 (PDT)
Received: from web82608.mail.mud.yahoo.com (web82608.mail.mud.yahoo.com [68.142.201.125]) by core3.amsl.com (Postfix) with SMTP id C56BB3A67AE for <mif@ietf.org>; Tue,  6 Apr 2010 09:13:25 -0700 (PDT)
Received: (qmail 96920 invoked by uid 60001); 6 Apr 2010 16:13:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1270570402; bh=pwiFQuHPMNR4aFlR3WjAKR72hL70avPEAewXTS/SLpM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DKhZZ0fCKUMRIANm57CX3IFiKdhE+qUIiiqWYO0owkaeGtim5cL8bWtPSkygD5/3rHd5YIrMG0LdQKIWy720CpoaO4VZ/3BVnPIZjVGwc4Qj6d/W4gFV73CayGJ5QPaxXmonsntISnjQLpCm80O/mAvO9E4LBXJdWHNGYx2fLmM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=enDnbeLOZdjCvIb7uasnOr3nl7gm6BYK5s103DcQZvwSM9qN1PSHHpDEo5PMOVSDuV+CorjXgQhwzT+a5hE9oXG/pyZTyG6smXNxmXhxsaYZtrywKZjBCVPWN5NmBd1Xw4dZGo+/tNJrA6/Xza+O/i5a4NIzAs7WAU2b13IBy4Y=;
Message-ID: <211213.96301.qm@web82608.mail.mud.yahoo.com>
X-YMail-OSG: EoMRUDkVM1nbUd2.UlZ6RAMBfJuFdeqdxc3Z13iRzExGi.C vKhc9Ztx2mnkledgfLeyotMfvxx0HFb2gGLC.A8.OAYUNSYF0Dmdj8BRfRE7 fXShx2cxTjz7uxougFKIK0HTeORAJ3pR0Y1FsN6Dl4iQ2yZK6I.18KiHtt_w rkwHqZysdg9zPZrSg_nGAgSJUd3InTYxC3URUGE7OnLIeEceDDHQSOnSL1zZ FX0PSyUzYcNsUI8tgJcpUeIWzIRt2Pr1KXDAKl5jKzasPMzdHFoMuHKl3VQe dxqN3K5hPB_DST8Ww9S2sqFziAa.KA7MhnYD0JduO.k2lv6j0sX89b7wa0P4 DvLLyBVf15MU-
Received: from [98.237.196.120] by web82608.mail.mud.yahoo.com via HTTP; Tue, 06 Apr 2010 09:13:22 PDT
X-Mailer: YahooMailRC/324.3 YahooMailWebService/0.8.100.260964
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com>
Date: Tue, 6 Apr 2010 09:13:22 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Dan Wing <dwing@cisco.com>, mif@ietf.org
In-Reply-To: <044f01cad05d$22cdd090$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 16:13:46 -0000

Re: draft-montenegro-mif-multihoming:=0A=0AI would have thought that it is =
clear, given that this info is found in section 4.2 which is called "interf=
ace-specific DNS configuration". It is not found in the previous section 4.=
1 which=A0is called "host-wide DNS configuration".=0A=0A=0A=0A----- Origina=
l Message ----=0A> From: Dan Wing <dwing@cisco.com>=0A> To: mif@ietf.org=0A=
> Sent: Tue, March 30, 2010 4:02:55 PM=0A> Subject: [mif] draft-ietf-mif-cu=
rrent-practices-00=0A> =0A> Section 3.2.1.3 of describes the DNS configurat=
ion of Windows, and =0A> says:=0A=0A=A0 "Interface specific DNS configurati=
on can be input via =0A> static=0A=A0 configuration or via DHCP.=A0 It incl=
udes:=0A=0A=A0 =0A> o=A0 An interface-specific suffix list.=0A=0A=A0 o=A0 A=
 list of DNS =0A> server IP addresses."=0A=0AIt is curious that the first b=
ullet repeats =0A> "interface specific", but the=0Asecond bullet does not r=
epeat it.=A0 A =0A> reasonable interpretation is that the=0Asecond bullet i=
s not =0A> interface-specific, but the lead-in sentence says this =0A> is=
=0Ainterface-specific.=A0 I was hoping draft-montenegro-mif-multihoming-00 =
=0A> would=0Aclarify, but it =0A> doesn't.=0A=0A-d=0A=0A___________________=
____________________________=0Amif =0A> mailing list=0A> href=3D"mailto:mif=
@ietf.org">mif@ietf.org=0A> href=3D"https://www.ietf.org/mailman/listinfo/m=
if" target=3D_blank =0A> >https://www.ietf.org/mailman/listinfo/mif

From dwing@cisco.com  Tue Apr  6 11:44:20 2010
Return-Path: <dwing@cisco.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 1AF273A69C2 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 11:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.392
X-Spam-Level: 
X-Spam-Status: No, score=-9.392 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 jssHqOLahzf2 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 11:44:19 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 061BC3A69D4 for <mif@ietf.org>; Tue,  6 Apr 2010 11:42:50 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwIAAseu0urRN+J/2dsb2JhbACHWIEUhjeMF3GiE5kEhQkEgyQ
X-IronPort-AV: E=Sophos;i="4.51,374,1267401600"; d="scan'208";a="178857898"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 06 Apr 2010 18:42:42 +0000
Received: from dwingwxp01 (sjc-vpn4-120.cisco.com [10.21.80.120]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o36IgUYP028424; Tue, 6 Apr 2010 18:42:35 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'gabriel montenegro'" <g_e_montenegro@yahoo.com>, <mif@ietf.org>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <211213.96301.qm@web82608.mail.mud.yahoo.com>
Date: Tue, 6 Apr 2010 11:42:26 -0700
Message-ID: <07dd01cad5b8$eec4e3e0$7893150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcrVpBi+x71HZDcaQVyfE9TGWJIFxwAFF5KQ
In-Reply-To: <211213.96301.qm@web82608.mail.mud.yahoo.com>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 18:44:20 -0000

=20

> -----Original Message-----
> From: gabriel montenegro [mailto:g_e_montenegro@yahoo.com]=20
> Sent: Tuesday, April 06, 2010 9:13 AM
> To: Dan Wing; mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>=20
> Re: draft-montenegro-mif-multihoming:
>=20
> I would have thought that it is clear, given that this info=20
> is found in section 4.2 which is called "interface-specific=20
> DNS configuration".

I agree it is in an appropriately-named section -- I said
that in my original post to MIF.

My specific suggestion is to simply change from

OLD:
   Interface-specific DNS configuration is input either via static
   configuration or via DHCP.

   .  Interface-specific suffix list

   .  List of DNS server IP addresses - The first one is the "primary"
     with all others being secondary.
NEW:
   Interface-specific DNS configuration is input either via static
   configuration or via DHCP.

   .  suffix list
.....^

   .  List of DNS server IP addresses - The first one is the "primary"
     with all others being secondary.


-d

> It is not found in the previous section=20
> 4.1 which=A0is called "host-wide DNS configuration".
>=20
>=20
>=20
> ----- Original Message ----
> > From: Dan Wing <dwing@cisco.com>
> > To: mif@ietf.org
> > Sent: Tue, March 30, 2010 4:02:55 PM
> > Subject: [mif] draft-ietf-mif-current-practices-00
> >=20
> > Section 3.2.1.3 of describes the DNS configuration of Windows, and=20
> > says:
>=20
> =A0 "Interface specific DNS configuration can be input via=20
> > static
> =A0 configuration or via DHCP.=A0 It includes:
>=20
> =A0=20
> > o=A0 An interface-specific suffix list.
>=20
> =A0 o=A0 A list of DNS=20
> > server IP addresses."
>=20
> It is curious that the first bullet repeats=20
> > "interface specific", but the
> second bullet does not repeat it.=A0 A=20
> > reasonable interpretation is that the
> second bullet is not=20
> > interface-specific, but the lead-in sentence says this=20
> > is
> interface-specific.=A0 I was hoping =
draft-montenegro-mif-multihoming-00=20
> > would
> clarify, but it=20
> > doesn't.
>=20
> -d
>=20
> _______________________________________________
> mif=20
> > mailing list
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank=20
> > >https://www.ietf.org/mailman/listinfo/mif


From dwing@cisco.com  Tue Apr  6 11:53:12 2010
Return-Path: <dwing@cisco.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 E22313A69E8 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 11:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.995
X-Spam-Level: 
X-Spam-Status: No, score=-9.995 tagged_above=-999 required=5 tests=[AWL=0.604,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 sG+6HmBKe8U2 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 11:53:11 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id AC50A3A69F4 for <mif@ietf.org>; Tue,  6 Apr 2010 11:52:32 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoIAPseu0urRN+J/2dsb2JhbACHWIEUkk5xoiKZBoUJBIMk
X-IronPort-AV: E=Sophos;i="4.51,374,1267401600"; d="scan'208";a="178860894"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 06 Apr 2010 18:52:30 +0000
Received: from dwingwxp01 (sjc-vpn4-120.cisco.com [10.21.80.120]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o36IqEbp003576; Tue, 6 Apr 2010 18:52:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dave Thaler'" <dthaler@microsoft.com>, "'Hui Deng'" <denghui02@gmail.com>, "'Gabriel Montenegro'" <gmonte@microsoft.com>
References: <AcrQXSIWX7VrtDK7SBKyEB9Yj26v2Q==> <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 6 Apr 2010 11:52:11 -0700
Message-ID: <07e201cad5ba$4d53eea0$7893150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AQHK1TKMaTaZ5uEk9UKBxenwZvGT9pIVqnJAgAAdoSA=
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 18:53:13 -0000

=20

> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@microsoft.com]=20
> Sent: Tuesday, April 06, 2010 10:06 AM
> To: Hui Deng; Dan Wing; Gabriel Montenegro
> Cc: mif@ietf.org
> Subject: RE: [mif] draft-ietf-mif-current-practices-00
>=20
> Hui is correct, Windows has per-interface DNS server lists configured.
>=20
> It then uses a host-wide "effective" server list for an actual query,
> where the effective server list may be different for different names.
>=20
> On Windows the per-interface suffix is actually termed the
> "connection-specific DNS suffix" to distinguish it from the
> "primary DNS suffix" of the machine.  I think that's why
> "interface-specific" was repeated in the first bullet.



In draft-montenegro-mif-multihoming, there are two purposes and terms =
that=20
seem to be intermingled using the term "DNS suffix". =20

One purpose is the suffix for non-FQDN names, like "payroll" or "mail",=20
which will have a suffix added to them (e.g., example.com).  The=20
other purpose is deciding which DNS server will be be sent a query for=20
a certain FQDN (e.g., queries for *.example.net go to one DNS server=20
and queries for *.example.com go to a different DNS server).


In draft-ietf-mif-current-practices-00, which is the WG document
that seems to have boiled down draft-montenegro-mif-multihoming,
but draft-ietf-mif-current-practices-00 also does not clearly
separate the two purposes.

-d


> Example on Windows, extracted from "ipconfig /all" output:
>=20
> Windows IP Configuration
>=20
>    Host Name . . . . . . . . . . . . : dthaler-win7
>    Primary Dns Suffix  . . . . . . . : ntdev.corp.microsoft.com
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    Node Type . . . . . . . . . . . . : Hybrid
>    IP Routing Enabled. . . . . . . . : No
>    WINS Proxy Enabled. . . . . . . . : No
>    DNS Suffix Search List. . . . . . : ntdev.corp.microsoft.com
>                                        redmond.corp.microsoft.com
>                                        ntdev.microsoft.com
>                                        dns.corp.microsoft.com
>    System Quarantine State . . . . . : Not Restricted
>=20
> Wireless LAN adapter Wireless Network Connection:
>=20
>    Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    Description . . . . . . . . . . . : Intel(R) Wireless WiFi=20
> Link 4965AGN
>    Physical Address. . . . . . . . . : 00-1D-E0-34-4F-6F
>    DHCP Enabled. . . . . . . . . . . : Yes
>    Autoconfiguration Enabled . . . . : Yes
>    Link-local IPv6 Address . . . . . :=20
> fe80::4853:4753:9d8d:3b45%13(Preferred)
>    IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
>    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>    Lease Obtained. . . . . . . . . . : Monday, April 05, 2010=20
> 10:19:02 PM
>    Lease Expires . . . . . . . . . . : Tuesday, April 06,=20
> 2010 10:19:02 PM
>    Default Gateway . . . . . . . . . : 192.168.0.1
>    DHCP Server . . . . . . . . . . . : 192.168.0.1
>    DHCPv6 IAID . . . . . . . . . . . : 335551968
>    DHCPv6 Client DUID. . . . . . . . :=20
> 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
>=20
>    DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
>                                        192.168.0.1
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    NetBIOS over Tcpip. . . . . . . . : Enabled
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: Hui Deng [mailto:denghui02@gmail.com]
> > Sent: Monday, April 05, 2010 7:40 PM
> > To: Dan Wing; Gabriel Montenegro; Dave Thaler
> > Cc: mif@ietf.org
> > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> >=20
> > DNS server always has specific interface related information,
> > but the final DNS server will still be host based, I wouldn't say it
> > is not correct.
> >=20
> > one example would be you have internet connection and vpn connection
> > at the same time,
> > good VPN implementation will always rely on VPN DNS server=20
> information
> > for Internet connection.
> >=20
> > -Hui
> >=20
> > 2010/3/31 Dan Wing <dwing@cisco.com>:
> > > Section 3.2.1.3 of describes the DNS configuration of Windows, and
> > says:
> > >
> > > =A0"Interface specific DNS configuration can be input via static
> > > =A0 configuration or via DHCP. =A0It includes:
> > >
> > > =A0 o =A0An interface-specific suffix list.
> > >
> > > =A0 o =A0A list of DNS server IP addresses."
> > >
> > > It is curious that the first bullet repeats "interface=20
> specific", but
> > the
> > > second bullet does not repeat it. =A0A reasonable interpretation =
is
> > that the
> > > second bullet is not interface-specific, but the lead-in sentence
> > says this is
> > > interface-specific. =A0I was hoping=20
> draft-montenegro-mif-multihoming-00
> > would
> > > clarify, but it doesn't.
> > >
> > > -d
> > >
> > > _______________________________________________
> > > mif mailing list
> > > mif@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mif
> > >
>=20


From dthaler@microsoft.com  Tue Apr  6 10:06:23 2010
Return-Path: <dthaler@microsoft.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 114653A68C6 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 10:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 IEw72N2L-m3I for <mif@core3.amsl.com>; Tue,  6 Apr 2010 10:06:22 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id EEEBC3A6767 for <mif@ietf.org>; Tue,  6 Apr 2010 10:06:21 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 6 Apr 2010 10:06:19 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.21; Tue, 6 Apr 2010 10:06:18 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.63]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 6 Apr 2010 10:06:18 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Hui Deng <denghui02@gmail.com>, Dan Wing <dwing@cisco.com>, "Gabriel Montenegro" <gmonte@microsoft.com>
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AQHK1TKMaTaZ5uEk9UKBxenwZvGT9pIVqnJA
Date: Tue, 6 Apr 2010 17:05:58 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <AcrQXSIWX7VrtDK7SBKyEB9Yj26v2Q==> <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com>
In-Reply-To: <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 06 Apr 2010 17:43:34 -0700
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 17:06:23 -0000

Hui is correct, Windows has per-interface DNS server lists configured.

It then uses a host-wide "effective" server list for an actual query,
where the effective server list may be different for different names.

On Windows the per-interface suffix is actually termed the
"connection-specific DNS suffix" to distinguish it from the
"primary DNS suffix" of the machine.  I think that's why
"interface-specific" was repeated in the first bullet.

Example on Windows, extracted from "ipconfig /all" output:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : dthaler-win7
   Primary Dns Suffix  . . . . . . . : ntdev.corp.microsoft.com
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ntdev.corp.microsoft.com
                                       redmond.corp.microsoft.com
                                       ntdev.microsoft.com
                                       dns.corp.microsoft.com
   System Quarantine State . . . . . : Not Restricted

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
   Physical Address. . . . . . . . . : 00-1D-E0-34-4F-6F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4853:4753:9d8d:3b45%13(Preferr=
ed)
   IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, April 05, 2010 10:19:02 PM
   Lease Expires . . . . . . . . . . : Tuesday, April 06, 2010 10:19:02 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 335551968
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-=
8D-DD

   DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
                                       192.168.0.1
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   NetBIOS over Tcpip. . . . . . . . : Enabled

-Dave

> -----Original Message-----
> From: Hui Deng [mailto:denghui02@gmail.com]
> Sent: Monday, April 05, 2010 7:40 PM
> To: Dan Wing; Gabriel Montenegro; Dave Thaler
> Cc: mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>=20
> DNS server always has specific interface related information,
> but the final DNS server will still be host based, I wouldn't say it
> is not correct.
>=20
> one example would be you have internet connection and vpn connection
> at the same time,
> good VPN implementation will always rely on VPN DNS server information
> for Internet connection.
>=20
> -Hui
>=20
> 2010/3/31 Dan Wing <dwing@cisco.com>:
> > Section 3.2.1.3 of describes the DNS configuration of Windows, and
> says:
> >
> > =A0"Interface specific DNS configuration can be input via static
> > =A0 configuration or via DHCP. =A0It includes:
> >
> > =A0 o =A0An interface-specific suffix list.
> >
> > =A0 o =A0A list of DNS server IP addresses."
> >
> > It is curious that the first bullet repeats "interface specific", but
> the
> > second bullet does not repeat it. =A0A reasonable interpretation is
> that the
> > second bullet is not interface-specific, but the lead-in sentence
> says this is
> > interface-specific. =A0I was hoping draft-montenegro-mif-multihoming-00
> would
> > clarify, but it doesn't.
> >
> > -d
> >
> > _______________________________________________
> > mif mailing list
> > mif@ietf.org
> > https://www.ietf.org/mailman/listinfo/mif
> >


From dthaler@microsoft.com  Tue Apr  6 12:43:22 2010
Return-Path: <dthaler@microsoft.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 061793A68E8 for <mif@core3.amsl.com>; Tue,  6 Apr 2010 12:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 MczuTPGkW48t for <mif@core3.amsl.com>; Tue,  6 Apr 2010 12:43:21 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id E417C3A687E for <mif@ietf.org>; Tue,  6 Apr 2010 12:43:20 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 6 Apr 2010 12:43:18 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.21; Tue, 6 Apr 2010 12:43:17 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.63]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 6 Apr 2010 12:43:02 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Hui Deng' <denghui02@gmail.com>, "Gabriel Montenegro" <gmonte@microsoft.com>
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AQHK1TKMaTaZ5uEk9UKBxenwZvGT9pIVqnJAgAAdoSCAAA5RwA==
Date: Tue, 6 Apr 2010 19:42:41 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <AcrQXSIWX7VrtDK7SBKyEB9Yj26v2Q==> <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com>
In-Reply-To: <07e201cad5ba$4d53eea0$7893150a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 06 Apr 2010 17:43:34 -0700
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 06 Apr 2010 19:43:22 -0000

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, April 06, 2010 11:52 AM
> To: Dave Thaler; 'Hui Deng'; Gabriel Montenegro
> Cc: mif@ietf.org
> Subject: RE: [mif] draft-ietf-mif-current-practices-00
>=20
>=20
>=20
> > -----Original Message-----
> > From: Dave Thaler [mailto:dthaler@microsoft.com]
> > Sent: Tuesday, April 06, 2010 10:06 AM
> > To: Hui Deng; Dan Wing; Gabriel Montenegro
> > Cc: mif@ietf.org
> > Subject: RE: [mif] draft-ietf-mif-current-practices-00
> >
> > Hui is correct, Windows has per-interface DNS server lists
> configured.
> >
> > It then uses a host-wide "effective" server list for an actual query,
> > where the effective server list may be different for different names.
> >
> > On Windows the per-interface suffix is actually termed the
> > "connection-specific DNS suffix" to distinguish it from the
> > "primary DNS suffix" of the machine.  I think that's why
> > "interface-specific" was repeated in the first bullet.
>=20
>=20
>=20
> In draft-montenegro-mif-multihoming, there are two purposes and terms
> that
> seem to be intermingled using the term "DNS suffix".
>=20
> One purpose is the suffix for non-FQDN names, like "payroll" or "mail",
> which will have a suffix added to them (e.g., example.com). =20

That's what windows calls the "DNS Suffix Search List" (see the
sample output I sent previously below).  It's called the
"domain search list" in other places (like RFC 3397), or just
"search list" (RFC 1123).

> The
> other purpose is deciding which DNS server will be be sent a query for
> a certain FQDN (e.g., queries for *.example.net go to one DNS server
> and queries for *.example.com go to a different DNS server).

Another purpose is deciding which DNS server will receive a dynamic=20
update for a name with a certain suffix (e.g., Windows supports dynamic
updates for the primary DNS name, and optionally also the connection-
specific DNS name of the machine).

>=20
>=20
> In draft-ietf-mif-current-practices-00, which is the WG document
> that seems to have boiled down draft-montenegro-mif-multihoming,
> but draft-ietf-mif-current-practices-00 also does not clearly
> separate the two purposes.

Yep

-Dave
>=20
> -d
>=20
>=20
> > Example on Windows, extracted from "ipconfig /all" output:
> >
> > Windows IP Configuration
> >
> >    Host Name . . . . . . . . . . . . : dthaler-win7
> >    Primary Dns Suffix  . . . . . . . : ntdev.corp.microsoft.com
> >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    Node Type . . . . . . . . . . . . : Hybrid
> >    IP Routing Enabled. . . . . . . . : No
> >    WINS Proxy Enabled. . . . . . . . : No
> >    DNS Suffix Search List. . . . . . : ntdev.corp.microsoft.com
> >                                        redmond.corp.microsoft.com
> >                                        ntdev.microsoft.com
> >                                        dns.corp.microsoft.com
> >    System Quarantine State . . . . . : Not Restricted
> >
> > Wireless LAN adapter Wireless Network Connection:
> >
> >    Connection-specific DNS Suffix  . : hsd1.wa.comcast.net.
> >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> > Link 4965AGN
> >    Physical Address. . . . . . . . . : 00-1D-E0-34-4F-6F
> >    DHCP Enabled. . . . . . . . . . . : Yes
> >    Autoconfiguration Enabled . . . . : Yes
> >    Link-local IPv6 Address . . . . . :
> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> >    IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> >    Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >    Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> > 10:19:02 PM
> >    Lease Expires . . . . . . . . . . : Tuesday, April 06,
> > 2010 10:19:02 PM
> >    Default Gateway . . . . . . . . . : 192.168.0.1
> >    DHCP Server . . . . . . . . . . . : 192.168.0.1
> >    DHCPv6 IAID . . . . . . . . . . . : 335551968
> >    DHCPv6 Client DUID. . . . . . . . :
> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> >
> >    DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> >                                        192.168.0.1
> >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    NetBIOS over Tcpip. . . . . . . . : Enabled
> >
> > -Dave
> >
> > > -----Original Message-----
> > > From: Hui Deng [mailto:denghui02@gmail.com]
> > > Sent: Monday, April 05, 2010 7:40 PM
> > > To: Dan Wing; Gabriel Montenegro; Dave Thaler
> > > Cc: mif@ietf.org
> > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> > >
> > > DNS server always has specific interface related information,
> > > but the final DNS server will still be host based, I wouldn't say
> it
> > > is not correct.
> > >
> > > one example would be you have internet connection and vpn
> connection
> > > at the same time,
> > > good VPN implementation will always rely on VPN DNS server
> > information
> > > for Internet connection.
> > >
> > > -Hui
> > >
> > > 2010/3/31 Dan Wing <dwing@cisco.com>:
> > > > Section 3.2.1.3 of describes the DNS configuration of Windows,
> and
> > > says:
> > > >
> > > > =A0"Interface specific DNS configuration can be input via static
> > > > =A0 configuration or via DHCP. =A0It includes:
> > > >
> > > > =A0 o =A0An interface-specific suffix list.
> > > >
> > > > =A0 o =A0A list of DNS server IP addresses."
> > > >
> > > > It is curious that the first bullet repeats "interface
> > specific", but
> > > the
> > > > second bullet does not repeat it. =A0A reasonable interpretation is
> > > that the
> > > > second bullet is not interface-specific, but the lead-in sentence
> > > says this is
> > > > interface-specific. =A0I was hoping
> > draft-montenegro-mif-multihoming-00
> > > would
> > > > clarify, but it doesn't.
> > > >
> > > > -d
> > > >
> > > > _______________________________________________
> > > > mif mailing list
> > > > mif@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mif
> > > >
> >
>=20


From denghui02@gmail.com  Wed Apr  7 19:29:00 2010
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 0F31B3A62C1 for <mif@core3.amsl.com>; Wed,  7 Apr 2010 19:29:00 -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 qIH-KNVgCHQS for <mif@core3.amsl.com>; Wed,  7 Apr 2010 19:28:57 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 400AD3A6841 for <mif@ietf.org>; Wed,  7 Apr 2010 19:28:57 -0700 (PDT)
Received: by gyh4 with SMTP id 4so940109gyh.31 for <mif@ietf.org>; Wed, 07 Apr 2010 19:28:51 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uKHnShCUya7E0Aw8ZQaNFu/bMz4XjK8BrU8aQFfZYts=; b=CkMSlr17d61SIOCA20TG3B4vKCdbjL41qrqzOrPl/rB1BbwegPQoa2DP9K5dNQWok9 sphwbURCgepNU25BPq3MUAzPOO5YIjj5Ld79yswWNGTaNArKWEk6GdfZ4Hqvbz3Cjof3 8ZSooqs76meCDoMLLiQ3AWUZzDXOB6VM/cnzk=
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=dllOACqXYxsYh2a0+LkQ4VchcYQT65MPMYTlyGjTkysg9cYSUhVbLPMvznzhBYhdcz 3VjQRmHDKfSxOELuWP8UY2lOqhwaTIabPfd2hw6leIzxEPcW7yEUCZioKs+N42ca7t0v 6c7hWTdSck5wNqyWFlBc+LM8CAcS6BP8Q3S7E=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Wed, 7 Apr 2010 19:28:48 -0700 (PDT)
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 8 Apr 2010 10:28:48 +0800
Received: by 10.100.224.10 with SMTP id w10mr14982495ang.183.1270693728669;  Wed, 07 Apr 2010 19:28:48 -0700 (PDT)
Message-ID: <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Dave Thaler <dthaler@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mif@ietf.org" <mif@ietf.org>, Gabriel Montenegro <gmonte@microsoft.com>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 08 Apr 2010 02:29:00 -0000

2nd purpose has been documented in the current practice draft,
whether 1st and 3rd purpose need to be documented as well? it may not
directly related to MIF?

-Hui

2010/4/7 Dave Thaler <dthaler@microsoft.com>:
>> -----Original Message-----
>> From: Dan Wing [mailto:dwing@cisco.com]
>> Sent: Tuesday, April 06, 2010 11:52 AM
>> To: Dave Thaler; 'Hui Deng'; Gabriel Montenegro
>> Cc: mif@ietf.org
>> Subject: RE: [mif] draft-ietf-mif-current-practices-00
>>
>>
>>
>> > -----Original Message-----
>> > From: Dave Thaler [mailto:dthaler@microsoft.com]
>> > Sent: Tuesday, April 06, 2010 10:06 AM
>> > To: Hui Deng; Dan Wing; Gabriel Montenegro
>> > Cc: mif@ietf.org
>> > Subject: RE: [mif] draft-ietf-mif-current-practices-00
>> >
>> > Hui is correct, Windows has per-interface DNS server lists
>> configured.
>> >
>> > It then uses a host-wide "effective" server list for an actual query,
>> > where the effective server list may be different for different names.
>> >
>> > On Windows the per-interface suffix is actually termed the
>> > "connection-specific DNS suffix" to distinguish it from the
>> > "primary DNS suffix" of the machine. =A0I think that's why
>> > "interface-specific" was repeated in the first bullet.
>>
>>
>>
>> In draft-montenegro-mif-multihoming, there are two purposes and terms
>> that
>> seem to be intermingled using the term "DNS suffix".
>>
>> One purpose is the suffix for non-FQDN names, like "payroll" or "mail",
>> which will have a suffix added to them (e.g., example.com).
>
> That's what windows calls the "DNS Suffix Search List" (see the
> sample output I sent previously below). =A0It's called the
> "domain search list" in other places (like RFC 3397), or just
> "search list" (RFC 1123).
>
>> The
>> other purpose is deciding which DNS server will be be sent a query for
>> a certain FQDN (e.g., queries for *.example.net go to one DNS server
>> and queries for *.example.com go to a different DNS server).
>
> Another purpose is deciding which DNS server will receive a dynamic
> update for a name with a certain suffix (e.g., Windows supports dynamic
> updates for the primary DNS name, and optionally also the connection-
> specific DNS name of the machine).
>
>>
>>
>> In draft-ietf-mif-current-practices-00, which is the WG document
>> that seems to have boiled down draft-montenegro-mif-multihoming,
>> but draft-ietf-mif-current-practices-00 also does not clearly
>> separate the two purposes.
>
> Yep
>
> -Dave
>>
>> -d
>>
>>
>> > Example on Windows, extracted from "ipconfig /all" output:
>> >
>> > Windows IP Configuration
>> >
>> > =A0 =A0Host Name . . . . . . . . . . . . : dthaler-win7
>> > =A0 =A0Primary Dns Suffix =A0. . . . . . . : ntdev.corp.microsoft.com
>> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
>> > =A0 =A0IP Routing Enabled. . . . . . . . : No
>> > =A0 =A0WINS Proxy Enabled. . . . . . . . : No
>> > =A0 =A0DNS Suffix Search List. . . . . . : ntdev.corp.microsoft.com
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0redmond.corp.microsoft.com
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0ntdev.microsoft.com
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0dns.corp.microsoft.com
>> > =A0 =A0System Quarantine State . . . . . : Not Restricted
>> >
>> > Wireless LAN adapter Wireless Network Connection:
>> >
>> > =A0 =A0Connection-specific DNS Suffix =A0. : hsd1.wa.comcast.net.
>> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
>> > Link 4965AGN
>> > =A0 =A0Physical Address. . . . . . . . . : 00-1D-E0-34-4F-6F
>> > =A0 =A0DHCP Enabled. . . . . . . . . . . : Yes
>> > =A0 =A0Autoconfiguration Enabled . . . . : Yes
>> > =A0 =A0Link-local IPv6 Address . . . . . :
>> > fe80::4853:4753:9d8d:3b45%13(Preferred)
>> > =A0 =A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
>> > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
>> > 10:19:02 PM
>> > =A0 =A0Lease Expires . . . . . . . . . . : Tuesday, April 06,
>> > 2010 10:19:02 PM
>> > =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
>> > =A0 =A0DHCP Server . . . . . . . . . . . : 192.168.0.1
>> > =A0 =A0DHCPv6 IAID . . . . . . . . . . . : 335551968
>> > =A0 =A0DHCPv6 Client DUID. . . . . . . . :
>> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
>> >
>> > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0192.168.0.1
>> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > =A0 =A0NetBIOS over Tcpip. . . . . . . . : Enabled
>> >
>> > -Dave
>> >
>> > > -----Original Message-----
>> > > From: Hui Deng [mailto:denghui02@gmail.com]
>> > > Sent: Monday, April 05, 2010 7:40 PM
>> > > To: Dan Wing; Gabriel Montenegro; Dave Thaler
>> > > Cc: mif@ietf.org
>> > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
>> > >
>> > > DNS server always has specific interface related information,
>> > > but the final DNS server will still be host based, I wouldn't say
>> it
>> > > is not correct.
>> > >
>> > > one example would be you have internet connection and vpn
>> connection
>> > > at the same time,
>> > > good VPN implementation will always rely on VPN DNS server
>> > information
>> > > for Internet connection.
>> > >
>> > > -Hui
>> > >
>> > > 2010/3/31 Dan Wing <dwing@cisco.com>:
>> > > > Section 3.2.1.3 of describes the DNS configuration of Windows,
>> and
>> > > says:
>> > > >
>> > > > =A0"Interface specific DNS configuration can be input via static
>> > > > =A0 configuration or via DHCP. =A0It includes:
>> > > >
>> > > > =A0 o =A0An interface-specific suffix list.
>> > > >
>> > > > =A0 o =A0A list of DNS server IP addresses."
>> > > >
>> > > > It is curious that the first bullet repeats "interface
>> > specific", but
>> > > the
>> > > > second bullet does not repeat it. =A0A reasonable interpretation i=
s
>> > > that the
>> > > > second bullet is not interface-specific, but the lead-in sentence
>> > > says this is
>> > > > interface-specific. =A0I was hoping
>> > draft-montenegro-mif-multihoming-00
>> > > would
>> > > > clarify, but it doesn't.
>> > > >
>> > > > -d
>> > > >
>> > > > _______________________________________________
>> > > > mif mailing list
>> > > > mif@ietf.org
>> > > > https://www.ietf.org/mailman/listinfo/mif
>> > > >
>> >
>>
>
>

From dwing@cisco.com  Thu Apr  8 07:22:47 2010
Return-Path: <dwing@cisco.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 E7B373A67AB for <mif@core3.amsl.com>; Thu,  8 Apr 2010 07:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 i9yCqeGc9VTU for <mif@core3.amsl.com>; Thu,  8 Apr 2010 07:22:44 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 4E59F3A6A2B for <mif@ietf.org>; Thu,  8 Apr 2010 07:22:28 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokDALKCvUuQ/uCWe2dsb2JhbACHWIEUkkUVAQELCyIGHKBJmSWFCQSDJA
X-IronPort-AV: E=Sophos;i="4.52,170,1270425600"; d="scan'208";a="59148071"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 08 Apr 2010 14:22:23 +0000
Received: from dwingwxp01 (sjc-vpn2-1352.cisco.com [10.21.117.72]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o38EMLDM011021; Thu, 8 Apr 2010 14:22:22 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Hui Deng'" <denghui02@gmail.com>, "'Dave Thaler'" <dthaler@microsoft.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com>
Date: Thu, 8 Apr 2010 07:22:23 -0700
Message-ID: <0f7701cad726$e8e28990$7893150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcrWwzuT4zXAeGSkQxyDxSYdtOLLhQAY0CNw
In-Reply-To: <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com>
Cc: mif@ietf.org, 'Gabriel Montenegro' <gmonte@microsoft.com>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 08 Apr 2010 14:22:47 -0000

=20

> -----Original Message-----
> From: Hui Deng [mailto:denghui02@gmail.com]=20
> Sent: Wednesday, April 07, 2010 7:29 PM
> To: Dave Thaler
> Cc: Dan Wing; Gabriel Montenegro; mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>=20
> 2nd purpose has been documented in the current practice draft,
> whether 1st and 3rd purpose need to be documented as well? it may not
> directly related to MIF?

Some operating systems -- e.g., most flavors of Unix -- do not support =
the
ability for sending different DNS queries to different DNS servers.

It would be helpful if the draft more clearly described the =
functionality.
Someone unfamiliar with the Windows functionality, reading the draft, =
assumes
it is merely talking about the 'domain search list' -- because that is =
what
they are familiar with. =20

I don't care how the draft is fixed to make it clearer.  I propose =
describing
the 2 (and, as Dave pointed out, 3) functions.  If you want to adjust =
the
document to instead talk about the per-interface stuff, that's great -- =
my
point is that right now it is insufficiently clear in explaining it.

-d

> -Hui
>=20
> 2010/4/7 Dave Thaler <dthaler@microsoft.com>:
> >> -----Original Message-----
> >> From: Dan Wing [mailto:dwing@cisco.com]
> >> Sent: Tuesday, April 06, 2010 11:52 AM
> >> To: Dave Thaler; 'Hui Deng'; Gabriel Montenegro
> >> Cc: mif@ietf.org
> >> Subject: RE: [mif] draft-ietf-mif-current-practices-00
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Dave Thaler [mailto:dthaler@microsoft.com]
> >> > Sent: Tuesday, April 06, 2010 10:06 AM
> >> > To: Hui Deng; Dan Wing; Gabriel Montenegro
> >> > Cc: mif@ietf.org
> >> > Subject: RE: [mif] draft-ietf-mif-current-practices-00
> >> >
> >> > Hui is correct, Windows has per-interface DNS server lists
> >> configured.
> >> >
> >> > It then uses a host-wide "effective" server list for an=20
> actual query,
> >> > where the effective server list may be different for=20
> different names.
> >> >
> >> > On Windows the per-interface suffix is actually termed the
> >> > "connection-specific DNS suffix" to distinguish it from the
> >> > "primary DNS suffix" of the machine. =A0I think that's why
> >> > "interface-specific" was repeated in the first bullet.
> >>
> >>
> >>
> >> In draft-montenegro-mif-multihoming, there are two=20
> purposes and terms
> >> that
> >> seem to be intermingled using the term "DNS suffix".
> >>
> >> One purpose is the suffix for non-FQDN names, like=20
> "payroll" or "mail",
> >> which will have a suffix added to them (e.g., example.com).
> >
> > That's what windows calls the "DNS Suffix Search List" (see the
> > sample output I sent previously below). =A0It's called the
> > "domain search list" in other places (like RFC 3397), or just
> > "search list" (RFC 1123).
> >
> >> The
> >> other purpose is deciding which DNS server will be be sent=20
> a query for
> >> a certain FQDN (e.g., queries for *.example.net go to one=20
> DNS server
> >> and queries for *.example.com go to a different DNS server).
> >
> > Another purpose is deciding which DNS server will receive a dynamic
> > update for a name with a certain suffix (e.g., Windows=20
> supports dynamic
> > updates for the primary DNS name, and optionally also the=20
> connection-
> > specific DNS name of the machine).
> >
> >>
> >>
> >> In draft-ietf-mif-current-practices-00, which is the WG document
> >> that seems to have boiled down draft-montenegro-mif-multihoming,
> >> but draft-ietf-mif-current-practices-00 also does not clearly
> >> separate the two purposes.
> >
> > Yep
> >
> > -Dave
> >>
> >> -d
> >>
> >>
> >> > Example on Windows, extracted from "ipconfig /all" output:
> >> >
> >> > Windows IP Configuration
> >> >
> >> > =A0 =A0Host Name . . . . . . . . . . . . : dthaler-win7
> >> > =A0 =A0Primary Dns Suffix =A0. . . . . . . : =
ntdev.corp.microsoft.com
> >> > =A0 =
=A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
> >> > =A0 =A0IP Routing Enabled. . . . . . . . : No
> >> > =A0 =A0WINS Proxy Enabled. . . . . . . . : No
> >> > =A0 =A0DNS Suffix Search List. . . . . . : =
ntdev.corp.microsoft.com
> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0redmond.corp.microsoft.com
> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0ntdev.microsoft.com
> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0dns.corp.microsoft.com
> >> > =A0 =A0System Quarantine State . . . . . : Not Restricted
> >> >
> >> > Wireless LAN adapter Wireless Network Connection:
> >> >
> >> > =A0 =A0Connection-specific DNS Suffix =A0. : hsd1.wa.comcast.net.
> >> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> >> > Link 4965AGN
> >> > =A0 =A0Physical Address. . . . . . . . . : 00-1D-E0-34-4F-6F
> >> > =A0 =A0DHCP Enabled. . . . . . . . . . . : Yes
> >> > =A0 =A0Autoconfiguration Enabled . . . . : Yes
> >> > =A0 =A0Link-local IPv6 Address . . . . . :
> >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> >> > =A0 =A0IPv4 Address. . . . . . . . . . . : =
192.168.0.195(Preferred)
> >> > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> > =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> >> > 10:19:02 PM
> >> > =A0 =A0Lease Expires . . . . . . . . . . : Tuesday, April 06,
> >> > 2010 10:19:02 PM
> >> > =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
> >> > =A0 =A0DHCP Server . . . . . . . . . . . : 192.168.0.1
> >> > =A0 =A0DHCPv6 IAID . . . . . . . . . . . : 335551968
> >> > =A0 =A0DHCPv6 Client DUID. . . . . . . . :
> >> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> >> >
> >> > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0192.168.0.1
> >> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> > =A0 =A0NetBIOS over Tcpip. . . . . . . . : Enabled
> >> >
> >> > -Dave
> >> >
> >> > > -----Original Message-----
> >> > > From: Hui Deng [mailto:denghui02@gmail.com]
> >> > > Sent: Monday, April 05, 2010 7:40 PM
> >> > > To: Dan Wing; Gabriel Montenegro; Dave Thaler
> >> > > Cc: mif@ietf.org
> >> > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> >> > >
> >> > > DNS server always has specific interface related information,
> >> > > but the final DNS server will still be host based, I=20
> wouldn't say
> >> it
> >> > > is not correct.
> >> > >
> >> > > one example would be you have internet connection and vpn
> >> connection
> >> > > at the same time,
> >> > > good VPN implementation will always rely on VPN DNS server
> >> > information
> >> > > for Internet connection.
> >> > >
> >> > > -Hui
> >> > >
> >> > > 2010/3/31 Dan Wing <dwing@cisco.com>:
> >> > > > Section 3.2.1.3 of describes the DNS configuration=20
> of Windows,
> >> and
> >> > > says:
> >> > > >
> >> > > > =A0"Interface specific DNS configuration can be input=20
> via static
> >> > > > =A0 configuration or via DHCP. =A0It includes:
> >> > > >
> >> > > > =A0 o =A0An interface-specific suffix list.
> >> > > >
> >> > > > =A0 o =A0A list of DNS server IP addresses."
> >> > > >
> >> > > > It is curious that the first bullet repeats "interface
> >> > specific", but
> >> > > the
> >> > > > second bullet does not repeat it. =A0A reasonable=20
> interpretation is
> >> > > that the
> >> > > > second bullet is not interface-specific, but the=20
> lead-in sentence
> >> > > says this is
> >> > > > interface-specific. =A0I was hoping
> >> > draft-montenegro-mif-multihoming-00
> >> > > would
> >> > > > clarify, but it doesn't.
> >> > > >
> >> > > > -d
> >> > > >
> >> > > > _______________________________________________
> >> > > > mif mailing list
> >> > > > mif@ietf.org
> >> > > > https://www.ietf.org/mailman/listinfo/mif
> >> > > >
> >> >
> >>
> >
> >


From g_e_montenegro@yahoo.com  Thu Apr  8 13:17:23 2010
Return-Path: <g_e_montenegro@yahoo.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 D7BA53A694D for <mif@core3.amsl.com>; Thu,  8 Apr 2010 13:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 rEMBnMpbXa+z for <mif@core3.amsl.com>; Thu,  8 Apr 2010 13:17:22 -0700 (PDT)
Received: from web82601.mail.mud.yahoo.com (web82601.mail.mud.yahoo.com [68.142.201.118]) by core3.amsl.com (Postfix) with SMTP id 1560F3A6942 for <mif@ietf.org>; Thu,  8 Apr 2010 13:17:22 -0700 (PDT)
Received: (qmail 31720 invoked by uid 60001); 8 Apr 2010 20:17:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1270757833; bh=sJR7GjIl6IublEe0NqYSD28tD84SIdLXHzPakxOvd7k=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=OcawSKVRres1sUjTXRECcWovAusA+4jcdl5gixYVr18HfR2oFr3kTps0dpFwXI9AkrQSahTm0MYGdDT/SmdFuhKOrRcEOUUNWohEGPb1ErlwkOTyntzioDj5dGuMHlk+TCq24hFsIHitiokNga5wqtJwJn9bkWXbqH8KOD9XKh0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=YGK5L6IT52AIPJ3cuYoJbdiY2yNH6Y1yGkd2vbGyX25xyMbGaWeWnwncP3p0/3lwM5lcVZXooIuzLnqNPhSvEtn70qZ5l0s/oxBVEcfstROw3eRq5Um57yL5ZCLzjE6y8I1YUtHExYx+ncO+EefE+pGsx/rlT8CxvojQf5zbcg8=;
Message-ID: <294720.31470.qm@web82601.mail.mud.yahoo.com>
X-YMail-OSG: 50WIpR0VM1ldE28KdkfBZIGNtdsgNxvYb64vc13lg2AYrZv tSOWYI9bTgxQLEBQnWy2DPHZvLTO7FqiM9bQyeUvf6KjFZD4JSZtn3ap8M0Z sFYjHaPCGY.Nc0OWKyrnGdVN5a.vUOwBSpc27_fA5af0cAK4tVs1lUMu0xFx eKnEayDdNIi6XjL3yqc4.jeNSJJ0ES6aAbhd4lER2XDGkHGiT3vIXcRI9icY AUwoCnPlIJvSqW1_7Ci0LmnLgQDB7CV4xgHBbte0nLHCKQzfuxsOwZ_pyKJr iqffHlgBq7ner64CVXI7aQCWOqeCXBubep118hxINYXWn7xGKbCP2t_2jqum pGiG8wSG_Aq43XIExGiJKl65M5Q--
Received: from [98.237.196.120] by web82601.mail.mud.yahoo.com via HTTP; Thu, 08 Apr 2010 13:17:13 PDT
X-Mailer: YahooMailRC/324.3 YahooMailWebService/0.8.100.260964
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com>
Date: Thu, 8 Apr 2010 13:17:13 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Dan Wing <dwing@cisco.com>, Hui Deng <denghui02@gmail.com>, Dave Thaler <dthaler@microsoft.com>
In-Reply-To: <0f7701cad726$e8e28990$7893150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 08 Apr 2010 20:17:23 -0000

In addition to those three usages of "suffix":=0A=0A1. Domain Search list s=
uffix=0A2. For interface-specific suffix list=A0=0A3. Suffix to control Dyn=
amic DNS=A0Updates=0A=0AThere is yet another usage in Windows introduced in=
 windows 7 and its server counterpart, Windows Server 2008 R2:=0A=0A4. Suff=
ix in the NRPT [1] to aid in identifying a Namespace that requires special =
handling, =0Aas used for DirectAccess [2]. This is not MIF-specific either.=
=0A=0AOnly #2 is MIF-specific (and this should be called out), but it makes=
 sense to clarify the =0Aother uses of "suffix" otherwise #2 won't be clear=
.=0A=0A[1] NRPT: See http://technet.microsoft.com/en-us/magazine/ff394369.a=
spx=0A[2] DirectAcess: http://technet.microsoft.com/en-us/magazine/2009.05.=
cableguy.aspx=0A=0AGabriel=0A=0A----- Original Message ----=0A> From: Dan W=
ing <dwing@cisco.com>=0A> To: Hui Deng <denghui02@gmail.com>; Dave Thaler <=
dthaler@microsoft.com>=0A> Cc: mif@ietf.org; Gabriel Montenegro <gmonte@mic=
rosoft.com>=0A> Sent: Thu, April 8, 2010 7:22:23 AM=0A> Subject: Re: [mif] =
draft-ietf-mif-current-practices-00=0A> =0A> =0A=0A> -----Original Message-=
----=0A> From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com" =
=0A> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com] =0A> Sent: =
=0A> Wednesday, April 07, 2010 7:29 PM=0A> To: Dave Thaler=0A> Cc: Dan Wing=
; =0A> Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org=0A> =
Subject: Re: [mif] =0A> draft-ietf-mif-current-practices-00=0A> =0A> 2nd pu=
rpose has been =0A> documented in the current practice draft,=0A> whether 1=
st and 3rd purpose =0A> need to be documented as well? it may not=0A> direc=
tly related to =0A> MIF?=0A=0ASome operating systems -- e.g., most flavors =
of Unix -- do not =0A> support the=0Aability for sending different DNS quer=
ies to different DNS =0A> servers.=0A=0AIt would be helpful if the draft mo=
re clearly described the =0A> functionality.=0ASomeone unfamiliar with the =
Windows functionality, reading the =0A> draft, assumes=0Ait is merely talki=
ng about the 'domain search list' -- because =0A> that is what=0Athey are f=
amiliar with.=A0 =0A=0AI don't care how the draft =0A> is fixed to make it =
clearer.=A0 I propose describing=0Athe 2 (and, as Dave =0A> pointed out, 3)=
 functions.=A0 If you want to adjust the=0Adocument to =0A> instead talk ab=
out the per-interface stuff, that's great -- my=0Apoint is that =0A> right =
now it is insufficiently clear in explaining it.=0A=0A-d=0A=0A> =0A> -Hui=
=0A> =0A> 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com" =
=0A> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:=0A> =0A>=
 >> -----Original Message-----=0A> >> From: Dan Wing [mailto:> ymailto=3D"m=
ailto:dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com=
]=0A> >> Sent: =0A> Tuesday, April 06, 2010 11:52 AM=0A> >> To: Dave Thaler=
; 'Hui Deng'; =0A> Gabriel Montenegro=0A> >> Cc: > href=3D"mailto:mif@ietf.=
org">mif@ietf.org=0A> >> Subject: RE: [mif] =0A> draft-ietf-mif-current-pra=
ctices-00=0A> >>=0A> >>=0A> =0A> >>=0A> >> > -----Original Message-----=0A>=
 >> > =0A> From: Dave Thaler [mailto:> href=3D"mailto:dthaler@microsoft.com=
">dthaler@microsoft.com]=0A> >> =0A> > Sent: Tuesday, April 06, 2010 10:06 =
AM=0A> >> > To: Hui Deng; =0A> Dan Wing; Gabriel Montenegro=0A> >> > Cc: > =
ymailto=3D"mailto:mif@ietf.org" =0A> href=3D"mailto:mif@ietf.org">mif@ietf.=
org=0A> >> > Subject: RE: =0A> [mif] draft-ietf-mif-current-practices-00=0A=
> >> >=0A> >> =0A> > Hui is correct, Windows has per-interface DNS server l=
ists=0A> >> =0A> configured.=0A> >> >=0A> >> > It then uses a host-wide =0A=
> "effective" server list for an =0A> actual query,=0A> >> > =0A> where the=
 effective server list may be different for =0A> different =0A> names.=0A> =
>> >=0A> >> > On Windows the per-interface =0A> suffix is actually termed t=
he=0A> >> > "connection-specific DNS =0A> suffix" to distinguish it from th=
e=0A> >> > "primary DNS suffix" of =0A> the machine. =A0I think that's why=
=0A> >> > "interface-specific" was =0A> repeated in the first bullet.=0A> >=
>=0A> >>=0A> =0A> >>=0A> >> In draft-montenegro-mif-multihoming, there are =
two =0A> =0A> purposes and terms=0A> >> that=0A> >> seem to be =0A> intermi=
ngled using the term "DNS suffix".=0A> >>=0A> >> One =0A> purpose is the su=
ffix for non-FQDN names, like =0A> "payroll" or =0A> "mail",=0A> >> which w=
ill have a suffix added to them (e.g., > target=3D"_blank" href=3D"http://e=
xample.com">example.com).=0A> >=0A> =0A> > That's what windows calls the "D=
NS Suffix Search List" (see the=0A> =0A> > sample output I sent previously =
below). =A0It's called the=0A> > =0A> "domain search list" in other places =
(like RFC 3397), or just=0A> > =0A> "search list" (RFC 1123).=0A> >=0A> >> =
The=0A> >> =0A> other purpose is deciding which DNS server will be be sent =
=0A> a query =0A> for=0A> >> a certain FQDN (e.g., queries for *.> href=3D"=
http://example.net">example.net go to one =0A> DNS server=0A> =0A> >> and q=
ueries for *.example.com go to a different DNS server).=0A> =0A> >=0A> > An=
other purpose is deciding which DNS server will receive a =0A> dynamic=0A> =
> update for a name with a certain suffix (e.g., Windows =0A> =0A> supports=
 dynamic=0A> > updates for the primary DNS name, and =0A> optionally also t=
he =0A> connection-=0A> > specific DNS name of the =0A> machine).=0A> >=0A>=
 >>=0A> >>=0A> >> In =0A> draft-ietf-mif-current-practices-00, which is the=
 WG document=0A> >> =0A> that seems to have boiled down draft-montenegro-mi=
f-multihoming,=0A> =0A> >> but draft-ietf-mif-current-practices-00 also doe=
s not clearly=0A> =0A> >> separate the two purposes.=0A> >=0A> > Yep=0A> =
=0A> >=0A> > -Dave=0A> >>=0A> >> -d=0A> =0A> >>=0A> >>=0A> >> > Example on =
Windows, extracted =0A> from "ipconfig /all" output:=0A> >> >=0A> >> > Wind=
ows =0A> IP Configuration=0A> >> >=0A> >> > =A0 =A0Host Name . . . =0A> . .=
 . . . . . . . : dthaler-win7=0A> >> > =A0 =A0Primary Dns Suffix =A0. =0A> =
. . . . . . : > href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microso=
ft.com=0A> =0A> >> > =A0 =0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^=0A> >> =0A> > =A0 =A0Node Type . . . . . . . . . . . . :=
 Hybrid=0A> >> > =A0 =A0IP =0A> Routing Enabled. . . . . . . . : No=0A> >> =
> =A0 =A0WINS Proxy Enabled. =0A> . . . . . . . : No=0A> >> > =A0 =A0DNS Su=
ffix Search List. . . . . . : =0A> ntdev.corp.microsoft.com=0A> >> > =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =0A> =A0 =
=A0 =A0> href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.=
com=0A> =0A> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0> href=3D"http://ntdev.microsoft.com">ntdev.microsof=
t.com=0A> >> > =0A> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0> href=3D"http://dns.corp.microsoft.com">dns.corp.m=
icrosoft.com=0A> >> =0A> > =A0 =A0System Quarantine State . . . . . : Not R=
estricted=0A> >> =0A> >=0A> >> > Wireless LAN adapter Wireless Network =0A>=
 Connection:=0A> >> >=0A> >> > =A0 =A0Connection-specific =0A> DNS Suffix =
=A0. : > href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.=0A> >> > =
=0A> =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A> >>=
 =0A> > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi=
=0A> =0A> >> > Link 4965AGN=0A> >> > =A0 =A0Physical Address. . . . . . =0A=
> . . . : 00-1D-E0-34-4F-6F=0A> >> > =A0 =A0DHCP Enabled. . . . . . . . . =
=0A> . . : Yes=0A> >> > =A0 =A0Autoconfiguration Enabled . . . . : =0A> Yes=
=0A> >> > =A0 =A0Link-local IPv6 Address . . . . . :=0A> =0A> >> > fe80::48=
53:4753:9d8d:3b45%13(Preferred)=0A> >> > =A0 =0A> =A0IPv4 Address. . . . . =
. . . . . . : 192.168.0.195(Preferred)=0A> >> =0A> > =A0 =A0Subnet Mask . .=
 . . . . . . . . . : 255.255.255.0=0A> >> > =0A> =A0 =A0Lease Obtained. . .=
 . . . . . . . : Monday, April 05, 2010=0A> >> =0A> > 10:19:02 PM=0A> >> > =
=A0 =A0Lease Expires . . . . . . . . . . : =0A> Tuesday, April 06,=0A> >> >=
 2010 10:19:02 PM=0A> >> > =0A> =A0 =A0Default Gateway . . . . . . . . . : =
192.168.0.1=0A> >> > =A0 =A0DHCP =0A> Server . . . . . . . . . . . : 192.16=
8.0.1=0A> >> > =A0 =A0DHCPv6 IAID =0A> . . . . . . . . . . . : 335551968=0A=
> >> > =A0 =A0DHCPv6 Client DUID. . =0A> . . . . . . :=0A> >> > =0A> 00-01-=
00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD=0A> >> >=0A> >> =0A> > =A0 =A0DNS Serve=
rs . . . . . . . . . . . : 2001:df8:0:1::25=0A> >> =0A> > =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.0.1=
=0A> >> > =A0 =0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A> >=
> > =A0 =0A> =A0NetBIOS over Tcpip. . . . . . . . : Enabled=0A> >> >=0A> =
=0A> >> > -Dave=0A> >> >=0A> >> > > =0A> -----Original Message-----=0A> >> =
> > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com" =0A> hr=
ef=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]=0A> >> > =0A> > Sent=
: Monday, April 05, 2010 7:40 PM=0A> >> > > To: Dan =0A> Wing; Gabriel Mont=
enegro; Dave Thaler=0A> >> > > Cc: > ymailto=3D"mailto:mif@ietf.org" =0A> h=
ref=3D"mailto:mif@ietf.org">mif@ietf.org=0A> >> > > Subject: =0A> Re: [mif]=
 draft-ietf-mif-current-practices-00=0A> >> > >=0A> =0A> >> > > DNS server =
always has specific interface related =0A> information,=0A> >> > > but the =
final DNS server will still be =0A> host based, I =0A> wouldn't say=0A> >> =
it=0A> >> > =0A> > is not correct.=0A> >> > >=0A> >> > > one =0A> example w=
ould be you have internet connection and vpn=0A> >> =0A> connection=0A> >> =
> > at the same time,=0A> >> > =0A> > good VPN implementation will always r=
ely on VPN DNS server=0A> >> =0A> > information=0A> >> > > for Internet con=
nection.=0A> =0A> >> > >=0A> >> > > -Hui=0A> >> > =0A> >=0A> >> > > 2010/3/=
31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com" =0A> href=3D"mailto:dwing=
@cisco.com">dwing@cisco.com>:=0A> >> > =0A> > > Section 3.2.1.3 of describe=
s the DNS configuration =0A> of =0A> Windows,=0A> >> and=0A> >> > > says:=
=0A> >> =0A> > > >=0A> >> > > > =A0"Interface specific DNS =0A> configurati=
on can be input =0A> via static=0A> >> > > > =A0 =0A> configuration or via =
DHCP. =A0It includes:=0A> >> > > >=0A> =0A> >> > > > =A0 o =A0An interface-=
specific suffix list.=0A> >> =0A> > > >=0A> >> > > > =A0 o =A0A list of DNS=
 server IP =0A> addresses."=0A> >> > > >=0A> >> > > > It =0A> is curious th=
at the first bullet repeats "interface=0A> >> > =0A> specific", but=0A> >> =
> > the=0A> >> > > > =0A> second bullet does not repeat it. =A0A reasonable=
 =0A> interpretation =0A> is=0A> >> > > that the=0A> >> > > > second =0A> b=
ullet is not interface-specific, but the =0A> lead-in sentence=0A> =0A> >> =
> > says this is=0A> >> > > > =0A> interface-specific. =A0I was hoping=0A> =
>> > =0A> draft-montenegro-mif-multihoming-00=0A> >> > > would=0A> =0A> >> =
> > > clarify, but it doesn't.=0A> >> > > =0A> >=0A> >> > > > -d=0A> >> > >=
 >=0A> =0A> >> > > > _______________________________________________=0A> =
=0A> >> > > > mif mailing list=0A> >> > > > > ymailto=3D"mailto:mif@ietf.or=
g" =0A> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A> >> > > > > href=3D"ht=
tps://www.ietf.org/mailman/listinfo/mif" target=3D_blank =0A> >https://www.=
ietf.org/mailman/listinfo/mif=0A> >> > > =0A> >=0A> >> >=0A> >>=0A> >=0A> =
=0A> >=0A=0A_______________________________________________=0Amif mailing =
=0A> list=0A> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A> href=3D"https:/=
/www.ietf.org/mailman/listinfo/mif" target=3D_blank =0A> >https://www.ietf.=
org/mailman/listinfo/mif

From denghui02@gmail.com  Fri Apr  9 06:29:13 2010
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 36E8B3A6801 for <mif@core3.amsl.com>; Fri,  9 Apr 2010 06:29: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 iU4OXjveGtCV for <mif@core3.amsl.com>; Fri,  9 Apr 2010 06:29:11 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 642593A63C9 for <mif@ietf.org>; Fri,  9 Apr 2010 06:29:11 -0700 (PDT)
Received: by pwj2 with SMTP id 2so2766369pwj.31 for <mif@ietf.org>; Fri, 09 Apr 2010 06:29:05 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JHKk09e7IezoLpAGmzWPnP5wXZNVENlOZrnE3JidgLo=; b=IpvoQHcV9gB1NrMdtJxy5r2GzTxpHkbrdK3ZIUKVdxEbxo6G61zFo6ucQPk1/eXG+V 2rQtKKAWAPe4EsWokuf0cxKwH2gk1TUwVKZJJEl2sOj/5co6PA1Voj5VhX9KjKaMLnB2 ai+uogyjo+O+sfKmnZXailEvbGN4rpPtsNdKA=
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=ATVmDGP8oSf2xbr7t+9ia9gcnfH6etg81bKki1xRo/i9vRcHgUWYYB6sInTITWJw3m JmYlN8DGnnh4osQNqYPjALDJPx2M4jQs3OemCEQNmk5DxuXlpXqT/dkRJc16lAylSCqm IGx6piuuR2HGWGGTjUUmuOquA0M1HrG0uxncU=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Fri, 9 Apr 2010 06:29:04 -0700 (PDT)
In-Reply-To: <294720.31470.qm@web82601.mail.mud.yahoo.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com>
Date: Fri, 9 Apr 2010 21:29:04 +0800
Received: by 10.142.74.1 with SMTP id w1mr21875wfa.258.1270819745074; Fri, 09  Apr 2010 06:29:05 -0700 (PDT)
Message-ID: <j2x1d38a3351004090629tce6af37ejf5d463d5d0faac9e@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: gabriel montenegro <g_e_montenegro@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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: Fri, 09 Apr 2010 13:29:13 -0000

Hi Gabriel,

Thanks for your sending the summary of usage and reference,
It become more clear about suffix now.

Btw, could you kind help again to make the revision text
for MIF current practice draft related to this?

Thanks again

-Hui


2010/4/9 gabriel montenegro <g_e_montenegro@yahoo.com>:
> In addition to those three usages of "suffix":
>
> 1. Domain Search list suffix
> 2. For interface-specific suffix list
> 3. Suffix to control Dynamic DNS=A0Updates
>
> There is yet another usage in Windows introduced in windows 7 and its ser=
ver counterpart, Windows Server 2008 R2:
>
> 4. Suffix in the NRPT [1] to aid in identifying a Namespace that requires=
 special handling,
> as used for DirectAccess [2]. This is not MIF-specific either.
>
> Only #2 is MIF-specific (and this should be called out), but it makes sen=
se to clarify the
> other uses of "suffix" otherwise #2 won't be clear.
>
> [1] NRPT: See http://technet.microsoft.com/en-us/magazine/ff394369.aspx
> [2] DirectAcess: http://technet.microsoft.com/en-us/magazine/2009.05.cabl=
eguy.aspx
>
> Gabriel
>
> ----- Original Message ----
>> From: Dan Wing <dwing@cisco.com>
>> To: Hui Deng <denghui02@gmail.com>; Dave Thaler <dthaler@microsoft.com>
>> Cc: mif@ietf.org; Gabriel Montenegro <gmonte@microsoft.com>
>> Sent: Thu, April 8, 2010 7:22:23 AM
>> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>>
>>
>
>> -----Original Message-----
>> From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
>> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
>> Sent:
>> Wednesday, April 07, 2010 7:29 PM
>> To: Dave Thaler
>> Cc: Dan Wing;
>> Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org
>> Subject: Re: [mif]
>> draft-ietf-mif-current-practices-00
>>
>> 2nd purpose has been
>> documented in the current practice draft,
>> whether 1st and 3rd purpose
>> need to be documented as well? it may not
>> directly related to
>> MIF?
>
> Some operating systems -- e.g., most flavors of Unix -- do not
>> support the
> ability for sending different DNS queries to different DNS
>> servers.
>
> It would be helpful if the draft more clearly described the
>> functionality.
> Someone unfamiliar with the Windows functionality, reading the
>> draft, assumes
> it is merely talking about the 'domain search list' -- because
>> that is what
> they are familiar with.
>
> I don't care how the draft
>> is fixed to make it clearer.=A0 I propose describing
> the 2 (and, as Dave
>> pointed out, 3) functions.=A0 If you want to adjust the
> document to
>> instead talk about the per-interface stuff, that's great -- my
> point is that
>> right now it is insufficiently clear in explaining it.
>
> -d
>
>>
>> -Hui
>>
>> 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com"
>> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
>>
>> >> -----Original Message-----
>> >> From: Dan Wing [mailto:> ymailto=3D"mailto:dwing@cisco.com"
>> href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
>> >> Sent:
>> Tuesday, April 06, 2010 11:52 AM
>> >> To: Dave Thaler; 'Hui Deng';
>> Gabriel Montenegro
>> >> Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org
>> >> Subject: RE: [mif]
>> draft-ietf-mif-current-practices-00
>> >>
>> >>
>>
>> >>
>> >> > -----Original Message-----
>> >> >
>> From: Dave Thaler [mailto:> href=3D"mailto:dthaler@microsoft.com">dthale=
r@microsoft.com]
>> >>
>> > Sent: Tuesday, April 06, 2010 10:06 AM
>> >> > To: Hui Deng;
>> Dan Wing; Gabriel Montenegro
>> >> > Cc: > ymailto=3D"mailto:mif@ietf.org"
>> href=3D"mailto:mif@ietf.org">mif@ietf.org
>> >> > Subject: RE:
>> [mif] draft-ietf-mif-current-practices-00
>> >> >
>> >>
>> > Hui is correct, Windows has per-interface DNS server lists
>> >>
>> configured.
>> >> >
>> >> > It then uses a host-wide
>> "effective" server list for an
>> actual query,
>> >> >
>> where the effective server list may be different for
>> different
>> names.
>> >> >
>> >> > On Windows the per-interface
>> suffix is actually termed the
>> >> > "connection-specific DNS
>> suffix" to distinguish it from the
>> >> > "primary DNS suffix" of
>> the machine. =A0I think that's why
>> >> > "interface-specific" was
>> repeated in the first bullet.
>> >>
>> >>
>>
>> >>
>> >> In draft-montenegro-mif-multihoming, there are two
>>
>> purposes and terms
>> >> that
>> >> seem to be
>> intermingled using the term "DNS suffix".
>> >>
>> >> One
>> purpose is the suffix for non-FQDN names, like
>> "payroll" or
>> "mail",
>> >> which will have a suffix added to them (e.g., > target=3D"_blank" hre=
f=3D"http://example.com">example.com).
>> >
>>
>> > That's what windows calls the "DNS Suffix Search List" (see the
>>
>> > sample output I sent previously below). =A0It's called the
>> >
>> "domain search list" in other places (like RFC 3397), or just
>> >
>> "search list" (RFC 1123).
>> >
>> >> The
>> >>
>> other purpose is deciding which DNS server will be be sent
>> a query
>> for
>> >> a certain FQDN (e.g., queries for *.> href=3D"http://example.net">exa=
mple.net go to one
>> DNS server
>>
>> >> and queries for *.example.com go to a different DNS server).
>>
>> >
>> > Another purpose is deciding which DNS server will receive a
>> dynamic
>> > update for a name with a certain suffix (e.g., Windows
>>
>> supports dynamic
>> > updates for the primary DNS name, and
>> optionally also the
>> connection-
>> > specific DNS name of the
>> machine).
>> >
>> >>
>> >>
>> >> In
>> draft-ietf-mif-current-practices-00, which is the WG document
>> >>
>> that seems to have boiled down draft-montenegro-mif-multihoming,
>>
>> >> but draft-ietf-mif-current-practices-00 also does not clearly
>>
>> >> separate the two purposes.
>> >
>> > Yep
>>
>> >
>> > -Dave
>> >>
>> >> -d
>>
>> >>
>> >>
>> >> > Example on Windows, extracted
>> from "ipconfig /all" output:
>> >> >
>> >> > Windows
>> IP Configuration
>> >> >
>> >> > =A0 =A0Host Name . . .
>> . . . . . . . . . : dthaler-win7
>> >> > =A0 =A0Primary Dns Suffix =A0.
>> . . . . . . : > href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.micr=
osoft.com
>>
>> >> >
>> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >>
>> > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
>> >> > =A0 =A0IP
>> Routing Enabled. . . . . . . . : No
>> >> > =A0 =A0WINS Proxy Enabled.
>> . . . . . . . : No
>> >> > =A0 =A0DNS Suffix Search List. . . . . . :
>> ntdev.corp.microsoft.com
>> >> >
>> =A0 =A0 =A0> href=3D"http://redmond.corp.microsoft.com">redmond.corp.mic=
rosoft.com
>>
>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0> href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
>> >> >
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0> href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
>> >>
>> > =A0 =A0System Quarantine State . . . . . : Not Restricted
>> >>
>> >
>> >> > Wireless LAN adapter Wireless Network
>> Connection:
>> >> >
>> >> > =A0 =A0Connection-specific
>> DNS Suffix =A0. : > href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.=
net.
>> >> >
>> =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >>
>> > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
>>
>> >> > Link 4965AGN
>> >> > =A0 =A0Physical Address. . . . . .
>> . . . : 00-1D-E0-34-4F-6F
>> >> > =A0 =A0DHCP Enabled. . . . . . . . .
>> . . : Yes
>> >> > =A0 =A0Autoconfiguration Enabled . . . . :
>> Yes
>> >> > =A0 =A0Link-local IPv6 Address . . . . . :
>>
>> >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
>> >> >
>> =A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
>> >>
>> > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> >
>> =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
>> >>
>> > 10:19:02 PM
>> >> > =A0 =A0Lease Expires . . . . . . . . . . :
>> Tuesday, April 06,
>> >> > 2010 10:19:02 PM
>> >> >
>> =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
>> >> > =A0 =A0DHCP
>> Server . . . . . . . . . . . : 192.168.0.1
>> >> > =A0 =A0DHCPv6 IAID
>> . . . . . . . . . . . : 335551968
>> >> > =A0 =A0DHCPv6 Client DUID. .
>> . . . . . . :
>> >> >
>> 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
>> >> >
>> >>
>> > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
>> >>
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0192.168.0.1
>> >> >
>> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >> >
>> =A0NetBIOS over Tcpip. . . . . . . . : Enabled
>> >> >
>>
>> >> > -Dave
>> >> >
>> >> > >
>> -----Original Message-----
>> >> > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
>> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
>> >> >
>> > Sent: Monday, April 05, 2010 7:40 PM
>> >> > > To: Dan
>> Wing; Gabriel Montenegro; Dave Thaler
>> >> > > Cc: > ymailto=3D"mailto:mif@ietf.org"
>> href=3D"mailto:mif@ietf.org">mif@ietf.org
>> >> > > Subject:
>> Re: [mif] draft-ietf-mif-current-practices-00
>> >> > >
>>
>> >> > > DNS server always has specific interface related
>> information,
>> >> > > but the final DNS server will still be
>> host based, I
>> wouldn't say
>> >> it
>> >> >
>> > is not correct.
>> >> > >
>> >> > > one
>> example would be you have internet connection and vpn
>> >>
>> connection
>> >> > > at the same time,
>> >> >
>> > good VPN implementation will always rely on VPN DNS server
>> >>
>> > information
>> >> > > for Internet connection.
>>
>> >> > >
>> >> > > -Hui
>> >> >
>> >
>> >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"
>> href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
>> >> >
>> > > Section 3.2.1.3 of describes the DNS configuration
>> of
>> Windows,
>> >> and
>> >> > > says:
>> >>
>> > > >
>> >> > > > =A0"Interface specific DNS
>> configuration can be input
>> via static
>> >> > > >
>> configuration or via DHCP. =A0It includes:
>> >> > > >
>>
>> >> > > > =A0 o =A0An interface-specific suffix list.
>> >>
>> > > >
>> >> > > > =A0 o =A0A list of DNS server IP
>> addresses."
>> >> > > >
>> >> > > > It
>> is curious that the first bullet repeats "interface
>> >> >
>> specific", but
>> >> > > the
>> >> > > >
>> second bullet does not repeat it. =A0A reasonable
>> interpretation
>> is
>> >> > > that the
>> >> > > > second
>> bullet is not interface-specific, but the
>> lead-in sentence
>>
>> >> > > says this is
>> >> > > >
>> interface-specific. =A0I was hoping
>> >> >
>> draft-montenegro-mif-multihoming-00
>> >> > > would
>>
>> >> > > > clarify, but it doesn't.
>> >> > >
>> >
>> >> > > > -d
>> >> > > >
>>
>> >> > > > _______________________________________________
>>
>> >> > > > mif mailing list
>> >> > > > > ymailto=3D"mailto:mif@ietf.org"
>> href=3D"mailto:mif@ietf.org">mif@ietf.org
>> >> > > > > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_=
blank
>> >https://www.ietf.org/mailman/listinfo/mif
>> >> > >
>> >
>> >> >
>> >>
>> >
>>
>> >
>
> _______________________________________________
> mif mailing
>> list
>> href=3D"mailto:mif@ietf.org">mif@ietf.org
>> href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
>> >https://www.ietf.org/mailman/listinfo/mif
>

From denghui02@gmail.com  Fri Apr  9 08:31:36 2010
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 2A2EC28C0CE for <mif@core3.amsl.com>; Fri,  9 Apr 2010 08:31: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=[AWL=0.000,  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 Gj8OtuAT4ugu for <mif@core3.amsl.com>; Fri,  9 Apr 2010 08:31:35 -0700 (PDT)
Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by core3.amsl.com (Postfix) with ESMTP id 68DEF3A683A for <mif@ietf.org>; Fri,  9 Apr 2010 08:31:32 -0700 (PDT)
Received: by iwn27 with SMTP id 27so2425086iwn.5 for <mif@ietf.org>; Fri, 09 Apr 2010 08:31:26 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2wDMqn3QASSXRgquNbaFb2Eti8iPwyeZHpBw+334ZKY=; b=b+3BWV1NPE0zqelg5B9iicWkXzmMmnwc51lMkE1VabCJVdoMJfpfj3RWHa+InpsuPX upZml0W6DMcc19qdCN4ig4tyYCB6xW2JQtrKUBu28Spicp+wX8LonSfoVIhrGd7j11d4 XVrGNSvE8XWw+YAPc6ZmHtRFygJ2MVFqdrKBg=
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=qQAuDMvYdHElj8Gyz/vZEDF0wWFIXbH4ZyhbtrkzSnD2HRD4NamiegtOyb82xgpV4P 8Mzb82mPvWZPXeo/h7HyZrpu2FWyrI61K5xvO6Od7aLy3kSHBZp+gVnRH1JRzR0QHeKN 0iLNxA0Iv6Gn9Wi88E4xPIdepR275j32ZI+8M=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Fri, 9 Apr 2010 08:31:25 -0700 (PDT)
In-Reply-To: <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com>
Date: Fri, 9 Apr 2010 23:31:25 +0800
Received: by 10.231.154.207 with SMTP id p15mr73381ibw.91.1270827085771; Fri,  09 Apr 2010 08:31:25 -0700 (PDT)
Message-ID: <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: George Tsirtsis <tsirtsis@googlemail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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: Fri, 09 Apr 2010 15:31:36 -0000

Hi, George,

just two clarifications AMSS/Brew DNS configuration is
interface based other than host based?

secondly, network profile could identify only APN other than PDP context?

thanks

-Hui

2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:
> Hi all,
>
> I sent this to Margaret during the IETF meeting but I did not hear
> back from her. Maybe it got lost in the IETF noise so I thought I
> might as well forward this to the list.
>
> I hope it helps.
>
> George
>
> ---------- Forwarded message ----------
> From: George Tsirtsis <tsirtsis@googlemail.com>
> Date: Wed, Jul 29, 2009 at 9:58 AM
> Subject: AMSS/Brew Multi-interface handling
> To: mrw@sandstorm.net
>
>
> Hi Margaret,
>
> Here is a description of how multi-interface support is handled by
> Advanced Mobile Station Software (AMSS) that comes with Brew OS for
> all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
> helpful information for draft-mrw-mif-current-practices.
>
> Let me know if you have any questions.
>
> Regards
> George Tsirtsis (wearing a Qualcomm hat)
>
> -------------------------------------------------------------------------=
----------------------------
>
>
> Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
>
> AMSS supports a concept of =93netpolicy=94 which allows each application
> to specify the type of network connectivity desired. =A0The netpolicy
> contains parameters such as access technology, IP version type and
> network profile. =A0Access technology could be a specific technology
> type such as CDMA or WiFi or could be a group of technologies, such as
> ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4, Ipv6
> or Default. =A0The network profile identifies a type of network domain
> or service within a certain network technology, such as 3GPP APN or
> Mobile IP Home Agent. =A0It also specifies all the mandatory parameters
> required to connect to the domain such authentication credentials and
> other optional parameters such as QoS attributes. =A0Network Profile is
> technology specific and set of parameters contained in the profile
> could vary for different technologies.
>
> Two models of network usage are supported.
>
> Applications requiring network connectivity specify an appropriate
> netpolicy in order to select the desired network. =A0The netpolicy may
> match one or more network interfaces. =A0AMSS system selection module
> selects the best interface out of the ones that match the netpolicy
> based on various criteria such as cost, speed or other provisioned
> rules. =A0Application explicitly starts the selected network interface
> and, as a result, the application also gets bound to the corresponding
> network interface. =A0All outbound packets from this application are
> always routed over this bound interface using the source address of
> the interface.
> Alternately, applications may rely on a separate connection manager to
> control (start/stop) the network interface. =A0 =A0In this method,
> applications are not necessarily bound to any one interface. =A0All
> outbound packets from such applications are routed on one of the
> interfaces that match its netpolicy. =A0The routing decision is made
> individually for each packet and =A0selects the best interface based on
> the criteria described above and the destination address. =A0 Source
> address is always that assigned to the interface used to transmit the
> packet.
>
> Note that all of the routing/interface selection decisions are based
> on the netpolicy and not just destination address to avoid overlapping
> private Ipv4 address issue. =A0This also allows multiple (logical)
> interfaces to be configured with the same IP address, for example, to
> handle certain tunnelling scenarios. =A0 Applications that do not
> specify a netpolicy are routed by AMSS to the best possible interface
> using the default netpolicy. =A0Default netpolicy could be pre-defined
> or provisioned by the administrator or operator. =A0Hence default
> interface could vary from device to device and also depends upon the
> available networks at any given time.
> AMSS allows each interface to be configured with its own set of DNS
> configuration parameters =96 a list of DNS servers, domain names etc.
> Interface selected to make a DNS resolution is the one to which
> application making the DNS query is bound. =A0Applications can also
> specify a different netpolicy as part of DNS request to select another
> interface for DNS resolution. =A0Regardless, all the DNS queries are
> sent only over this selected interface using the DNS configuration
> from the interface. =A0 DNS resolution is first attempted with the
> primary server configured in the interface. =A0If a response is not
> received, the queries are sent to all the other servers configured in
> the interface in a sequential manner using a backoff mechanism.
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From g_e_montenegro@yahoo.com  Fri Apr  9 09:12:51 2010
Return-Path: <g_e_montenegro@yahoo.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 401F13A69FA for <mif@core3.amsl.com>; Fri,  9 Apr 2010 09:12:51 -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=[AWL=0.650,  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 EjnXzK1ZdKZx for <mif@core3.amsl.com>; Fri,  9 Apr 2010 09:12:49 -0700 (PDT)
Received: from web82601.mail.mud.yahoo.com (web82601.mail.mud.yahoo.com [68.142.201.118]) by core3.amsl.com (Postfix) with SMTP id 0B23F3A6A24 for <mif@ietf.org>; Fri,  9 Apr 2010 09:12:22 -0700 (PDT)
Received: (qmail 99343 invoked by uid 60001); 9 Apr 2010 16:12:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1270829534; bh=CKOgx0IUrC41jGSRVkFNvEArZ9E6UQxw0pSPp6XYGsc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Y3jdJOt47UVMqkU3u+JNmEOpGU5IumjUTTFN5WAc1rgEic5C96bkd25QAvjHEIMgXEbkrTw2rtbfjKlk4J4Ca0iW/p9RXX5P2BRYO+oRK2rAIbp5MoWahvuYzoXUvJb9BOlfjLA6MNpqXp/RK35rLthhfHO6Mxt3kJiQ9i6beaU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BscRFhwEaAp28B/LDJIuP6/LFhcU5eRWqVIZvB20pGE+hl5SAH2KeC5t1i3hVtYw+/zyzDVb7sxoU+E+jgbrXsLtKqrsy0rCcsw1oSPC/frx74htHetTrFsF+cguNle4Np80gCDdzuW1phLWoCBX9i59jiI+M6+dr7HpEE1gJ8Q=;
Message-ID: <169037.98657.qm@web82601.mail.mud.yahoo.com>
X-YMail-OSG: ct5CaKoVM1n2lcdS1ybEKWDu8ZfWM15uUuvPsYHWgi8cLE7 HYmR8i8viHls5HmQxuFsv_tskCY6m7mSzimwLwOLdvgmuUBuaTbuPh4aLQ3K B6enrRLVG6t4tHubx3xJ7w2DmhIakZmNU5AukYRqSaLYOOUpQzuhgZKcpy2u ZLu6QCwhJfZaWOr.d9G2fehoiE9aUyWsijn6rIvmxOjIvRbdf8Nu8GiWCl4q GYtMPv_PiypqGrJFhowhXL9hG8wrDB_nuObtSH39fHQf4ahT8OVbRyOGHtIg 79gBCGemWMB1QMtJDd0AllAHB._7M9vgGGEU_81E1uL6R.RSlQEWeWSTBk.E OHljZWc00d6E4X4.qp0otVBqs3Q--
Received: from [98.237.196.120] by web82601.mail.mud.yahoo.com via HTTP; Fri, 09 Apr 2010 09:12:14 PDT
X-Mailer: YahooMailRC/348.3 YahooMailWebService/0.8.100.260964
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com> <j2x1d38a3351004090629tce6af37ejf5d463d5d0faac9e@mail.gmail.com>
Date: Fri, 9 Apr 2010 09:12:14 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Hui Deng <denghui02@gmail.com>
In-Reply-To: <j2x1d38a3351004090629tce6af37ejf5d463d5d0faac9e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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: Fri, 09 Apr 2010 16:12:51 -0000

Sure. I'll massage text from this thread and send it to Margaret.=0A=0A=0A=
=0A----- Original Message ----=0A> From: Hui Deng <denghui02@gmail.com>=0A>=
 To: gabriel montenegro <g_e_montenegro@yahoo.com>=0A> Cc: Dan Wing <dwing@=
cisco.com>; Dave Thaler <dthaler@microsoft.com>; mif@ietf.org=0A> Sent: Fri=
, April 9, 2010 6:29:04 AM=0A> Subject: Re: [mif] draft-ietf-mif-current-pr=
actices-00=0A> =0A> Hi Gabriel,=0A=0AThanks for your sending the summary of=
 usage and =0A> reference,=0AIt become more clear about suffix now.=0A=0ABt=
w, could you kind =0A> help again to make the revision text=0Afor MIF curre=
nt practice draft related =0A> to this?=0A=0AThanks again=0A=0A-Hui=0A=0A=
=0A2010/4/9 gabriel montenegro =0A> <> href=3D"mailto:g_e_montenegro@yahoo.=
com">g_e_montenegro@yahoo.com>:=0A> =0A> In addition to those three usages =
of "suffix":=0A>=0A> 1. Domain Search =0A> list suffix=0A> 2. For interface=
-specific suffix list=0A> 3. Suffix to =0A> control Dynamic DNS=A0Updates=
=0A>=0A> There is yet another usage in =0A> Windows introduced in windows 7=
 and its server counterpart, Windows Server 2008 =0A> R2:=0A>=0A> 4. Suffix=
 in the NRPT [1] to aid in identifying a Namespace =0A> that requires speci=
al handling,=0A> as used for DirectAccess [2]. This is =0A> not MIF-specifi=
c either.=0A>=0A> Only #2 is MIF-specific (and this =0A> should be called o=
ut), but it makes sense to clarify the=0A> other uses of =0A> "suffix" othe=
rwise #2 won't be clear.=0A>=0A> [1] NRPT: See =0A> http://technet.microsof=
t.com/en-us/magazine/ff394369.aspx=0A> [2] =0A> DirectAcess: =0A> http://te=
chnet.microsoft.com/en-us/magazine/2009.05.cableguy.aspx=0A>=0A> =0A> Gabri=
el=0A>=0A> ----- Original Message ----=0A>> From: Dan Wing =0A> <> href=3D"=
mailto:dwing@cisco.com">dwing@cisco.com>=0A>> To: Hui Deng =0A> <> href=3D"=
mailto:denghui02@gmail.com">denghui02@gmail.com>; Dave Thaler =0A> <> href=
=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>=0A>> =0A> Cc: > hr=
ef=3D"mailto:mif@ietf.org">mif@ietf.org; Gabriel Montenegro <> ymailto=3D"m=
ailto:gmonte@microsoft.com" =0A> href=3D"mailto:gmonte@microsoft.com">gmont=
e@microsoft.com>=0A>> =0A> Sent: Thu, April 8, 2010 7:22:23 AM=0A>> Subject=
: Re: [mif] =0A> draft-ietf-mif-current-practices-00=0A>>=0A>>=0A>=0A>> =0A=
> -----Original Message-----=0A>> From: Hui Deng [mailto:> =0A> ymailto=3D"=
mailto:> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com"=0A>> =0A>=
 href=3D"mailto:> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com">=
> ymailto=3D"mailto:denghui02@gmail.com" =0A> href=3D"mailto:denghui02@gmai=
l.com">denghui02@gmail.com]=0A>> =0A> Sent:=0A>> Wednesday, April 07, 2010 =
7:29 PM=0A>> To: Dave =0A> Thaler=0A>> Cc: Dan Wing;=0A>> Gabriel Montenegr=
o; > =0A> href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">> hre=
f=3D"mailto:mif@ietf.org">mif@ietf.org=0A>> Subject: Re: =0A> [mif]=0A>> dr=
aft-ietf-mif-current-practices-00=0A>>=0A>> =0A> 2nd purpose has been=0A>> =
documented in the current practice =0A> draft,=0A>> whether 1st and 3rd pur=
pose=0A>> need to be documented =0A> as well? it may not=0A>> directly rela=
ted to=0A>> =0A> MIF?=0A>=0A> Some operating systems -- e.g., most flavors =
of Unix -- do =0A> not=0A>> support the=0A> ability for sending different D=
NS queries to =0A> different DNS=0A>> servers.=0A>=0A> It would be helpful =
if the =0A> draft more clearly described the=0A>> functionality.=0A> Someon=
e =0A> unfamiliar with the Windows functionality, reading the=0A>> draft, =
=0A> assumes=0A> it is merely talking about the 'domain search list' -- =0A=
> because=0A>> that is what=0A> they are familiar with.=0A>=0A> =0A> I don'=
t care how the draft=0A>> is fixed to make it clearer.=A0 I propose =0A> de=
scribing=0A> the 2 (and, as Dave=0A>> pointed out, 3) functions.=A0 =0A> If=
 you want to adjust the=0A> document to=0A>> instead talk about the =0A> pe=
r-interface stuff, that's great -- my=0A> point is that=0A>> right =0A> now=
 it is insufficiently clear in explaining it.=0A>=0A> =0A> -d=0A>=0A>>=0A>>=
 -Hui=0A>>=0A>> 2010/4/7 Dave =0A> Thaler <> ymailto=3D"mailto:> href=3D"ma=
ilto:dthaler@microsoft.com">dthaler@microsoft.com"=0A>> =0A> href=3D"mailto=
:> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com">> ymailto=
=3D"mailto:dthaler@microsoft.com" =0A> href=3D"mailto:dthaler@microsoft.com=
">dthaler@microsoft.com>:=0A>>=0A>> =0A> >> -----Original Message-----=0A>>=
 >> From: Dan Wing =0A> [mailto:> ymailto=3D"mailto:> href=3D"mailto:dwing@=
cisco.com">dwing@cisco.com"=0A>> href=3D"mailto:> ymailto=3D"mailto:dwing@c=
isco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com">> ymailto=
=3D"mailto:dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisc=
o.com]=0A>> >> =0A> Sent:=0A>> Tuesday, April 06, 2010 11:52 AM=0A>> >> To:=
 Dave =0A> Thaler; 'Hui Deng';=0A>> Gabriel Montenegro=0A>> >> Cc: > =0A> h=
ref=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">> href=3D"mailto=
:mif@ietf.org">mif@ietf.org=0A>> >> Subject: RE: =0A> [mif]=0A>> draft-ietf=
-mif-current-practices-00=0A>> =0A> >>=0A>> >>=0A>>=0A>> >>=0A>> =0A> >> > =
-----Original Message-----=0A>> >> >=0A>> =0A> From: Dave Thaler [mailto:> =
href=3D"mailto:> ymailto=3D"mailto:dthaler@microsoft.com" =0A> href=3D"mail=
to:dthaler@microsoft.com">dthaler@microsoft.com">> ymailto=3D"mailto:dthale=
r@microsoft.com" =0A> href=3D"mailto:dthaler@microsoft.com">dthaler@microso=
ft.com]=0A>> =0A> >>=0A>> > Sent: Tuesday, April 06, 2010 10:06 AM=0A>> =0A=
> >> > To: Hui Deng;=0A>> Dan Wing; Gabriel Montenegro=0A>> =0A> >> > Cc: >=
 ymailto=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org"=0A>> href=
=3D"mailto:> ymailto=3D"mailto:mif@ietf.org" href=3D"mailto:mif@ietf.org">m=
if@ietf.org">> ymailto=3D"mailto:mif@ietf.org" =0A> href=3D"mailto:mif@ietf=
.org">mif@ietf.org=0A>> >> > Subject: =0A> RE:=0A>> [mif] draft-ietf-mif-cu=
rrent-practices-00=0A>> >> =0A> >=0A>> >>=0A>> > Hui is correct, Windows ha=
s =0A> per-interface DNS server lists=0A>> >>=0A>> =0A> configured.=0A>> >>=
 >=0A>> >> > It then uses a =0A> host-wide=0A>> "effective" server list for=
 an=0A>> actual =0A> query,=0A>> >> >=0A>> where the effective server list =
may =0A> be different for=0A>> different=0A>> names.=0A>> >> =0A> >=0A>> >>=
 > On Windows the per-interface=0A>> suffix =0A> is actually termed the=0A>=
> >> > "connection-specific =0A> DNS=0A>> suffix" to distinguish it from th=
e=0A>> >> > =0A> "primary DNS suffix" of=0A>> the machine. =A0I think that'=
s why=0A>> =0A> >> > "interface-specific" was=0A>> repeated in the first =
=0A> bullet.=0A>> >>=0A>> >>=0A>>=0A>> =0A> >>=0A>> >> In draft-montenegro-=
mif-multihoming, there are =0A> two=0A>>=0A>> purposes and terms=0A>> >> =
=0A> that=0A>> >> seem to be=0A>> intermingled using the term =0A> "DNS suf=
fix".=0A>> >>=0A>> >> One=0A>> purpose =0A> is the suffix for non-FQDN name=
s, like=0A>> "payroll" or=0A>> =0A> "mail",=0A>> >> which will have a suffi=
x added to them (e.g., > =0A> target=3D"_blank" href=3D"http://example.com"=
>> href=3D"http://example.com">example.com).=0A>> =0A> >=0A>>=0A>> > That's=
 what windows calls the "DNS Suffix =0A> Search List" (see the=0A>>=0A>> > =
sample output I sent =0A> previously below). =A0It's called the=0A>> >=0A>>=
 "domain search =0A> list" in other places (like RFC 3397), or just=0A>> >=
=0A>> =0A> "search list" (RFC 1123).=0A>> >=0A>> >> The=0A>> =0A> >>=0A>> o=
ther purpose is deciding which DNS server will be be =0A> sent=0A>> a query=
=0A>> for=0A>> >> a certain FQDN =0A> (e.g., queries for *.> href=3D"http:/=
/example.net">> href=3D"http://example.net">example.net go to one=0A>> DNS =
=0A> server=0A>>=0A>> >> and queries for *.example.com go to a =0A> differe=
nt DNS server).=0A>>=0A>> >=0A>> > Another =0A> purpose is deciding which D=
NS server will receive a=0A>> =0A> dynamic=0A>> > update for a name with a =
certain suffix (e.g., =0A> Windows=0A>>=0A>> supports dynamic=0A>> > update=
s for =0A> the primary DNS name, and=0A>> optionally also the=0A>> =0A> con=
nection-=0A>> > specific DNS name of the=0A>> =0A> machine).=0A>> >=0A>> >>=
=0A>> >>=0A>> =0A> >> In=0A>> draft-ietf-mif-current-practices-00, which is=
 the WG =0A> document=0A>> >>=0A>> that seems to have boiled down =0A> draf=
t-montenegro-mif-multihoming,=0A>>=0A>> >> but =0A> draft-ietf-mif-current-=
practices-00 also does not =0A> clearly=0A>>=0A>> >> separate the two purpo=
ses.=0A>> =0A> >=0A>> > Yep=0A>>=0A>> >=0A>> > =0A> -Dave=0A>> >>=0A>> >> -=
d=0A>>=0A>> =0A> >>=0A>> >>=0A>> >> > Example on Windows, =0A> extracted=0A=
>> from "ipconfig /all" output:=0A>> >> =0A> >=0A>> >> > Windows=0A>> IP Co=
nfiguration=0A>> =0A> >> >=0A>> >> > =A0 =A0Host Name . . .=0A>> . . . . . =
=0A> . . . . : dthaler-win7=0A>> >> > =A0 =A0Primary Dns Suffix =0A> =A0.=
=0A>> . . . . . . : > href=3D"http://ntdev.corp.microsoft.com">> target=3D"=
_blank" =0A> href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.=
com=0A>>=0A>> =0A> >> >=0A>> =0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^^^^^=0A>> =0A> >>=0A>> > =A0 =A0Node Type . . . . . . . .=
 . . . . : =0A> Hybrid=0A>> >> > =A0 =A0IP=0A>> Routing Enabled. . . . . . =
. =0A> . : No=0A>> >> > =A0 =A0WINS Proxy Enabled.=0A>> . . . . . . =0A> . =
: No=0A>> >> > =A0 =A0DNS Suffix Search List. . . . . . =0A> :=0A>> ntdev.c=
orp.microsoft.com=0A>> >> >=0A>> =A0 =A0 =0A> =A0> href=3D"http://redmond.c=
orp.microsoft.com">> href=3D"http://redmond.corp.microsoft.com">redmond.cor=
p.microsoft.com=0A>>=0A>> =0A> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0> =0A> href=3D"http://ntdev.microso=
ft.com">> href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com=0A>> >> =
=0A> >=0A>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0> =0A> href=3D"http://dns.corp.microsoft.com">> href=3D"htt=
p://dns.corp.microsoft.com">dns.corp.microsoft.com=0A>> =0A> >>=0A>> > =A0 =
=A0System Quarantine State . . . . . : Not =0A> Restricted=0A>> >>=0A>> >=
=0A>> >> > =0A> Wireless LAN adapter Wireless Network=0A>> Connection:=0A>>=
 =0A> >> >=0A>> >> > =A0 =A0Connection-specific=0A>> DNS =0A> Suffix =A0. :=
 > href=3D"http://hsd1.wa.comcast.net">> href=3D"http://hsd1.wa.comcast.net=
">hsd1.wa.comcast.net.=0A>> >> =0A> >=0A>> =A0 =0A> =A0^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A>> =0A> >>=0A>> > =A0 =A0Description=
 . . . . . . . . . . . : Intel(R) =0A> Wireless WiFi=0A>>=0A>> >> > Link 49=
65AGN=0A>> =0A> >> > =A0 =A0Physical Address. . . . . .=0A>> . . . : =0A> 0=
0-1D-E0-34-4F-6F=0A>> >> > =A0 =A0DHCP Enabled. . . . . . . . =0A> .=0A>> .=
 . : Yes=0A>> >> > =A0 =A0Autoconfiguration Enabled . =0A> . . . :=0A>> Yes=
=0A>> >> > =A0 =A0Link-local IPv6 Address . . =0A> . . . :=0A>>=0A>> >> > =
=0A> fe80::4853:4753:9d8d:3b45%13(Preferred)=0A>> >> >=0A>> =0A> =A0IPv4 Ad=
dress. . . . . . . . . . . : 192.168.0.195(Preferred)=0A>> =0A> >>=0A>> > =
=A0 =A0Subnet Mask . . . . . . . . . . . : =0A> 255.255.255.0=0A>> >> >=0A>=
> =A0 =A0Lease Obtained. . . . . . =0A> . . . . : Monday, April 05, 2010=0A=
>> >>=0A>> > 10:19:02 =0A> PM=0A>> >> > =A0 =A0Lease Expires . . . . . . . =
. . . :=0A>> =0A> Tuesday, April 06,=0A>> >> > 2010 10:19:02 PM=0A>> =0A> >=
> >=0A>> =A0 =A0Default Gateway . . . . . . . . . : =0A> 192.168.0.1=0A>> >=
> > =A0 =A0DHCP=0A>> Server . . . . . . . . =0A> . . . : 192.168.0.1=0A>> >=
> > =A0 =A0DHCPv6 IAID=0A>> . . . . =0A> . . . . . . . : 335551968=0A>> >> =
> =A0 =A0DHCPv6 Client DUID. =0A> .=0A>> . . . . . . :=0A>> >> >=0A>> =0A> =
00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD=0A>> >> >=0A>> =0A> >>=0A>> > =A0=
 =A0DNS Servers . . . . . . . . . . . : =0A> 2001:df8:0:1::25=0A>> >>=0A>> =
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =0A> =A0 =A0 =A0 =A0 =
=A0 =A0 =A0192.168.0.1=0A>> >> >=0A>> =0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^=0A>> >> =0A> >=0A>> =A0NetBIOS over Tcpip. . . . . . . .=
 : Enabled=0A>> =0A> >> >=0A>>=0A>> >> > -Dave=0A>> >> =0A> >=0A>> >> > >=
=0A>> -----Original =0A> Message-----=0A>> >> > > From: Hui Deng [mailto:> =
=0A> ymailto=3D"mailto:> href=3D"mailto:denghui02@gmail.com">denghui02@gmai=
l.com"=0A>> =0A> href=3D"mailto:> href=3D"mailto:denghui02@gmail.com">dengh=
ui02@gmail.com">> ymailto=3D"mailto:denghui02@gmail.com" =0A> href=3D"mailt=
o:denghui02@gmail.com">denghui02@gmail.com]=0A>> >> =0A> >=0A>> > Sent: Mon=
day, April 05, 2010 7:40 PM=0A>> >> =0A> > > To: Dan=0A>> Wing; Gabriel Mon=
tenegro; Dave Thaler=0A>> =0A> >> > > Cc: > ymailto=3D"mailto:> href=3D"mai=
lto:mif@ietf.org">mif@ietf.org"=0A>> href=3D"mailto:> ymailto=3D"mailto:mif=
@ietf.org" href=3D"mailto:mif@ietf.org">mif@ietf.org">> ymailto=3D"mailto:m=
if@ietf.org" =0A> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A>> >> > > =0A=
> Subject:=0A>> Re: [mif] draft-ietf-mif-current-practices-00=0A>> =0A> >> =
> >=0A>>=0A>> >> > > DNS server always =0A> has specific interface related=
=0A>> information,=0A>> >> =0A> > > but the final DNS server will still be=
=0A>> host based, =0A> I=0A>> wouldn't say=0A>> >> it=0A>> >> =0A> >=0A>> >=
 is not correct.=0A>> >> > >=0A>> =0A> >> > > one=0A>> example would be you=
 have internet connection =0A> and vpn=0A>> >>=0A>> connection=0A>> >> > =
=0A> > at the same time,=0A>> >> >=0A>> > good VPN =0A> implementation will=
 always rely on VPN DNS server=0A>> =0A> >>=0A>> > information=0A>> >> > > =
for =0A> Internet connection.=0A>>=0A>> >> > >=0A>> =0A> >> > > -Hui=0A>> >=
> >=0A>> >=0A>> =0A> >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:> ymail=
to=3D"mailto:dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@ci=
sco.com"=0A>> href=3D"mailto:> ymailto=3D"mailto:dwing@cisco.com" =0A> href=
=3D"mailto:dwing@cisco.com">dwing@cisco.com">> ymailto=3D"mailto:dwing@cisc=
o.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:=0A>> >> =0A> =
>=0A>> > > Section 3.2.1.3 of describes the DNS =0A> configuration=0A>> of=
=0A>> Windows,=0A>> >> =0A> and=0A>> >> > > says:=0A>> >>=0A>> > =0A> > >=
=0A>> >> > > > =A0"Interface specific =0A> DNS=0A>> configuration can be in=
put=0A>> via static=0A>> =0A> >> > > >=0A>> configuration or via DHCP. =A0I=
t =0A> includes:=0A>> >> > > >=0A>>=0A>> >> =0A> > > > =A0 o =A0An interfac=
e-specific suffix list.=0A>> =0A> >>=0A>> > > >=0A>> >> > > > =A0 o =A0A =
=0A> list of DNS server IP=0A>> addresses."=0A>> >> > > =0A> >=0A>> >> > > =
> It=0A>> is curious that the =0A> first bullet repeats "interface=0A>> >> =
>=0A>> specific", =0A> but=0A>> >> > > the=0A>> >> > > =0A> >=0A>> second b=
ullet does not repeat it. =A0A reasonable=0A>> =0A> interpretation=0A>> is=
=0A>> >> > > that =0A> the=0A>> >> > > > second=0A>> bullet is not =0A> int=
erface-specific, but the=0A>> lead-in sentence=0A>>=0A>> =0A> >> > > says t=
his is=0A>> >> > > >=0A>> =0A> interface-specific. =A0I was hoping=0A>> >> =
>=0A>> =0A> draft-montenegro-mif-multihoming-00=0A>> >> > > =0A> would=0A>>=
=0A>> >> > > > clarify, but it =0A> doesn't.=0A>> >> > >=0A>> >=0A>> >> =0A=
> > > > -d=0A>> >> > > >=0A>>=0A>> =0A> >> > > > =0A> _____________________=
__________________________=0A>>=0A>> >> =0A> > > > mif mailing list=0A>> >>=
 > > > > =0A> ymailto=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org=
"=0A>> href=3D"mailto:> ymailto=3D"mailto:mif@ietf.org" href=3D"mailto:mif@=
ietf.org">mif@ietf.org">> ymailto=3D"mailto:mif@ietf.org" =0A> href=3D"mail=
to:mif@ietf.org">mif@ietf.org=0A>> >> > > > =0A> > href=3D"> >https://www.i=
etf.org/mailman/listinfo/mif" target=3D_blank=0A>> >> href=3D"https://www.i=
etf.org/mailman/listinfo/mif" target=3D_blank =0A> >https://www.ietf.org/ma=
ilman/listinfo/mif=0A>> >> > =0A> >=0A>> >=0A>> >> >=0A>> >>=0A>> =0A> >=0A=
>>=0A>> >=0A>=0A> =0A> _______________________________________________=0A> =
mif mailing=0A>> =0A> list=0A>> href=3D"mailto:> href=3D"mailto:mif@ietf.or=
g">mif@ietf.org">> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A>> href=3D">=
 href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank =0A> >h=
ttps://www.ietf.org/mailman/listinfo/mif" target=3D_blank=0A>> >> href=3D"h=
ttps://www.ietf.org/mailman/listinfo/mif" target=3D_blank =0A> >https://www=
.ietf.org/mailman/listinfo/mif=0A>

From julienl@qualcomm.com  Fri Apr  9 10:12:46 2010
Return-Path: <julienl@qualcomm.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 802CC3A68AA for <mif@core3.amsl.com>; Fri,  9 Apr 2010 10:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.167
X-Spam-Level: 
X-Spam-Status: No, score=-106.167 tagged_above=-999 required=5 tests=[AWL=0.432, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NjXyR0K803XY for <mif@core3.amsl.com>; Fri,  9 Apr 2010 10:12:43 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 206303A688E for <mif@ietf.org>; Fri,  9 Apr 2010 10:12:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1270833160; x=1302369160; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Margaret=20Wasserman=20<mrw@sandstorm.net>,=20Geor ge=20Tsirtsis=0D=0A=09<tsirtsis@googlemail.com>|CC:=20mif =20<mif@ietf.org>|Date:=20Fri,=209=20Apr=202010=2010:12:1 9=20-0700|Subject:=20RE:=20[mif]=20AMSS/Brew=20Multi-inte rface=20handling|Thread-Topic:=20[mif]=20AMSS/Brew=20Mult i-interface=20handling|Thread-Index:=20AcoeepsvPD3sFbJ4SY iaVFfJ49ENgC5jREZA|Message-ID:=20<BF345F63074F8040B58C00A 186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com> |References:=20<d3886a520907290158o33705c50m31e848d2b20c7 64b@mail.gmail.com>=0D=0A=09<d3886a520908160241k52ede41bp ad57325a1c741f3b@mail.gmail.com>=0D=0A=20<424FB149-AE77-4 F63-9C18-EF04B2A20937@sandstorm.net>|In-Reply-To:=20<424F B149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=omhmlIzalURVwaVfjMAfdMBZ1uKg/ZGansmYmwHmEtc=; b=b80ZS+Ca21FrrwXB3nxZp2+YIDXIavxEqFYDtxC/v9Jco4CuSliUG7aF F19hANpWnRZvr6ZDpB4fCyE38n0SGS6Iw60PJlR7A0But1xxqAxcPEu8u H1Hghm1sXJ6nGhsoLKXauzDeilh0Nk542fIx+M7uKrh5y8tegXSW7alr3 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,5946"; a="38403614"
Received: from ironmsg01-l.qualcomm.com ([172.30.48.15]) by wolverine01.qualcomm.com with ESMTP; 09 Apr 2010 10:12:22 -0700
X-IronPort-AV: E=Sophos;i="4.52,176,1270450800";  d="scan'208";a="9025724"
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by ironmsg01-l.qualcomm.com with ESMTP/TLS/RC4-MD5; 09 Apr 2010 10:12:23 -0700
Received: from nalasexhc03.na.qualcomm.com (10.47.129.194) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 9 Apr 2010 10:12:21 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc03.na.qualcomm.com ([10.47.129.194]) with mapi; Fri, 9 Apr 2010 10:12:22 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Margaret Wasserman <mrw@sandstorm.net>, George Tsirtsis <tsirtsis@googlemail.com>
Date: Fri, 9 Apr 2010 10:12:19 -0700
Thread-Topic: [mif] AMSS/Brew Multi-interface handling
Thread-Index: AcoeepsvPD3sFbJ4SYiaVFfJ49ENgC5jREZA
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net>
In-Reply-To: <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net>
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
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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: Fri, 09 Apr 2010 17:12:46 -0000

Hi Margaret -=20

I notice this text is not included in the current rev. of the current pract=
ice draft. Are you going to include it?

Thanks.

--julien

> -----Original Message-----
> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> Margaret Wasserman
> Sent: Sunday, August 16, 2009 7:04 AM
> To: George Tsirtsis
> Cc: mif
> Subject: Re: [mif] AMSS/Brew Multi-interface handling
>=20
>=20
> Hi George,
>=20
> Thanks for sending this!
>=20
> I'll add it to the next version of the draft.
>=20
> Margaret
>=20
> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
>=20
> > Hi all,
> >
> > I sent this to Margaret during the IETF meeting but I did not hear
> > back from her. Maybe it got lost in the IETF noise so I thought I
> > might as well forward this to the list.
> >
> > I hope it helps.
> >
> > George
> >
> > ---------- Forwarded message ----------
> > From: George Tsirtsis <tsirtsis@googlemail.com>
> > Date: Wed, Jul 29, 2009 at 9:58 AM
> > Subject: AMSS/Brew Multi-interface handling
> > To: mrw@sandstorm.net
> >
> >
> > Hi Margaret,
> >
> > Here is a description of how multi-interface support is handled by
> > Advanced Mobile Station Software (AMSS) that comes with Brew OS for
> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
> > helpful information for draft-mrw-mif-current-practices.
> >
> > Let me know if you have any questions.
> >
> > Regards
> > George Tsirtsis (wearing a Qualcomm hat)
> >
> > ---------------------------------------------------------------------
> --------------------------------
> >
> >
> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
> >
> > AMSS supports a concept of "netpolicy" which allows each application
> > to specify the type of network connectivity desired.  The netpolicy
> > contains parameters such as access technology, IP version type and
> > network profile.  Access technology could be a specific technology
> > type such as CDMA or WiFi or could be a group of technologies, such
> as
> > ANY_Cellular or ANY_Wireless.  IP version could be one of Ipv4, Ipv6
> > or Default.  The network profile identifies a type of network domain
> > or service within a certain network technology, such as 3GPP APN or
> > Mobile IP Home Agent.  It also specifies all the mandatory parameters
> > required to connect to the domain such authentication credentials and
> > other optional parameters such as QoS attributes.  Network Profile is
> > technology specific and set of parameters contained in the profile
> > could vary for different technologies.
> >
> > Two models of network usage are supported.
> >
> > Applications requiring network connectivity specify an appropriate
> > netpolicy in order to select the desired network.  The netpolicy may
> > match one or more network interfaces.  AMSS system selection module
> > selects the best interface out of the ones that match the netpolicy
> > based on various criteria such as cost, speed or other provisioned
> > rules.  Application explicitly starts the selected network interface
> > and, as a result, the application also gets bound to the
> corresponding
> > network interface.  All outbound packets from this application are
> > always routed over this bound interface using the source address of
> > the interface.
> > Alternately, applications may rely on a separate connection manager
> to
> > control (start/stop) the network interface.    In this method,
> > applications are not necessarily bound to any one interface.  All
> > outbound packets from such applications are routed on one of the
> > interfaces that match its netpolicy.  The routing decision is made
> > individually for each packet and  selects the best interface based on
> > the criteria described above and the destination address.   Source
> > address is always that assigned to the interface used to transmit the
> > packet.
> >
> > Note that all of the routing/interface selection decisions are based
> > on the netpolicy and not just destination address to avoid
> overlapping
> > private Ipv4 address issue.  This also allows multiple (logical)
> > interfaces to be configured with the same IP address, for example, to
> > handle certain tunnelling scenarios.   Applications that do not
> > specify a netpolicy are routed by AMSS to the best possible interface
> > using the default netpolicy.  Default netpolicy could be pre-defined
> > or provisioned by the administrator or operator.  Hence default
> > interface could vary from device to device and also depends upon the
> > available networks at any given time.
> > AMSS allows each interface to be configured with its own set of DNS
> > configuration parameters - a list of DNS servers, domain names etc.
> > Interface selected to make a DNS resolution is the one to which
> > application making the DNS query is bound.  Applications can also
> > specify a different netpolicy as part of DNS request to select
> another
> > interface for DNS resolution.  Regardless, all the DNS queries are
> > sent only over this selected interface using the DNS configuration
> > from the interface.   DNS resolution is first attempted with the
> > primary server configured in the interface.  If a response is not
> > received, the queries are sent to all the other servers configured in
> > the interface in a sequential manner using a backoff mechanism.
> > _______________________________________________
> > mif mailing list
> > mif@ietf.org
> > https://www.ietf.org/mailman/listinfo/mif
> >
>=20
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From dwing@cisco.com  Fri Apr  9 14:38:47 2010
Return-Path: <dwing@cisco.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 DF2813A69E1 for <mif@core3.amsl.com>; Fri,  9 Apr 2010 14:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 d4q8dFbpgv48 for <mif@core3.amsl.com>; Fri,  9 Apr 2010 14:38:46 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 8AAFE3A68B3 for <mif@ietf.org>; Fri,  9 Apr 2010 14:38:45 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArUJAFI7v0utJV2c/2dsb2JhbACHWoEUhlOLfnGiFpkbhQkEgyQ
X-IronPort-AV: E=Sophos;i="4.52,179,1270425600"; d="scan'208";a="100532601"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-2.cisco.com with ESMTP; 09 Apr 2010 21:38:40 +0000
Received: from dwingwxp01 (sjc-vpn5-555.cisco.com [10.21.90.43]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id o39LcZoo021403;  Fri, 9 Apr 2010 21:38:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'gabriel montenegro'" <g_e_montenegro@yahoo.com>, "'Hui Deng'" <denghui02@gmail.com>, "'Dave Thaler'" <dthaler@microsoft.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com>
Date: Fri, 9 Apr 2010 14:38:28 -0700
Message-ID: <000201cad82d$053e0900$2b5a150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcrXWHrAmmWI89nZRZWPzCyZ8BIFOgAHmL8A
In-Reply-To: <294720.31470.qm@web82601.mail.mud.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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: Fri, 09 Apr 2010 21:38:48 -0000

> -----Original Message-----
> From: gabriel montenegro [mailto:g_e_montenegro@yahoo.com]=20
> Sent: Thursday, April 08, 2010 1:17 PM
> To: Dan Wing; Hui Deng; Dave Thaler
> Cc: mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>=20
> In addition to those three usages of "suffix":
>=20
> 1. Domain Search list suffix
> 2. For interface-specific suffix list=A0
> 3. Suffix to control Dynamic DNS=A0Updates
>=20
> There is yet another usage in Windows introduced in windows 7=20
> and its server counterpart, Windows Server 2008 R2:
>=20
> 4. Suffix in the NRPT [1] to aid in identifying a Namespace=20
> that requires special handling,=20
> as used for DirectAccess [2]. This is not MIF-specific either.
>
> Only #2 is MIF-specific (and this should be called out), but=20
> it makes sense to clarify the=20
> other uses of "suffix" otherwise #2 won't be clear.

Thanks.

To be concrete, I would suggest text something like this at
the top of the section on draft-ietf-mif-current-practices
describing Windows DNS behavior:

  "Windows uses host name suffixes for four different purposes:
   domain search list suffix (similar to the "domain" entry in
   the standard Unix /etc/resolv.conf file), interface-specific
   suffix list, dynamic DNS updates, and the name resolution
   policy table (NRPT).  It is Windows interface-specific
   suffix list that is described in this section."

and then tighten up the rest of section to only describe that.

-d

> [1] NRPT: See=20
> http://technet.microsoft.com/en-us/magazine/ff394369.aspx
> [2] DirectAcess:=20
> http://technet.microsoft.com/en-us/magazine/2009.05.cableguy.aspx



> Gabriel
>=20
> ----- Original Message ----
> > From: Dan Wing <dwing@cisco.com>
> > To: Hui Deng <denghui02@gmail.com>; Dave Thaler=20
> <dthaler@microsoft.com>
> > Cc: mif@ietf.org; Gabriel Montenegro <gmonte@microsoft.com>
> > Sent: Thu, April 8, 2010 7:22:23 AM
> > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> >=20
> >=20
>=20
> > -----Original Message-----
> > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"=20
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]=20
> > Sent:=20
> > Wednesday, April 07, 2010 7:29 PM
> > To: Dave Thaler
> > Cc: Dan Wing;=20
> > Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > Subject: Re: [mif]=20
> > draft-ietf-mif-current-practices-00
> >=20
> > 2nd purpose has been=20
> > documented in the current practice draft,
> > whether 1st and 3rd purpose=20
> > need to be documented as well? it may not
> > directly related to=20
> > MIF?
>=20
> Some operating systems -- e.g., most flavors of Unix -- do not=20
> > support the
> ability for sending different DNS queries to different DNS=20
> > servers.
>=20
> It would be helpful if the draft more clearly described the=20
> > functionality.
> Someone unfamiliar with the Windows functionality, reading the=20
> > draft, assumes
> it is merely talking about the 'domain search list' -- because=20
> > that is what
> they are familiar with.=A0=20
>=20
> I don't care how the draft=20
> > is fixed to make it clearer.=A0 I propose describing
> the 2 (and, as Dave=20
> > pointed out, 3) functions.=A0 If you want to adjust the
> document to=20
> > instead talk about the per-interface stuff, that's great -- my
> point is that=20
> > right now it is insufficiently clear in explaining it.
>=20
> -d
>=20
> >=20
> > -Hui
> >=20
> > 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com"=20
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
> >=20
> > >> -----Original Message-----
> > >> From: Dan Wing [mailto:> ymailto=3D"mailto:dwing@cisco.com"=20
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
> > >> Sent:=20
> > Tuesday, April 06, 2010 11:52 AM
> > >> To: Dave Thaler; 'Hui Deng';=20
> > Gabriel Montenegro
> > >> Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> Subject: RE: [mif]=20
> > draft-ietf-mif-current-practices-00
> > >>
> > >>
> >=20
> > >>
> > >> > -----Original Message-----
> > >> >=20
> > From: Dave Thaler [mailto:>=20
> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com]
> > >>=20
> > > Sent: Tuesday, April 06, 2010 10:06 AM
> > >> > To: Hui Deng;=20
> > Dan Wing; Gabriel Montenegro
> > >> > Cc: > ymailto=3D"mailto:mif@ietf.org"=20
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > Subject: RE:=20
> > [mif] draft-ietf-mif-current-practices-00
> > >> >
> > >>=20
> > > Hui is correct, Windows has per-interface DNS server lists
> > >>=20
> > configured.
> > >> >
> > >> > It then uses a host-wide=20
> > "effective" server list for an=20
> > actual query,
> > >> >=20
> > where the effective server list may be different for=20
> > different=20
> > names.
> > >> >
> > >> > On Windows the per-interface=20
> > suffix is actually termed the
> > >> > "connection-specific DNS=20
> > suffix" to distinguish it from the
> > >> > "primary DNS suffix" of=20
> > the machine. =A0I think that's why
> > >> > "interface-specific" was=20
> > repeated in the first bullet.
> > >>
> > >>
> >=20
> > >>
> > >> In draft-montenegro-mif-multihoming, there are two=20
> >=20
> > purposes and terms
> > >> that
> > >> seem to be=20
> > intermingled using the term "DNS suffix".
> > >>
> > >> One=20
> > purpose is the suffix for non-FQDN names, like=20
> > "payroll" or=20
> > "mail",
> > >> which will have a suffix added to them (e.g., >=20
> target=3D"_blank" href=3D"http://example.com">example.com).
> > >
> >=20
> > > That's what windows calls the "DNS Suffix Search List" (see the
> >=20
> > > sample output I sent previously below). =A0It's called the
> > >=20
> > "domain search list" in other places (like RFC 3397), or just
> > >=20
> > "search list" (RFC 1123).
> > >
> > >> The
> > >>=20
> > other purpose is deciding which DNS server will be be sent=20
> > a query=20
> > for
> > >> a certain FQDN (e.g., queries for *.>=20
> href=3D"http://example.net">example.net go to one=20
> > DNS server
> >=20
> > >> and queries for *.example.com go to a different DNS server).
> >=20
> > >
> > > Another purpose is deciding which DNS server will receive a=20
> > dynamic
> > > update for a name with a certain suffix (e.g., Windows=20
> >=20
> > supports dynamic
> > > updates for the primary DNS name, and=20
> > optionally also the=20
> > connection-
> > > specific DNS name of the=20
> > machine).
> > >
> > >>
> > >>
> > >> In=20
> > draft-ietf-mif-current-practices-00, which is the WG document
> > >>=20
> > that seems to have boiled down draft-montenegro-mif-multihoming,
> >=20
> > >> but draft-ietf-mif-current-practices-00 also does not clearly
> >=20
> > >> separate the two purposes.
> > >
> > > Yep
> >=20
> > >
> > > -Dave
> > >>
> > >> -d
> >=20
> > >>
> > >>
> > >> > Example on Windows, extracted=20
> > from "ipconfig /all" output:
> > >> >
> > >> > Windows=20
> > IP Configuration
> > >> >
> > >> > =A0 =A0Host Name . . .=20
> > . . . . . . . . . : dthaler-win7
> > >> > =A0 =A0Primary Dns Suffix =A0.=20
> > . . . . . . : >=20
> href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.com
> >=20
> > >> > =A0=20
> > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >>=20
> > > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
> > >> > =A0 =A0IP=20
> > Routing Enabled. . . . . . . . : No
> > >> > =A0 =A0WINS Proxy Enabled.=20
> > . . . . . . . : No
> > >> > =A0 =A0DNS Suffix Search List. . . . . . :=20
> > ntdev.corp.microsoft.com
> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0=20
> > =A0 =A0 =A0>=20
> href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.com
> >=20
> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0>=20
> href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
> > >> >=20
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0>=20
> href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
> > >>=20
> > > =A0 =A0System Quarantine State . . . . . : Not Restricted
> > >>=20
> > >
> > >> > Wireless LAN adapter Wireless Network=20
> > Connection:
> > >> >
> > >> > =A0 =A0Connection-specific=20
> > DNS Suffix =A0. : >=20
> href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.
> > >> >=20
> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >>=20
> > > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> >=20
> > >> > Link 4965AGN
> > >> > =A0 =A0Physical Address. . . . . .=20
> > . . . : 00-1D-E0-34-4F-6F
> > >> > =A0 =A0DHCP Enabled. . . . . . . . .=20
> > . . : Yes
> > >> > =A0 =A0Autoconfiguration Enabled . . . . :=20
> > Yes
> > >> > =A0 =A0Link-local IPv6 Address . . . . . :
> >=20
> > >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> > >> > =A0=20
> > =A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> > >>=20
> > > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > >> >=20
> > =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> > >>=20
> > > 10:19:02 PM
> > >> > =A0 =A0Lease Expires . . . . . . . . . . :=20
> > Tuesday, April 06,
> > >> > 2010 10:19:02 PM
> > >> >=20
> > =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
> > >> > =A0 =A0DHCP=20
> > Server . . . . . . . . . . . : 192.168.0.1
> > >> > =A0 =A0DHCPv6 IAID=20
> > . . . . . . . . . . . : 335551968
> > >> > =A0 =A0DHCPv6 Client DUID. .=20
> > . . . . . . :
> > >> >=20
> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> > >> >
> > >>=20
> > > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> > >>=20
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0192.168.0.1
> > >> > =A0=20
> > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >> > =A0=20
> > =A0NetBIOS over Tcpip. . . . . . . . : Enabled
> > >> >
> >=20
> > >> > -Dave
> > >> >
> > >> > >=20
> > -----Original Message-----
> > >> > > From: Hui Deng [mailto:>=20
> ymailto=3D"mailto:denghui02@gmail.com"=20
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > >> >=20
> > > Sent: Monday, April 05, 2010 7:40 PM
> > >> > > To: Dan=20
> > Wing; Gabriel Montenegro; Dave Thaler
> > >> > > Cc: > ymailto=3D"mailto:mif@ietf.org"=20
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > > Subject:=20
> > Re: [mif] draft-ietf-mif-current-practices-00
> > >> > >
> >=20
> > >> > > DNS server always has specific interface related=20
> > information,
> > >> > > but the final DNS server will still be=20
> > host based, I=20
> > wouldn't say
> > >> it
> > >> >=20
> > > is not correct.
> > >> > >
> > >> > > one=20
> > example would be you have internet connection and vpn
> > >>=20
> > connection
> > >> > > at the same time,
> > >> >=20
> > > good VPN implementation will always rely on VPN DNS server
> > >>=20
> > > information
> > >> > > for Internet connection.
> >=20
> > >> > >
> > >> > > -Hui
> > >> >=20
> > >
> > >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"=20
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
> > >> >=20
> > > > Section 3.2.1.3 of describes the DNS configuration=20
> > of=20
> > Windows,
> > >> and
> > >> > > says:
> > >>=20
> > > > >
> > >> > > > =A0"Interface specific DNS=20
> > configuration can be input=20
> > via static
> > >> > > > =A0=20
> > configuration or via DHCP. =A0It includes:
> > >> > > >
> >=20
> > >> > > > =A0 o =A0An interface-specific suffix list.
> > >>=20
> > > > >
> > >> > > > =A0 o =A0A list of DNS server IP=20
> > addresses."
> > >> > > >
> > >> > > > It=20
> > is curious that the first bullet repeats "interface
> > >> >=20
> > specific", but
> > >> > > the
> > >> > > >=20
> > second bullet does not repeat it. =A0A reasonable=20
> > interpretation=20
> > is
> > >> > > that the
> > >> > > > second=20
> > bullet is not interface-specific, but the=20
> > lead-in sentence
> >=20
> > >> > > says this is
> > >> > > >=20
> > interface-specific. =A0I was hoping
> > >> >=20
> > draft-montenegro-mif-multihoming-00
> > >> > > would
> >=20
> > >> > > > clarify, but it doesn't.
> > >> > >=20
> > >
> > >> > > > -d
> > >> > > >
> >=20
> > >> > > > _______________________________________________
> >=20
> > >> > > > mif mailing list
> > >> > > > > ymailto=3D"mailto:mif@ietf.org"=20
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > > > > href=3D"https://www.ietf.org/mailman/listinfo/mif"=20
> target=3D_blank=20
> > >https://www.ietf.org/mailman/listinfo/mif
> > >> > >=20
> > >
> > >> >
> > >>
> > >
> >=20
> > >
>=20
> _______________________________________________
> mif mailing=20
> > list
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank=20
> > >https://www.ietf.org/mailman/listinfo/mif


From denghui02@gmail.com  Sat Apr 10 05:58:07 2010
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 EA5343A68AF for <mif@core3.amsl.com>; Sat, 10 Apr 2010 05:58:07 -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 K36WQQG0Fsb3 for <mif@core3.amsl.com>; Sat, 10 Apr 2010 05:58:06 -0700 (PDT)
Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by core3.amsl.com (Postfix) with ESMTP id C6C0E3A6882 for <mif@ietf.org>; Sat, 10 Apr 2010 05:58:06 -0700 (PDT)
Received: by iwn27 with SMTP id 27so3228816iwn.5 for <mif@ietf.org>; Sat, 10 Apr 2010 05:57:57 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tp9wosCDV5q442D1H05MfrEC860wi7R+lzKn52N94lw=; b=UmLCqDDhPWS6PorHuzUzFNrEZSHTLr7oD5pGq02sOwOtTpO7P/CaYEiTtP+3j4G7Zp 5LAVNmJjJwciNXR+/XQhlPZbI7WhpHnhyjxA43yHykNgA5L89RQPBaFj8d52EwKn/mrl ut3YHmTNYkdoRiwKtJWexpD4uI9i+fssZ6wv4=
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=S8X7RINO/+p1uJGbhDzFWXVJGBy0C1xTbpoR0BGixrrID3Ple9bts80H/9vEoxIhUu i19w91QA7Z5pTCqRyndCeNkDlz9l+D6Ib4iDvnZ4EoI0Gcz9qXpssDVYUrToasCR72++ vzhhtiXfeLCzWCNqsrEUBczktJMF/erfi8PUc=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Sat, 10 Apr 2010 05:57:56 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com>
Date: Sat, 10 Apr 2010 20:57:56 +0800
Received: by 10.231.161.12 with SMTP id p12mr649812ibx.31.1270904277035; Sat,  10 Apr 2010 05:57:57 -0700 (PDT)
Message-ID: <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>, Margaret Wasserman <mrw@sandstorm.net>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 10 Apr 2010 12:58:08 -0000

Hi Julien

As I asked the question yesterday,
it is expected that Qualcomm has more detail clarification about the text,

Regards,

-Hui


2010/4/10 Laganier, Julien <julienl@qualcomm.com>:
> Hi Margaret -
>
> I notice this text is not included in the current rev. of the current pra=
ctice draft. Are you going to include it?
>
> Thanks.
>
> --julien
>
>> -----Original Message-----
>> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
>> Margaret Wasserman
>> Sent: Sunday, August 16, 2009 7:04 AM
>> To: George Tsirtsis
>> Cc: mif
>> Subject: Re: [mif] AMSS/Brew Multi-interface handling
>>
>>
>> Hi George,
>>
>> Thanks for sending this!
>>
>> I'll add it to the next version of the draft.
>>
>> Margaret
>>
>> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
>>
>> > Hi all,
>> >
>> > I sent this to Margaret during the IETF meeting but I did not hear
>> > back from her. Maybe it got lost in the IETF noise so I thought I
>> > might as well forward this to the list.
>> >
>> > I hope it helps.
>> >
>> > George
>> >
>> > ---------- Forwarded message ----------
>> > From: George Tsirtsis <tsirtsis@googlemail.com>
>> > Date: Wed, Jul 29, 2009 at 9:58 AM
>> > Subject: AMSS/Brew Multi-interface handling
>> > To: mrw@sandstorm.net
>> >
>> >
>> > Hi Margaret,
>> >
>> > Here is a description of how multi-interface support is handled by
>> > Advanced Mobile Station Software (AMSS) that comes with Brew OS for
>> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
>> > helpful information for draft-mrw-mif-current-practices.
>> >
>> > Let me know if you have any questions.
>> >
>> > Regards
>> > George Tsirtsis (wearing a Qualcomm hat)
>> >
>> > ---------------------------------------------------------------------
>> --------------------------------
>> >
>> >
>> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
>> >
>> > AMSS supports a concept of "netpolicy" which allows each application
>> > to specify the type of network connectivity desired. =A0The netpolicy
>> > contains parameters such as access technology, IP version type and
>> > network profile. =A0Access technology could be a specific technology
>> > type such as CDMA or WiFi or could be a group of technologies, such
>> as
>> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4, Ipv6
>> > or Default. =A0The network profile identifies a type of network domain
>> > or service within a certain network technology, such as 3GPP APN or
>> > Mobile IP Home Agent. =A0It also specifies all the mandatory parameter=
s
>> > required to connect to the domain such authentication credentials and
>> > other optional parameters such as QoS attributes. =A0Network Profile i=
s
>> > technology specific and set of parameters contained in the profile
>> > could vary for different technologies.
>> >
>> > Two models of network usage are supported.
>> >
>> > Applications requiring network connectivity specify an appropriate
>> > netpolicy in order to select the desired network. =A0The netpolicy may
>> > match one or more network interfaces. =A0AMSS system selection module
>> > selects the best interface out of the ones that match the netpolicy
>> > based on various criteria such as cost, speed or other provisioned
>> > rules. =A0Application explicitly starts the selected network interface
>> > and, as a result, the application also gets bound to the
>> corresponding
>> > network interface. =A0All outbound packets from this application are
>> > always routed over this bound interface using the source address of
>> > the interface.
>> > Alternately, applications may rely on a separate connection manager
>> to
>> > control (start/stop) the network interface. =A0 =A0In this method,
>> > applications are not necessarily bound to any one interface. =A0All
>> > outbound packets from such applications are routed on one of the
>> > interfaces that match its netpolicy. =A0The routing decision is made
>> > individually for each packet and =A0selects the best interface based o=
n
>> > the criteria described above and the destination address. =A0 Source
>> > address is always that assigned to the interface used to transmit the
>> > packet.
>> >
>> > Note that all of the routing/interface selection decisions are based
>> > on the netpolicy and not just destination address to avoid
>> overlapping
>> > private Ipv4 address issue. =A0This also allows multiple (logical)
>> > interfaces to be configured with the same IP address, for example, to
>> > handle certain tunnelling scenarios. =A0 Applications that do not
>> > specify a netpolicy are routed by AMSS to the best possible interface
>> > using the default netpolicy. =A0Default netpolicy could be pre-defined
>> > or provisioned by the administrator or operator. =A0Hence default
>> > interface could vary from device to device and also depends upon the
>> > available networks at any given time.
>> > AMSS allows each interface to be configured with its own set of DNS
>> > configuration parameters - a list of DNS servers, domain names etc.
>> > Interface selected to make a DNS resolution is the one to which
>> > application making the DNS query is bound. =A0Applications can also
>> > specify a different netpolicy as part of DNS request to select
>> another
>> > interface for DNS resolution. =A0Regardless, all the DNS queries are
>> > sent only over this selected interface using the DNS configuration
>> > from the interface. =A0 DNS resolution is first attempted with the
>> > primary server configured in the interface. =A0If a response is not
>> > received, the queries are sent to all the other servers configured in
>> > the interface in a sequential manner using a backoff mechanism.
>> > _______________________________________________
>> > mif mailing list
>> > mif@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mif
>> >
>>
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>

From teemu.savolainen@nokia.com  Mon Apr 12 13:53:41 2010
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 D9A403A685B for <mif@core3.amsl.com>; Mon, 12 Apr 2010 13:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.298
X-Spam-Level: 
X-Spam-Status: No, score=-5.298 tagged_above=-999 required=5 tests=[AWL=-1.299, BAYES_50=0.001, 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 YF5Doc6md-XQ for <mif@core3.amsl.com>; Mon, 12 Apr 2010 13:53:40 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id CE7793A6AB2 for <mif@ietf.org>; Mon, 12 Apr 2010 13:53:37 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o3CKrIhS024100; Mon, 12 Apr 2010 23:53:23 +0300
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 12 Apr 2010 23:53:07 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 12 Apr 2010 23:53:03 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 12 Apr 2010 23:52:58 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Mon, 12 Apr 2010 22:52:57 +0200
From: <teemu.savolainen@nokia.com>
To: <g_e_montenegro@yahoo.com>, <dwing@cisco.com>, <denghui02@gmail.com>, <dthaler@microsoft.com>
Date: Mon, 12 Apr 2010 22:52:55 +0200
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AcrXWIT9GSntcfe7TNW7iViuVK9clgDKFcmg
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com>
In-Reply-To: <294720.31470.qm@web82601.mail.mud.yahoo.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: 12 Apr 2010 20:52:58.0640 (UTC) FILETIME=[221CD900:01CADA82]
X-Nokia-AV: Clean
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 12 Apr 2010 20:53:42 -0000

Hi,

Why do you think #4 is not mif-specific? What possible use NRPT has for sin=
gle interfaced host? Or is the idea such that a host could have single inte=
rface, but just use different DNS server for queries matching NRPT?
....hmm...
Do you consider a host using DirectAccess single or multi-interfaced? From =
my quick reading of the DirectAccess feature, it sounds to be somewhere in =
between - not obviously multi-interface like the VPN-case is, but not quite=
 single-interfaced either.=20

Is there a way to configure NRPT policies remotely via some protocol?

Thanks for explanation,

Teemu

> -----Original Message-----
> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> ext gabriel montenegro
> Sent: 08. huhtikuuta 2010 23:17
> To: Dan Wing; Hui Deng; Dave Thaler
> Cc: mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>=20
> In addition to those three usages of "suffix":
>=20
> 1. Domain Search list suffix
> 2. For interface-specific suffix list
> 3. Suffix to control Dynamic DNS=A0Updates
>=20
> There is yet another usage in Windows introduced in windows 7 and its
> server counterpart, Windows Server 2008 R2:
>=20
> 4. Suffix in the NRPT [1] to aid in identifying a Namespace that
> requires special handling,
> as used for DirectAccess [2]. This is not MIF-specific either.
>=20
> Only #2 is MIF-specific (and this should be called out), but it makes
> sense to clarify the
> other uses of "suffix" otherwise #2 won't be clear.
>=20
> [1] NRPT: See http://technet.microsoft.com/en-us/magazine/ff394369.aspx
> [2] DirectAcess: http://technet.microsoft.com/en-
> us/magazine/2009.05.cableguy.aspx
>=20
> Gabriel
>=20
> ----- Original Message ----
> > From: Dan Wing <dwing@cisco.com>
> > To: Hui Deng <denghui02@gmail.com>; Dave Thaler
> <dthaler@microsoft.com>
> > Cc: mif@ietf.org; Gabriel Montenegro <gmonte@microsoft.com>
> > Sent: Thu, April 8, 2010 7:22:23 AM
> > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> >
> >
>=20
> > -----Original Message-----
> > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > Sent:
> > Wednesday, April 07, 2010 7:29 PM
> > To: Dave Thaler
> > Cc: Dan Wing;
> > Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > Subject: Re: [mif]
> > draft-ietf-mif-current-practices-00
> >
> > 2nd purpose has been
> > documented in the current practice draft,
> > whether 1st and 3rd purpose
> > need to be documented as well? it may not
> > directly related to
> > MIF?
>=20
> Some operating systems -- e.g., most flavors of Unix -- do not
> > support the
> ability for sending different DNS queries to different DNS
> > servers.
>=20
> It would be helpful if the draft more clearly described the
> > functionality.
> Someone unfamiliar with the Windows functionality, reading the
> > draft, assumes
> it is merely talking about the 'domain search list' -- because
> > that is what
> they are familiar with.
>=20
> I don't care how the draft
> > is fixed to make it clearer.=A0 I propose describing
> the 2 (and, as Dave
> > pointed out, 3) functions.=A0 If you want to adjust the
> document to
> > instead talk about the per-interface stuff, that's great -- my
> point is that
> > right now it is insufficiently clear in explaining it.
>=20
> -d
>=20
> >
> > -Hui
> >
> > 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com"
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
> >
> > >> -----Original Message-----
> > >> From: Dan Wing [mailto:> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
> > >> Sent:
> > Tuesday, April 06, 2010 11:52 AM
> > >> To: Dave Thaler; 'Hui Deng';
> > Gabriel Montenegro
> > >> Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> Subject: RE: [mif]
> > draft-ietf-mif-current-practices-00
> > >>
> > >>
> >
> > >>
> > >> > -----Original Message-----
> > >> >
> > From: Dave Thaler [mailto:>
> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com]
> > >>
> > > Sent: Tuesday, April 06, 2010 10:06 AM
> > >> > To: Hui Deng;
> > Dan Wing; Gabriel Montenegro
> > >> > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > Subject: RE:
> > [mif] draft-ietf-mif-current-practices-00
> > >> >
> > >>
> > > Hui is correct, Windows has per-interface DNS server lists
> > >>
> > configured.
> > >> >
> > >> > It then uses a host-wide
> > "effective" server list for an
> > actual query,
> > >> >
> > where the effective server list may be different for
> > different
> > names.
> > >> >
> > >> > On Windows the per-interface
> > suffix is actually termed the
> > >> > "connection-specific DNS
> > suffix" to distinguish it from the
> > >> > "primary DNS suffix" of
> > the machine. =A0I think that's why
> > >> > "interface-specific" was
> > repeated in the first bullet.
> > >>
> > >>
> >
> > >>
> > >> In draft-montenegro-mif-multihoming, there are two
> >
> > purposes and terms
> > >> that
> > >> seem to be
> > intermingled using the term "DNS suffix".
> > >>
> > >> One
> > purpose is the suffix for non-FQDN names, like
> > "payroll" or
> > "mail",
> > >> which will have a suffix added to them (e.g., > target=3D"_blank"
> href=3D"http://example.com">example.com).
> > >
> >
> > > That's what windows calls the "DNS Suffix Search List" (see the
> >
> > > sample output I sent previously below). =A0It's called the
> > >
> > "domain search list" in other places (like RFC 3397), or just
> > >
> > "search list" (RFC 1123).
> > >
> > >> The
> > >>
> > other purpose is deciding which DNS server will be be sent
> > a query
> > for
> > >> a certain FQDN (e.g., queries for *.>
> href=3D"http://example.net">example.net go to one
> > DNS server
> >
> > >> and queries for *.example.com go to a different DNS server).
> >
> > >
> > > Another purpose is deciding which DNS server will receive a
> > dynamic
> > > update for a name with a certain suffix (e.g., Windows
> >
> > supports dynamic
> > > updates for the primary DNS name, and
> > optionally also the
> > connection-
> > > specific DNS name of the
> > machine).
> > >
> > >>
> > >>
> > >> In
> > draft-ietf-mif-current-practices-00, which is the WG document
> > >>
> > that seems to have boiled down draft-montenegro-mif-multihoming,
> >
> > >> but draft-ietf-mif-current-practices-00 also does not clearly
> >
> > >> separate the two purposes.
> > >
> > > Yep
> >
> > >
> > > -Dave
> > >>
> > >> -d
> >
> > >>
> > >>
> > >> > Example on Windows, extracted
> > from "ipconfig /all" output:
> > >> >
> > >> > Windows
> > IP Configuration
> > >> >
> > >> > =A0 =A0Host Name . . .
> > . . . . . . . . . : dthaler-win7
> > >> > =A0 =A0Primary Dns Suffix =A0.
> > . . . . . . : >
> href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.com
> >
> > >> >
> > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >>
> > > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
> > >> > =A0 =A0IP
> > Routing Enabled. . . . . . . . : No
> > >> > =A0 =A0WINS Proxy Enabled.
> > . . . . . . . : No
> > >> > =A0 =A0DNS Suffix Search List. . . . . . :
> > ntdev.corp.microsoft.com
> > >> >
> > =A0 =A0 =A0>
> href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.com
> >
> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0>
> href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
> > >> >
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0>
> href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
> > >>
> > > =A0 =A0System Quarantine State . . . . . : Not Restricted
> > >>
> > >
> > >> > Wireless LAN adapter Wireless Network
> > Connection:
> > >> >
> > >> > =A0 =A0Connection-specific
> > DNS Suffix =A0. : >
> href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.
> > >> >
> > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >>
> > > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> >
> > >> > Link 4965AGN
> > >> > =A0 =A0Physical Address. . . . . .
> > . . . : 00-1D-E0-34-4F-6F
> > >> > =A0 =A0DHCP Enabled. . . . . . . . .
> > . . : Yes
> > >> > =A0 =A0Autoconfiguration Enabled . . . . :
> > Yes
> > >> > =A0 =A0Link-local IPv6 Address . . . . . :
> >
> > >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> > >> >
> > =A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> > >>
> > > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > >> >
> > =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> > >>
> > > 10:19:02 PM
> > >> > =A0 =A0Lease Expires . . . . . . . . . . :
> > Tuesday, April 06,
> > >> > 2010 10:19:02 PM
> > >> >
> > =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
> > >> > =A0 =A0DHCP
> > Server . . . . . . . . . . . : 192.168.0.1
> > >> > =A0 =A0DHCPv6 IAID
> > . . . . . . . . . . . : 335551968
> > >> > =A0 =A0DHCPv6 Client DUID. .
> > . . . . . . :
> > >> >
> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> > >> >
> > >>
> > > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> > >>
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0192.168.0.1
> > >> >
> > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >> >
> > =A0NetBIOS over Tcpip. . . . . . . . : Enabled
> > >> >
> >
> > >> > -Dave
> > >> >
> > >> > >
> > -----Original Message-----
> > >> > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > >> >
> > > Sent: Monday, April 05, 2010 7:40 PM
> > >> > > To: Dan
> > Wing; Gabriel Montenegro; Dave Thaler
> > >> > > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > > Subject:
> > Re: [mif] draft-ietf-mif-current-practices-00
> > >> > >
> >
> > >> > > DNS server always has specific interface related
> > information,
> > >> > > but the final DNS server will still be
> > host based, I
> > wouldn't say
> > >> it
> > >> >
> > > is not correct.
> > >> > >
> > >> > > one
> > example would be you have internet connection and vpn
> > >>
> > connection
> > >> > > at the same time,
> > >> >
> > > good VPN implementation will always rely on VPN DNS server
> > >>
> > > information
> > >> > > for Internet connection.
> >
> > >> > >
> > >> > > -Hui
> > >> >
> > >
> > >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
> > >> >
> > > > Section 3.2.1.3 of describes the DNS configuration
> > of
> > Windows,
> > >> and
> > >> > > says:
> > >>
> > > > >
> > >> > > > =A0"Interface specific DNS
> > configuration can be input
> > via static
> > >> > > >
> > configuration or via DHCP. =A0It includes:
> > >> > > >
> >
> > >> > > > =A0 o =A0An interface-specific suffix list.
> > >>
> > > > >
> > >> > > > =A0 o =A0A list of DNS server IP
> > addresses."
> > >> > > >
> > >> > > > It
> > is curious that the first bullet repeats "interface
> > >> >
> > specific", but
> > >> > > the
> > >> > > >
> > second bullet does not repeat it. =A0A reasonable
> > interpretation
> > is
> > >> > > that the
> > >> > > > second
> > bullet is not interface-specific, but the
> > lead-in sentence
> >
> > >> > > says this is
> > >> > > >
> > interface-specific. =A0I was hoping
> > >> >
> > draft-montenegro-mif-multihoming-00
> > >> > > would
> >
> > >> > > > clarify, but it doesn't.
> > >> > >
> > >
> > >> > > > -d
> > >> > > >
> >
> > >> > > > _______________________________________________
> >
> > >> > > > mif mailing list
> > >> > > > > ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > >> > > > > href=3D"https://www.ietf.org/mailman/listinfo/mif"
> target=3D_blank
> > >https://www.ietf.org/mailman/listinfo/mif
> > >> > >
> > >
> > >> >
> > >>
> > >
> >
> > >
>=20
> _______________________________________________
> mif mailing
> > list
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
> > >https://www.ietf.org/mailman/listinfo/mif
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From julienl@qualcomm.com  Mon Apr 12 14:21:45 2010
Return-Path: <julienl@qualcomm.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 1EB6628C19A for <mif@core3.amsl.com>; Mon, 12 Apr 2010 14:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.636
X-Spam-Level: 
X-Spam-Status: No, score=-105.636 tagged_above=-999 required=5 tests=[AWL=-0.896, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 HLDalWqpt8Xu for <mif@core3.amsl.com>; Mon, 12 Apr 2010 14:21:42 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 786E328C1CC for <mif@ietf.org>; Mon, 12 Apr 2010 14:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1271107203; x=1302643203; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Hui=20Deng=20<denghui02@gmail.com>|CC:=20Margaret =20Wasserman=20<mrw@sandstorm.net>,=20George=20Tsirtsis =0D=0A=09<tsirtsis@googlemail.com>,=20mif=20<mif@ietf.org >|Date:=20Mon,=2012=20Apr=202010=2014:20:00=20-0700 |Subject:=20RE:=20[mif]=20AMSS/Brew=20Multi-interface=20h andling|Thread-Topic:=20[mif]=20AMSS/Brew=20Multi-interfa ce=20handling|Thread-Index:=20AcrYrXwAde9npnm7TLCPinGsmvC S+QB2C7ig|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F 1C6AB47E4F@NALASEXMB04.na.qualcomm.com>|References:=20<d3 886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com >=0D=0A=09=20<d3886a520908160241k52ede41bpad57325a1c741f3 b@mail.gmail.com>=0D=0A=09=20<424FB149-AE77-4F63-9C18-EF0 4B2A20937@sandstorm.net>=0D=0A=09=20<BF345F63074F8040B58C 00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com>=0D=0A =20<s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail. gmail.com>|In-Reply-To:=20<s2u1d38a3351004100557i3b4b7027 r395b6e306ced299a@mail.gmail.com>|Accept-Language:=20en-U S|Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"iso-8859-1" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=dkvA2NSvANWQE3Uf6cnieizN2Kkz5mgcj3KP9Ts6/Fs=; b=x9mabFXTBZqJBrgA39VJ0P89Yq0yZzXKpC7P6vd1HDZjdx7yM7W7UVPG nvDvRoN2p09GLFTYw5xOs91yKLRrMRrZnVo5Pku3gANvOjtfKYb3HSwpB XOg5qBQ3JiCB+4NI0ZWyJthTpjXWsj4WiARRbGryMKIGPj4xqQM1kMALj s=;
X-IronPort-AV: E=McAfee;i="5400,1158,5949"; a="38536825"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine02.qualcomm.com with ESMTP; 12 Apr 2010 14:20:03 -0700
X-IronPort-AV: E=Sophos;i="4.52,192,1270450800"; d="scan'208";a="13054779"
Received: from nasanexhub05.na.qualcomm.com ([129.46.134.219]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 12 Apr 2010 14:20:02 -0700
Received: from nalasexhub04.na.qualcomm.com (10.47.130.55) by nasanexhub05.na.qualcomm.com (129.46.134.219) with Microsoft SMTP Server (TLS) id 8.2.234.1; Mon, 12 Apr 2010 14:20:01 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhub04.na.qualcomm.com ([10.47.130.55]) with mapi; Mon, 12 Apr 2010 14:20:01 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Hui Deng <denghui02@gmail.com>
Date: Mon, 12 Apr 2010 14:20:00 -0700
Thread-Topic: [mif] AMSS/Brew Multi-interface handling
Thread-Index: AcrYrXwAde9npnm7TLCPinGsmvCS+QB2C7ig
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AB47E4F@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com> <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail.gmail.com>
In-Reply-To: <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mif <mif@ietf.org>, Margaret Wasserman <mrw@sandstorm.net>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 12 Apr 2010 21:21:45 -0000

Hi Hui,

I do not understand what is meant here. Can you clarify?

Thanks.

--julien

Hui Deng wrote:
>=20
> Hi Julien
>=20
> As I asked the question yesterday,
> it is expected that Qualcomm has more detail clarification about the
> text,
>=20
> Regards,
>=20
> -Hui
>=20
>=20
> 2010/4/10 Laganier, Julien <julienl@qualcomm.com>:
> > Hi Margaret -
> >
> > I notice this text is not included in the current rev. of the current
> practice draft. Are you going to include it?
> >
> > Thanks.
> >
> > --julien
> >
> >> -----Original Message-----
> >> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf
> Of
> >> Margaret Wasserman
> >> Sent: Sunday, August 16, 2009 7:04 AM
> >> To: George Tsirtsis
> >> Cc: mif
> >> Subject: Re: [mif] AMSS/Brew Multi-interface handling
> >>
> >>
> >> Hi George,
> >>
> >> Thanks for sending this!
> >>
> >> I'll add it to the next version of the draft.
> >>
> >> Margaret
> >>
> >> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
> >>
> >> > Hi all,
> >> >
> >> > I sent this to Margaret during the IETF meeting but I did not hear
> >> > back from her. Maybe it got lost in the IETF noise so I thought I
> >> > might as well forward this to the list.
> >> >
> >> > I hope it helps.
> >> >
> >> > George
> >> >
> >> > ---------- Forwarded message ----------
> >> > From: George Tsirtsis <tsirtsis@googlemail.com>
> >> > Date: Wed, Jul 29, 2009 at 9:58 AM
> >> > Subject: AMSS/Brew Multi-interface handling
> >> > To: mrw@sandstorm.net
> >> >
> >> >
> >> > Hi Margaret,
> >> >
> >> > Here is a description of how multi-interface support is handled by
> >> > Advanced Mobile Station Software (AMSS) that comes with Brew OS
> for
> >> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
> >> > helpful information for draft-mrw-mif-current-practices.
> >> >
> >> > Let me know if you have any questions.
> >> >
> >> > Regards
> >> > George Tsirtsis (wearing a Qualcomm hat)
> >> >
> >> > ------------------------------------------------------------------
> ---
> >> --------------------------------
> >> >
> >> >
> >> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
> >> >
> >> > AMSS supports a concept of "netpolicy" which allows each
> application
> >> > to specify the type of network connectivity desired. =A0The
> netpolicy
> >> > contains parameters such as access technology, IP version type and
> >> > network profile. =A0Access technology could be a specific technology
> >> > type such as CDMA or WiFi or could be a group of technologies,
> such
> >> as
> >> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4,
> Ipv6
> >> > or Default. =A0The network profile identifies a type of network
> domain
> >> > or service within a certain network technology, such as 3GPP APN
> or
> >> > Mobile IP Home Agent. =A0It also specifies all the mandatory
> parameters
> >> > required to connect to the domain such authentication credentials
> and
> >> > other optional parameters such as QoS attributes. =A0Network Profile
> is
> >> > technology specific and set of parameters contained in the profile
> >> > could vary for different technologies.
> >> >
> >> > Two models of network usage are supported.
> >> >
> >> > Applications requiring network connectivity specify an appropriate
> >> > netpolicy in order to select the desired network. =A0The netpolicy
> may
> >> > match one or more network interfaces. =A0AMSS system selection
> module
> >> > selects the best interface out of the ones that match the
> netpolicy
> >> > based on various criteria such as cost, speed or other provisioned
> >> > rules. =A0Application explicitly starts the selected network
> interface
> >> > and, as a result, the application also gets bound to the
> >> corresponding
> >> > network interface. =A0All outbound packets from this application are
> >> > always routed over this bound interface using the source address
> of
> >> > the interface.
> >> > Alternately, applications may rely on a separate connection
> manager
> >> to
> >> > control (start/stop) the network interface. =A0 =A0In this method,
> >> > applications are not necessarily bound to any one interface. =A0All
> >> > outbound packets from such applications are routed on one of the
> >> > interfaces that match its netpolicy. =A0The routing decision is made
> >> > individually for each packet and =A0selects the best interface based
> on
> >> > the criteria described above and the destination address. =A0 Source
> >> > address is always that assigned to the interface used to transmit
> the
> >> > packet.
> >> >
> >> > Note that all of the routing/interface selection decisions are
> based
> >> > on the netpolicy and not just destination address to avoid
> >> overlapping
> >> > private Ipv4 address issue. =A0This also allows multiple (logical)
> >> > interfaces to be configured with the same IP address, for example,
> to
> >> > handle certain tunnelling scenarios. =A0 Applications that do not
> >> > specify a netpolicy are routed by AMSS to the best possible
> interface
> >> > using the default netpolicy. =A0Default netpolicy could be pre-
> defined
> >> > or provisioned by the administrator or operator. =A0Hence default
> >> > interface could vary from device to device and also depends upon
> the
> >> > available networks at any given time.
> >> > AMSS allows each interface to be configured with its own set of
> DNS
> >> > configuration parameters - a list of DNS servers, domain names etc.
> >> > Interface selected to make a DNS resolution is the one to which
> >> > application making the DNS query is bound. =A0Applications can also
> >> > specify a different netpolicy as part of DNS request to select
> >> another
> >> > interface for DNS resolution. =A0Regardless, all the DNS queries are
> >> > sent only over this selected interface using the DNS configuration
> >> > from the interface. =A0 DNS resolution is first attempted with the
> >> > primary server configured in the interface. =A0If a response is not
> >> > received, the queries are sent to all the other servers configured
> in
> >> > the interface in a sequential manner using a backoff mechanism.
> >> > _______________________________________________
> >> > mif mailing list
> >> > mif@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/mif
> >> >
> >>
> >> _______________________________________________
> >> mif mailing list
> >> mif@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mif
> > _______________________________________________
> > mif mailing list
> > mif@ietf.org
> > https://www.ietf.org/mailman/listinfo/mif
> >

From dthaler@microsoft.com  Mon Apr 12 15:43:30 2010
Return-Path: <dthaler@microsoft.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 D0AEE3A696F for <mif@core3.amsl.com>; Mon, 12 Apr 2010 15:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.689
X-Spam-Level: 
X-Spam-Status: No, score=-109.689 tagged_above=-999 required=5 tests=[AWL=0.910, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Nb0MRnDN6wTy for <mif@core3.amsl.com>; Mon, 12 Apr 2010 15:43:29 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id AC74B3A68CB for <mif@ietf.org>; Mon, 12 Apr 2010 15:43:27 -0700 (PDT)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 12 Apr 2010 15:43:21 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 12 Apr 2010 15:43:21 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.63]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Mon, 12 Apr 2010 15:43:21 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>, "g_e_montenegro@yahoo.com" <g_e_montenegro@yahoo.com>, "dwing@cisco.com" <dwing@cisco.com>, "denghui02@gmail.com" <denghui02@gmail.com>
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AQHK1TKMaTaZ5uEk9UKBxenwZvGT9pIVqnJAgAAdoSCAAA5RwIACev8AgADHYICAAGMjgIAGU02A//+oG2A=
Date: Mon, 12 Apr 2010 22:43:04 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF65139303B3@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com> <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 12 Apr 2010 22:43:30 -0000

> -----Original Message-----
> From: teemu.savolainen@nokia.com [mailto:teemu.savolainen@nokia.com]
> Sent: Monday, April 12, 2010 1:53 PM
> To: g_e_montenegro@yahoo.com; dwing@cisco.com; denghui02@gmail.com; Dave
> Thaler
> Cc: mif@ietf.org
> Subject: RE: [mif] draft-ietf-mif-current-practices-00
>=20
> Hi,
>=20
> Why do you think #4 is not mif-specific? What possible use NRPT has for s=
ingle
> interfaced host? Or is the idea such that a host could have single interf=
ace,
> but just use different DNS server for queries matching NRPT?

Right.  The NRPT is similar to a configured cache of NS records.
It's used to solve the problem of have access to multiple disjoint namespac=
es
(like corporate DNS and public DNS).  Private names aren't resolvable in
the public DNS, so you have to know what DNS server to ask.

> ....hmm...
> Do you consider a host using DirectAccess single or multi-interfaced? Fro=
m my
> quick reading of the DirectAccess feature, it sounds to be somewhere in
> between - not obviously multi-interface like the VPN-case is, but not qui=
te
> single-interfaced either.

Right it could be either one.

>=20
> Is there a way to configure NRPT policies remotely via some protocol?

Yes, it's designed to be configured by an enterprise administrator of the
organization that manages the host.  So there's an authenticated,=20
configuration distribution protocol for ActiveDirectory-domain-joined hosts=
.

-Dave

>=20
> Thanks for explanation,
>=20
> Teemu
>=20
> > -----Original Message-----
> > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> > ext gabriel montenegro
> > Sent: 08. huhtikuuta 2010 23:17
> > To: Dan Wing; Hui Deng; Dave Thaler
> > Cc: mif@ietf.org
> > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> >
> > In addition to those three usages of "suffix":
> >
> > 1. Domain Search list suffix
> > 2. For interface-specific suffix list
> > 3. Suffix to control Dynamic DNS=A0Updates
> >
> > There is yet another usage in Windows introduced in windows 7 and its
> > server counterpart, Windows Server 2008 R2:
> >
> > 4. Suffix in the NRPT [1] to aid in identifying a Namespace that
> > requires special handling,
> > as used for DirectAccess [2]. This is not MIF-specific either.
> >
> > Only #2 is MIF-specific (and this should be called out), but it makes
> > sense to clarify the
> > other uses of "suffix" otherwise #2 won't be clear.
> >
> > [1] NRPT: See http://technet.microsoft.com/en-us/magazine/ff394369.aspx
> > [2] DirectAcess: http://technet.microsoft.com/en-
> > us/magazine/2009.05.cableguy.aspx
> >
> > Gabriel
> >
> > ----- Original Message ----
> > > From: Dan Wing <dwing@cisco.com>
> > > To: Hui Deng <denghui02@gmail.com>; Dave Thaler
> > <dthaler@microsoft.com>
> > > Cc: mif@ietf.org; Gabriel Montenegro <gmonte@microsoft.com>
> > > Sent: Thu, April 8, 2010 7:22:23 AM
> > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> > >
> > >
> >
> > > -----Original Message-----
> > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
> > > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > > Sent:
> > > Wednesday, April 07, 2010 7:29 PM
> > > To: Dave Thaler
> > > Cc: Dan Wing;
> > > Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > Subject: Re: [mif]
> > > draft-ietf-mif-current-practices-00
> > >
> > > 2nd purpose has been
> > > documented in the current practice draft,
> > > whether 1st and 3rd purpose
> > > need to be documented as well? it may not
> > > directly related to
> > > MIF?
> >
> > Some operating systems -- e.g., most flavors of Unix -- do not
> > > support the
> > ability for sending different DNS queries to different DNS
> > > servers.
> >
> > It would be helpful if the draft more clearly described the
> > > functionality.
> > Someone unfamiliar with the Windows functionality, reading the
> > > draft, assumes
> > it is merely talking about the 'domain search list' -- because
> > > that is what
> > they are familiar with.
> >
> > I don't care how the draft
> > > is fixed to make it clearer.=A0 I propose describing
> > the 2 (and, as Dave
> > > pointed out, 3) functions.=A0 If you want to adjust the
> > document to
> > > instead talk about the per-interface stuff, that's great -- my
> > point is that
> > > right now it is insufficiently clear in explaining it.
> >
> > -d
> >
> > >
> > > -Hui
> > >
> > > 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com"
> > > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
> > >
> > > >> -----Original Message-----
> > > >> From: Dan Wing [mailto:> ymailto=3D"mailto:dwing@cisco.com"
> > > href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
> > > >> Sent:
> > > Tuesday, April 06, 2010 11:52 AM
> > > >> To: Dave Thaler; 'Hui Deng';
> > > Gabriel Montenegro
> > > >> Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> Subject: RE: [mif]
> > > draft-ietf-mif-current-practices-00
> > > >>
> > > >>
> > >
> > > >>
> > > >> > -----Original Message-----
> > > >> >
> > > From: Dave Thaler [mailto:>
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com]
> > > >>
> > > > Sent: Tuesday, April 06, 2010 10:06 AM
> > > >> > To: Hui Deng;
> > > Dan Wing; Gabriel Montenegro
> > > >> > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > Subject: RE:
> > > [mif] draft-ietf-mif-current-practices-00
> > > >> >
> > > >>
> > > > Hui is correct, Windows has per-interface DNS server lists
> > > >>
> > > configured.
> > > >> >
> > > >> > It then uses a host-wide
> > > "effective" server list for an
> > > actual query,
> > > >> >
> > > where the effective server list may be different for
> > > different
> > > names.
> > > >> >
> > > >> > On Windows the per-interface
> > > suffix is actually termed the
> > > >> > "connection-specific DNS
> > > suffix" to distinguish it from the
> > > >> > "primary DNS suffix" of
> > > the machine. =A0I think that's why
> > > >> > "interface-specific" was
> > > repeated in the first bullet.
> > > >>
> > > >>
> > >
> > > >>
> > > >> In draft-montenegro-mif-multihoming, there are two
> > >
> > > purposes and terms
> > > >> that
> > > >> seem to be
> > > intermingled using the term "DNS suffix".
> > > >>
> > > >> One
> > > purpose is the suffix for non-FQDN names, like
> > > "payroll" or
> > > "mail",
> > > >> which will have a suffix added to them (e.g., > target=3D"_blank"
> > href=3D"http://example.com">example.com).
> > > >
> > >
> > > > That's what windows calls the "DNS Suffix Search List" (see the
> > >
> > > > sample output I sent previously below). =A0It's called the
> > > >
> > > "domain search list" in other places (like RFC 3397), or just
> > > >
> > > "search list" (RFC 1123).
> > > >
> > > >> The
> > > >>
> > > other purpose is deciding which DNS server will be be sent
> > > a query
> > > for
> > > >> a certain FQDN (e.g., queries for *.>
> > href=3D"http://example.net">example.net go to one
> > > DNS server
> > >
> > > >> and queries for *.example.com go to a different DNS server).
> > >
> > > >
> > > > Another purpose is deciding which DNS server will receive a
> > > dynamic
> > > > update for a name with a certain suffix (e.g., Windows
> > >
> > > supports dynamic
> > > > updates for the primary DNS name, and
> > > optionally also the
> > > connection-
> > > > specific DNS name of the
> > > machine).
> > > >
> > > >>
> > > >>
> > > >> In
> > > draft-ietf-mif-current-practices-00, which is the WG document
> > > >>
> > > that seems to have boiled down draft-montenegro-mif-multihoming,
> > >
> > > >> but draft-ietf-mif-current-practices-00 also does not clearly
> > >
> > > >> separate the two purposes.
> > > >
> > > > Yep
> > >
> > > >
> > > > -Dave
> > > >>
> > > >> -d
> > >
> > > >>
> > > >>
> > > >> > Example on Windows, extracted
> > > from "ipconfig /all" output:
> > > >> >
> > > >> > Windows
> > > IP Configuration
> > > >> >
> > > >> > =A0 =A0Host Name . . .
> > > . . . . . . . . . : dthaler-win7
> > > >> > =A0 =A0Primary Dns Suffix =A0.
> > > . . . . . . : >
> > href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.com
> > >
> > > >> >
> > > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >>
> > > > =A0 =A0Node Type . . . . . . . . . . . . : Hybrid
> > > >> > =A0 =A0IP
> > > Routing Enabled. . . . . . . . : No
> > > >> > =A0 =A0WINS Proxy Enabled.
> > > . . . . . . . : No
> > > >> > =A0 =A0DNS Suffix Search List. . . . . . :
> > > ntdev.corp.microsoft.com
> > > >> >
> > > =A0 =A0 =A0>
> > href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.com
> > >
> > > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0>
> > href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
> > > >> >
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0>
> > href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
> > > >>
> > > > =A0 =A0System Quarantine State . . . . . : Not Restricted
> > > >>
> > > >
> > > >> > Wireless LAN adapter Wireless Network
> > > Connection:
> > > >> >
> > > >> > =A0 =A0Connection-specific
> > > DNS Suffix =A0. : >
> > href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.
> > > >> >
> > > =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >>
> > > > =A0 =A0Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> > >
> > > >> > Link 4965AGN
> > > >> > =A0 =A0Physical Address. . . . . .
> > > . . . : 00-1D-E0-34-4F-6F
> > > >> > =A0 =A0DHCP Enabled. . . . . . . . .
> > > . . : Yes
> > > >> > =A0 =A0Autoconfiguration Enabled . . . . :
> > > Yes
> > > >> > =A0 =A0Link-local IPv6 Address . . . . . :
> > >
> > > >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> > > >> >
> > > =A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> > > >>
> > > > =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > >> >
> > > =A0 =A0Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> > > >>
> > > > 10:19:02 PM
> > > >> > =A0 =A0Lease Expires . . . . . . . . . . :
> > > Tuesday, April 06,
> > > >> > 2010 10:19:02 PM
> > > >> >
> > > =A0 =A0Default Gateway . . . . . . . . . : 192.168.0.1
> > > >> > =A0 =A0DHCP
> > > Server . . . . . . . . . . . : 192.168.0.1
> > > >> > =A0 =A0DHCPv6 IAID
> > > . . . . . . . . . . . : 335551968
> > > >> > =A0 =A0DHCPv6 Client DUID. .
> > > . . . . . . :
> > > >> >
> > > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> > > >> >
> > > >>
> > > > =A0 =A0DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> > > >>
> > > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0192.168.0.1
> > > >> >
> > > =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >> >
> > > =A0NetBIOS over Tcpip. . . . . . . . : Enabled
> > > >> >
> > >
> > > >> > -Dave
> > > >> >
> > > >> > >
> > > -----Original Message-----
> > > >> > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com=
"
> > > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > > >> >
> > > > Sent: Monday, April 05, 2010 7:40 PM
> > > >> > > To: Dan
> > > Wing; Gabriel Montenegro; Dave Thaler
> > > >> > > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > > Subject:
> > > Re: [mif] draft-ietf-mif-current-practices-00
> > > >> > >
> > >
> > > >> > > DNS server always has specific interface related
> > > information,
> > > >> > > but the final DNS server will still be
> > > host based, I
> > > wouldn't say
> > > >> it
> > > >> >
> > > > is not correct.
> > > >> > >
> > > >> > > one
> > > example would be you have internet connection and vpn
> > > >>
> > > connection
> > > >> > > at the same time,
> > > >> >
> > > > good VPN implementation will always rely on VPN DNS server
> > > >>
> > > > information
> > > >> > > for Internet connection.
> > >
> > > >> > >
> > > >> > > -Hui
> > > >> >
> > > >
> > > >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"
> > > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
> > > >> >
> > > > > Section 3.2.1.3 of describes the DNS configuration
> > > of
> > > Windows,
> > > >> and
> > > >> > > says:
> > > >>
> > > > > >
> > > >> > > > =A0"Interface specific DNS
> > > configuration can be input
> > > via static
> > > >> > > >
> > > configuration or via DHCP. =A0It includes:
> > > >> > > >
> > >
> > > >> > > > =A0 o =A0An interface-specific suffix list.
> > > >>
> > > > > >
> > > >> > > > =A0 o =A0A list of DNS server IP
> > > addresses."
> > > >> > > >
> > > >> > > > It
> > > is curious that the first bullet repeats "interface
> > > >> >
> > > specific", but
> > > >> > > the
> > > >> > > >
> > > second bullet does not repeat it. =A0A reasonable
> > > interpretation
> > > is
> > > >> > > that the
> > > >> > > > second
> > > bullet is not interface-specific, but the
> > > lead-in sentence
> > >
> > > >> > > says this is
> > > >> > > >
> > > interface-specific. =A0I was hoping
> > > >> >
> > > draft-montenegro-mif-multihoming-00
> > > >> > > would
> > >
> > > >> > > > clarify, but it doesn't.
> > > >> > >
> > > >
> > > >> > > > -d
> > > >> > > >
> > >
> > > >> > > > _______________________________________________
> > >
> > > >> > > > mif mailing list
> > > >> > > > > ymailto=3D"mailto:mif@ietf.org"
> > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > > > > href=3D"https://www.ietf.org/mailman/listinfo/mif"
> > target=3D_blank
> > > >https://www.ietf.org/mailman/listinfo/mif
> > > >> > >
> > > >
> > > >> >
> > > >>
> > > >
> > >
> > > >
> >
> > _______________________________________________
> > mif mailing
> > > list
> > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
> > > >https://www.ietf.org/mailman/listinfo/mif
> > _______________________________________________
> > mif mailing list
> > mif@ietf.org
> > https://www.ietf.org/mailman/listinfo/mif


From dthaler@microsoft.com  Mon Apr 12 15:45:32 2010
Return-Path: <dthaler@microsoft.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 D27D63A6868 for <mif@core3.amsl.com>; Mon, 12 Apr 2010 15:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.871
X-Spam-Level: 
X-Spam-Status: No, score=-109.871 tagged_above=-999 required=5 tests=[AWL=0.728, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 snwVqzk14P8V for <mif@core3.amsl.com>; Mon, 12 Apr 2010 15:45:30 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 372EF3A6809 for <mif@ietf.org>; Mon, 12 Apr 2010 15:45:30 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 12 Apr 2010 15:45:10 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 12 Apr 2010 15:45:10 -0700
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.63]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 12 Apr 2010 15:45:09 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>, "g_e_montenegro@yahoo.com" <g_e_montenegro@yahoo.com>, "dwing@cisco.com" <dwing@cisco.com>, "denghui02@gmail.com" <denghui02@gmail.com>
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AQHK1TKMaTaZ5uEk9UKBxenwZvGT9pIVqnJAgAAdoSCAAA5RwIACev8AgADHYICAAGMjgIAGU02A//+oG2CAAAF6sA==
Date: Mon, 12 Apr 2010 22:44:54 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF65139303C8@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com> <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 12 Apr 2010 22:45:33 -0000

And for the "note well", Microsoft may have some IP in this area.

-Dave

> -----Original Message-----
> From: Dave Thaler
> Sent: Monday, April 12, 2010 3:43 PM
> To: 'teemu.savolainen@nokia.com'; g_e_montenegro@yahoo.com; dwing@cisco.c=
om;
> denghui02@gmail.com
> Cc: mif@ietf.org
> Subject: RE: [mif] draft-ietf-mif-current-practices-00
>
> > -----Original Message-----
> > From: teemu.savolainen@nokia.com [mailto:teemu.savolainen@nokia.com]
> > Sent: Monday, April 12, 2010 1:53 PM
> > To: g_e_montenegro@yahoo.com; dwing@cisco.com; denghui02@gmail.com; Dav=
e
> > Thaler
> > Cc: mif@ietf.org
> > Subject: RE: [mif] draft-ietf-mif-current-practices-00
> >
> > Hi,
> >
> > Why do you think #4 is not mif-specific? What possible use NRPT has for
> single
> > interfaced host? Or is the idea such that a host could have single
> interface,
> > but just use different DNS server for queries matching NRPT?
>
> Right.  The NRPT is similar to a configured cache of NS records.
> It's used to solve the problem of have access to multiple disjoint namesp=
aces
> (like corporate DNS and public DNS).  Private names aren't resolvable in
> the public DNS, so you have to know what DNS server to ask.
>
> > ....hmm...
> > Do you consider a host using DirectAccess single or multi-interfaced? F=
rom
> my
> > quick reading of the DirectAccess feature, it sounds to be somewhere in
> > between - not obviously multi-interface like the VPN-case is, but not q=
uite
> > single-interfaced either.
>
> Right it could be either one.
>
> >
> > Is there a way to configure NRPT policies remotely via some protocol?
>
> Yes, it's designed to be configured by an enterprise administrator of the
> organization that manages the host.  So there's an authenticated,
> configuration distribution protocol for ActiveDirectory-domain-joined hos=
ts.
>
> -Dave
>
> >
> > Thanks for explanation,
> >
> > Teemu
> >
> > > -----Original Message-----
> > > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> > > ext gabriel montenegro
> > > Sent: 08. huhtikuuta 2010 23:17
> > > To: Dan Wing; Hui Deng; Dave Thaler
> > > Cc: mif@ietf.org
> > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> > >
> > > In addition to those three usages of "suffix":
> > >
> > > 1. Domain Search list suffix
> > > 2. For interface-specific suffix list
> > > 3. Suffix to control Dynamic DNS Updates
> > >
> > > There is yet another usage in Windows introduced in windows 7 and its
> > > server counterpart, Windows Server 2008 R2:
> > >
> > > 4. Suffix in the NRPT [1] to aid in identifying a Namespace that
> > > requires special handling,
> > > as used for DirectAccess [2]. This is not MIF-specific either.
> > >
> > > Only #2 is MIF-specific (and this should be called out), but it makes
> > > sense to clarify the
> > > other uses of "suffix" otherwise #2 won't be clear.
> > >
> > > [1] NRPT: See http://technet.microsoft.com/en-us/magazine/ff394369.as=
px
> > > [2] DirectAcess: http://technet.microsoft.com/en-
> > > us/magazine/2009.05.cableguy.aspx
> > >
> > > Gabriel
> > >
> > > ----- Original Message ----
> > > > From: Dan Wing <dwing@cisco.com>
> > > > To: Hui Deng <denghui02@gmail.com>; Dave Thaler
> > > <dthaler@microsoft.com>
> > > > Cc: mif@ietf.org; Gabriel Montenegro <gmonte@microsoft.com>
> > > > Sent: Thu, April 8, 2010 7:22:23 AM
> > > > Subject: Re: [mif] draft-ietf-mif-current-practices-00
> > > >
> > > >
> > >
> > > > -----Original Message-----
> > > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.com"
> > > > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > > > Sent:
> > > > Wednesday, April 07, 2010 7:29 PM
> > > > To: Dave Thaler
> > > > Cc: Dan Wing;
> > > > Gabriel Montenegro; > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > Subject: Re: [mif]
> > > > draft-ietf-mif-current-practices-00
> > > >
> > > > 2nd purpose has been
> > > > documented in the current practice draft,
> > > > whether 1st and 3rd purpose
> > > > need to be documented as well? it may not
> > > > directly related to
> > > > MIF?
> > >
> > > Some operating systems -- e.g., most flavors of Unix -- do not
> > > > support the
> > > ability for sending different DNS queries to different DNS
> > > > servers.
> > >
> > > It would be helpful if the draft more clearly described the
> > > > functionality.
> > > Someone unfamiliar with the Windows functionality, reading the
> > > > draft, assumes
> > > it is merely talking about the 'domain search list' -- because
> > > > that is what
> > > they are familiar with.
> > >
> > > I don't care how the draft
> > > > is fixed to make it clearer.  I propose describing
> > > the 2 (and, as Dave
> > > > pointed out, 3) functions.  If you want to adjust the
> > > document to
> > > > instead talk about the per-interface stuff, that's great -- my
> > > point is that
> > > > right now it is insufficiently clear in explaining it.
> > >
> > > -d
> > >
> > > >
> > > > -Hui
> > > >
> > > > 2010/4/7 Dave Thaler <> ymailto=3D"mailto:dthaler@microsoft.com"
> > > > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
> > > >
> > > > >> -----Original Message-----
> > > > >> From: Dan Wing [mailto:> ymailto=3D"mailto:dwing@cisco.com"
> > > > href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
> > > > >> Sent:
> > > > Tuesday, April 06, 2010 11:52 AM
> > > > >> To: Dave Thaler; 'Hui Deng';
> > > > Gabriel Montenegro
> > > > >> Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > >> Subject: RE: [mif]
> > > > draft-ietf-mif-current-practices-00
> > > > >>
> > > > >>
> > > >
> > > > >>
> > > > >> > -----Original Message-----
> > > > >> >
> > > > From: Dave Thaler [mailto:>
> > > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com]
> > > > >>
> > > > > Sent: Tuesday, April 06, 2010 10:06 AM
> > > > >> > To: Hui Deng;
> > > > Dan Wing; Gabriel Montenegro
> > > > >> > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > >> > Subject: RE:
> > > > [mif] draft-ietf-mif-current-practices-00
> > > > >> >
> > > > >>
> > > > > Hui is correct, Windows has per-interface DNS server lists
> > > > >>
> > > > configured.
> > > > >> >
> > > > >> > It then uses a host-wide
> > > > "effective" server list for an
> > > > actual query,
> > > > >> >
> > > > where the effective server list may be different for
> > > > different
> > > > names.
> > > > >> >
> > > > >> > On Windows the per-interface
> > > > suffix is actually termed the
> > > > >> > "connection-specific DNS
> > > > suffix" to distinguish it from the
> > > > >> > "primary DNS suffix" of
> > > > the machine.  I think that's why
> > > > >> > "interface-specific" was
> > > > repeated in the first bullet.
> > > > >>
> > > > >>
> > > >
> > > > >>
> > > > >> In draft-montenegro-mif-multihoming, there are two
> > > >
> > > > purposes and terms
> > > > >> that
> > > > >> seem to be
> > > > intermingled using the term "DNS suffix".
> > > > >>
> > > > >> One
> > > > purpose is the suffix for non-FQDN names, like
> > > > "payroll" or
> > > > "mail",
> > > > >> which will have a suffix added to them (e.g., > target=3D"_blank=
"
> > > href=3D"http://example.com">example.com).
> > > > >
> > > >
> > > > > That's what windows calls the "DNS Suffix Search List" (see the
> > > >
> > > > > sample output I sent previously below).  It's called the
> > > > >
> > > > "domain search list" in other places (like RFC 3397), or just
> > > > >
> > > > "search list" (RFC 1123).
> > > > >
> > > > >> The
> > > > >>
> > > > other purpose is deciding which DNS server will be be sent
> > > > a query
> > > > for
> > > > >> a certain FQDN (e.g., queries for *.>
> > > href=3D"http://example.net">example.net go to one
> > > > DNS server
> > > >
> > > > >> and queries for *.example.com go to a different DNS server).
> > > >
> > > > >
> > > > > Another purpose is deciding which DNS server will receive a
> > > > dynamic
> > > > > update for a name with a certain suffix (e.g., Windows
> > > >
> > > > supports dynamic
> > > > > updates for the primary DNS name, and
> > > > optionally also the
> > > > connection-
> > > > > specific DNS name of the
> > > > machine).
> > > > >
> > > > >>
> > > > >>
> > > > >> In
> > > > draft-ietf-mif-current-practices-00, which is the WG document
> > > > >>
> > > > that seems to have boiled down draft-montenegro-mif-multihoming,
> > > >
> > > > >> but draft-ietf-mif-current-practices-00 also does not clearly
> > > >
> > > > >> separate the two purposes.
> > > > >
> > > > > Yep
> > > >
> > > > >
> > > > > -Dave
> > > > >>
> > > > >> -d
> > > >
> > > > >>
> > > > >>
> > > > >> > Example on Windows, extracted
> > > > from "ipconfig /all" output:
> > > > >> >
> > > > >> > Windows
> > > > IP Configuration
> > > > >> >
> > > > >> >    Host Name . . .
> > > > . . . . . . . . . : dthaler-win7
> > > > >> >    Primary Dns Suffix  .
> > > > . . . . . . : >
> > > href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.com
> > > >
> > > > >> >
> > > >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > > >>
> > > > >    Node Type . . . . . . . . . . . . : Hybrid
> > > > >> >    IP
> > > > Routing Enabled. . . . . . . . : No
> > > > >> >    WINS Proxy Enabled.
> > > > . . . . . . . : No
> > > > >> >    DNS Suffix Search List. . . . . . :
> > > > ntdev.corp.microsoft.com
> > > > >> >
> > > >      >
> > > href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.com
> > > >
> > > > >> >                                        >
> > > href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
> > > > >> >
> > > >                                        >
> > > href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
> > > > >>
> > > > >    System Quarantine State . . . . . : Not Restricted
> > > > >>
> > > > >
> > > > >> > Wireless LAN adapter Wireless Network
> > > > Connection:
> > > > >> >
> > > > >> >    Connection-specific
> > > > DNS Suffix  . : >
> > > href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.
> > > > >> >
> > > >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > > >>
> > > > >    Description . . . . . . . . . . . : Intel(R) Wireless WiFi
> > > >
> > > > >> > Link 4965AGN
> > > > >> >    Physical Address. . . . . .
> > > > . . . : 00-1D-E0-34-4F-6F
> > > > >> >    DHCP Enabled. . . . . . . . .
> > > > . . : Yes
> > > > >> >    Autoconfiguration Enabled . . . . :
> > > > Yes
> > > > >> >    Link-local IPv6 Address . . . . . :
> > > >
> > > > >> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> > > > >> >
> > > >  IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> > > > >>
> > > > >    Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > >> >
> > > >    Lease Obtained. . . . . . . . . . : Monday, April 05, 2010
> > > > >>
> > > > > 10:19:02 PM
> > > > >> >    Lease Expires . . . . . . . . . . :
> > > > Tuesday, April 06,
> > > > >> > 2010 10:19:02 PM
> > > > >> >
> > > >    Default Gateway . . . . . . . . . : 192.168.0.1
> > > > >> >    DHCP
> > > > Server . . . . . . . . . . . : 192.168.0.1
> > > > >> >    DHCPv6 IAID
> > > > . . . . . . . . . . . : 335551968
> > > > >> >    DHCPv6 Client DUID. .
> > > > . . . . . . :
> > > > >> >
> > > > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> > > > >> >
> > > > >>
> > > > >    DNS Servers . . . . . . . . . . . : 2001:df8:0:1::25
> > > > >>
> > > > >                                        192.168.0.1
> > > > >> >
> > > >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > > >> >
> > > >  NetBIOS over Tcpip. . . . . . . . : Enabled
> > > > >> >
> > > >
> > > > >> > -Dave
> > > > >> >
> > > > >> > >
> > > > -----Original Message-----
> > > > >> > > From: Hui Deng [mailto:> ymailto=3D"mailto:denghui02@gmail.c=
om"
> > > > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > > > >> >
> > > > > Sent: Monday, April 05, 2010 7:40 PM
> > > > >> > > To: Dan
> > > > Wing; Gabriel Montenegro; Dave Thaler
> > > > >> > > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > >> > > Subject:
> > > > Re: [mif] draft-ietf-mif-current-practices-00
> > > > >> > >
> > > >
> > > > >> > > DNS server always has specific interface related
> > > > information,
> > > > >> > > but the final DNS server will still be
> > > > host based, I
> > > > wouldn't say
> > > > >> it
> > > > >> >
> > > > > is not correct.
> > > > >> > >
> > > > >> > > one
> > > > example would be you have internet connection and vpn
> > > > >>
> > > > connection
> > > > >> > > at the same time,
> > > > >> >
> > > > > good VPN implementation will always rely on VPN DNS server
> > > > >>
> > > > > information
> > > > >> > > for Internet connection.
> > > >
> > > > >> > >
> > > > >> > > -Hui
> > > > >> >
> > > > >
> > > > >> > > 2010/3/31 Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"
> > > > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
> > > > >> >
> > > > > > Section 3.2.1.3 of describes the DNS configuration
> > > > of
> > > > Windows,
> > > > >> and
> > > > >> > > says:
> > > > >>
> > > > > > >
> > > > >> > > >  "Interface specific DNS
> > > > configuration can be input
> > > > via static
> > > > >> > > >
> > > > configuration or via DHCP.  It includes:
> > > > >> > > >
> > > >
> > > > >> > > >   o  An interface-specific suffix list.
> > > > >>
> > > > > > >
> > > > >> > > >   o  A list of DNS server IP
> > > > addresses."
> > > > >> > > >
> > > > >> > > > It
> > > > is curious that the first bullet repeats "interface
> > > > >> >
> > > > specific", but
> > > > >> > > the
> > > > >> > > >
> > > > second bullet does not repeat it.  A reasonable
> > > > interpretation
> > > > is
> > > > >> > > that the
> > > > >> > > > second
> > > > bullet is not interface-specific, but the
> > > > lead-in sentence
> > > >
> > > > >> > > says this is
> > > > >> > > >
> > > > interface-specific.  I was hoping
> > > > >> >
> > > > draft-montenegro-mif-multihoming-00
> > > > >> > > would
> > > >
> > > > >> > > > clarify, but it doesn't.
> > > > >> > >
> > > > >
> > > > >> > > > -d
> > > > >> > > >
> > > >
> > > > >> > > > _______________________________________________
> > > >
> > > > >> > > > mif mailing list
> > > > >> > > > > ymailto=3D"mailto:mif@ietf.org"
> > > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > >> > > > > href=3D"https://www.ietf.org/mailman/listinfo/mif"
> > > target=3D_blank
> > > > >https://www.ietf.org/mailman/listinfo/mif
> > > > >> > >
> > > > >
> > > > >> >
> > > > >>
> > > > >
> > > >
> > > > >
> > >
> > > _______________________________________________
> > > mif mailing
> > > > list
> > > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
> > > > >https://www.ietf.org/mailman/listinfo/mif
> > > _______________________________________________
> > > mif mailing list
> > > mif@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mif


From g_e_montenegro@yahoo.com  Mon Apr 12 16:18:14 2010
Return-Path: <g_e_montenegro@yahoo.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 3084A3A68AF for <mif@core3.amsl.com>; Mon, 12 Apr 2010 16:18:14 -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 6AipW4M-VXe3 for <mif@core3.amsl.com>; Mon, 12 Apr 2010 16:18:12 -0700 (PDT)
Received: from web82603.mail.mud.yahoo.com (web82603.mail.mud.yahoo.com [68.142.201.120]) by core3.amsl.com (Postfix) with SMTP id 623053A6927 for <mif@ietf.org>; Mon, 12 Apr 2010 16:17:59 -0700 (PDT)
Received: (qmail 97786 invoked by uid 60001); 12 Apr 2010 23:17:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1271114271; bh=XGKI6oYfx+tUTfV96S9ykKfTlV/blN2aIVjmdBV79JI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1FFUpcxbEoYG/4/1dTgcfqRNfEQ8ndiPvM050aKNe3o6HQWCpwVQEvLMweM/FH4ClQZavoen5/ieIlfRkk0pt3tJE09XvPNaNQXQC2opEFpI0Nk4YUriaDrpqnyZ4zgFFAzrFQ/pC/HhK4BLdd+TRkavvxMcH1MfHMA7D10ya/0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hwYgVCGpNRGUO6m4vfAl1CqEsrnustZWm4laloOJxm+mOOunugBYrYVRLUFPGcu4o/nNWgBFLvS3SQMbUh38EYtwzTtvylLTHs67Ikn9hcelrQkW21BqzFmUz8UhH3B39lxt54mGSUPDmzOzzDB0NSLMvaPV2PqGptwS91e8DOE=;
Message-ID: <350270.96614.qm@web82603.mail.mud.yahoo.com>
X-YMail-OSG: oKzD.d0VM1ke_m2sjFUr914nRM2yudx35W8YPcq.JwY8EK7 dWApmWTTqXKYk4DW3H47sgt_ZtREhEuxFBkhPkVYvNXdvnsMF.5k2fYSgY8_ MmmOPwqotlyZ7BJppDIyfQuDq..q3DsMopTVXUOCDimSAGSlWTdZzs_8jqJc OPsfWNqrdtGR8EWBMku_0QgWNa8awdvnlV9j7r2kcwFgE.zX4ojCXyjnuI1x nFoTaqQAnOQdXiS._XrWkKk7Bfi4huBOFDUsFYott4k_j3_4D.cS6NZyU.GW O_0Lsl8XhlUxD8gX_zCZnZVxBfw4M3r3.p0AgojvVcQFAM02XORUtPMKmNA- -
Received: from [131.107.0.75] by web82603.mail.mud.yahoo.com via HTTP; Mon, 12 Apr 2010 16:17:51 PDT
X-Mailer: YahooMailRC/348.3 YahooMailWebService/0.8.100.260964
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com> <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
Date: Mon, 12 Apr 2010 16:17:51 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: teemu.savolainen@nokia.com, dwing@cisco.com, denghui02@gmail.com, dthaler@microsoft.com
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 12 Apr 2010 23:18:14 -0000

Hi Teemu,=0A=0AI don't consider NRPT a MIF-specific technology as the whole=
 point is =0Ato enable=A0*namespace-specific DNS servers*, in addition to t=
he well-known=0Ainterface-specific DNS servers.=0A=0AAlso, NRPT is not spec=
ific to DirectAccess. For example, it is also used for DNSSEC. =0AEven when=
 used for DirectAccess, it is even harder than with VPNs to consider=0Ait a=
n "interface". For example, DirectAccess can use IPsec transport mode to ac=
cess=0Aintranet resources. Whereas VPN's that use IPsec in tunnel mode are =
sometimes=0Athought of as constituting an "interface", I'm not sure I've se=
en that for =0AIPsec in *transport* mode.=0A=0ANRPT can be managed remotely=
 by Group Policy.=0A=0Athanks,=0A=0AGabriel=0A=0A----- Original Message ---=
-=0A> From: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>=0A> T=
o: g_e_montenegro@yahoo.com; dwing@cisco.com; denghui02@gmail.com; dthaler@=
microsoft.com=0A> Cc: mif@ietf.org=0A> Sent: Mon, April 12, 2010 1:52:55 PM=
=0A> Subject: RE: [mif] draft-ietf-mif-current-practices-00=0A> =0A> Hi,=0A=
=0AWhy do you think #4 is not mif-specific? What possible use NRPT has =0A>=
 for single interfaced host? Or is the idea such that a host could have sin=
gle =0A> interface, but just use different DNS server for queries matching =
=0A> NRPT?=0A....hmm...=0ADo you consider a host using DirectAccess single =
or =0A> multi-interfaced? From my quick reading of the DirectAccess feature=
, it sounds =0A> to be somewhere in between - not obviously multi-interface=
 like the VPN-case is, =0A> but not quite single-interfaced either. =0A=0AI=
s there a way to configure NRPT =0A> policies remotely via some protocol?=
=0A=0AThanks for =0A> explanation,=0A=0ATeemu=0A=0A> -----Original Message-=
----=0A> From: =0A> > href=3D"mailto:mif-bounces@ietf.org">mif-bounces@ietf=
.org [mailto:> ymailto=3D"mailto:mif-bounces@ietf.org" =0A> href=3D"mailto:=
mif-bounces@ietf.org">mif-bounces@ietf.org] On Behalf =0A> Of=0A> ext gabri=
el montenegro=0A> Sent: 08. huhtikuuta 2010 =0A> 23:17=0A> To: Dan Wing; Hu=
i Deng; Dave Thaler=0A> Cc: > ymailto=3D"mailto:mif@ietf.org" =0A> href=3D"=
mailto:mif@ietf.org">mif@ietf.org=0A> Subject: Re: [mif] =0A> draft-ietf-mi=
f-current-practices-00=0A> =0A> In addition to those three =0A> usages of "=
suffix":=0A> =0A> 1. Domain Search list suffix=0A> 2. For =0A> interface-sp=
ecific suffix list=0A> 3. Suffix to control Dynamic =0A> DNS=A0Updates=0A> =
=0A> There is yet another usage in Windows introduced in =0A> windows 7 and=
 its=0A> server counterpart, Windows Server 2008 R2:=0A> =0A> =0A> 4. Suffi=
x in the NRPT [1] to aid in identifying a Namespace =0A> that=0A> requires =
special handling,=0A> as used for DirectAccess [2]. =0A> This is not MIF-sp=
ecific either.=0A> =0A> Only #2 is MIF-specific (and =0A> this should be ca=
lled out), but it makes=0A> sense to clarify the=0A> =0A> other uses of "su=
ffix" otherwise #2 won't be clear.=0A> =0A> [1] NRPT: =0A> See http://techn=
et.microsoft.com/en-us/magazine/ff394369.aspx=0A> [2] =0A> DirectAcess: htt=
p://technet.microsoft.com/en-=0A> =0A> us/magazine/2009.05.cableguy.aspx=0A=
> =0A> Gabriel=0A> =0A> =0A> ----- Original Message ----=0A> > From: Dan Wi=
ng <> ymailto=3D"mailto:dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.co=
m">dwing@cisco.com>=0A> > To: Hui Deng =0A> <> href=3D"mailto:denghui02@gma=
il.com">denghui02@gmail.com>; Dave =0A> Thaler=0A> <> href=3D"mailto:dthale=
r@microsoft.com">dthaler@microsoft.com>=0A> > =0A> Cc: > href=3D"mailto:mif=
@ietf.org">mif@ietf.org; Gabriel Montenegro <> ymailto=3D"mailto:gmonte@mic=
rosoft.com" =0A> href=3D"mailto:gmonte@microsoft.com">gmonte@microsoft.com>=
=0A> > =0A> Sent: Thu, April 8, 2010 7:22:23 AM=0A> > Subject: Re: [mif] =
=0A> draft-ietf-mif-current-practices-00=0A> >=0A> >=0A> =0A> =0A> > -----O=
riginal Message-----=0A> > From: Hui Deng [mailto:> =0A> ymailto=3D"mailto:=
> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com"=0A> > =0A> href=
=3D"mailto:> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com">> yma=
ilto=3D"mailto:denghui02@gmail.com" =0A> href=3D"mailto:denghui02@gmail.com=
">denghui02@gmail.com]=0A> > =0A> Sent:=0A> > Wednesday, April 07, 2010 7:2=
9 PM=0A> > To: Dave =0A> Thaler=0A> > Cc: Dan Wing;=0A> > Gabriel Montenegr=
o; > =0A> href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">> hre=
f=3D"mailto:mif@ietf.org">mif@ietf.org=0A> > Subject: Re: =0A> [mif]=0A> > =
draft-ietf-mif-current-practices-00=0A> >=0A> > =0A> 2nd purpose has been=
=0A> > documented in the current practice =0A> draft,=0A> > whether 1st and=
 3rd purpose=0A> > need to be =0A> documented as well? it may not=0A> > dir=
ectly related to=0A> > =0A> MIF?=0A> =0A> Some operating systems -- e.g., m=
ost flavors of Unix -- do =0A> not=0A> > support the=0A> ability for sendin=
g different DNS queries =0A> to different DNS=0A> > servers.=0A> =0A> It wo=
uld be helpful if =0A> the draft more clearly described the=0A> > functiona=
lity.=0A> Someone =0A> unfamiliar with the Windows functionality, reading t=
he=0A> > draft, =0A> assumes=0A> it is merely talking about the 'domain sea=
rch list' -- =0A> because=0A> > that is what=0A> they are familiar with.=0A=
> =0A> =0A> I don't care how the draft=0A> > is fixed to make it clearer.=
=A0 I =0A> propose describing=0A> the 2 (and, as Dave=0A> > pointed out, 3)=
 =0A> functions.=A0 If you want to adjust the=0A> document to=0A> > instead=
 =0A> talk about the per-interface stuff, that's great -- my=0A> point is =
=0A> that=0A> > right now it is insufficiently clear in explaining it.=0A> =
=0A> =0A> -d=0A> =0A> >=0A> > -Hui=0A> >=0A> > =0A> 2010/4/7 Dave Thaler <>=
 ymailto=3D"mailto:> ymailto=3D"mailto:dthaler@microsoft.com" =0A> href=3D"=
mailto:dthaler@microsoft.com">dthaler@microsoft.com"=0A> > =0A> href=3D"mai=
lto:> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com">> ymailt=
o=3D"mailto:dthaler@microsoft.com" =0A> href=3D"mailto:dthaler@microsoft.co=
m">dthaler@microsoft.com>:=0A> =0A> >=0A> > >> -----Original Message-----=
=0A> > >> =0A> From: Dan Wing [mailto:> ymailto=3D"mailto:> href=3D"mailto:=
dwing@cisco.com">dwing@cisco.com"=0A> > href=3D"mailto:> ymailto=3D"mailto:=
dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com">> ym=
ailto=3D"mailto:dwing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing=
@cisco.com]=0A> > >> =0A> Sent:=0A> > Tuesday, April 06, 2010 11:52 AM=0A> =
> >> To: =0A> Dave Thaler; 'Hui Deng';=0A> > Gabriel Montenegro=0A> > >> =
=0A> Cc: > href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">> hr=
ef=3D"mailto:mif@ietf.org">mif@ietf.org=0A> > >> Subject: RE: =0A> [mif]=0A=
> > draft-ietf-mif-current-practices-00=0A> > =0A> >>=0A> > >>=0A> >=0A> > =
>>=0A> > =0A> >> > -----Original Message-----=0A> > >> >=0A> > =0A> From: D=
ave Thaler [mailto:>=0A> href=3D"mailto:> ymailto=3D"mailto:dthaler@microso=
ft.com" =0A> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com">>=
 ymailto=3D"mailto:dthaler@microsoft.com" =0A> href=3D"mailto:dthaler@micro=
soft.com">dthaler@microsoft.com]=0A> > =0A> >>=0A> > > Sent: Tuesday, April=
 06, 2010 10:06 AM=0A> > =0A> >> > To: Hui Deng;=0A> > Dan Wing; Gabriel Mo=
ntenegro=0A> =0A> > >> > Cc: > ymailto=3D"mailto:> href=3D"mailto:mif@ietf.=
org">mif@ietf.org"=0A> > href=3D"mailto:> ymailto=3D"mailto:mif@ietf.org" h=
ref=3D"mailto:mif@ietf.org">mif@ietf.org">> ymailto=3D"mailto:mif@ietf.org"=
 =0A> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A> > >> > Subject: =0A> RE=
:=0A> > [mif] draft-ietf-mif-current-practices-00=0A> > >> =0A> >=0A> > >>=
=0A> > > Hui is correct, Windows has =0A> per-interface DNS server lists=0A=
> > >>=0A> > =0A> configured.=0A> > >> >=0A> > >> > It then uses a =0A> hos=
t-wide=0A> > "effective" server list for an=0A> > actual =0A> query,=0A> > =
>> >=0A> > where the effective server list =0A> may be different for=0A> > =
different=0A> > names.=0A> > =0A> >> >=0A> > >> > On Windows the per-interf=
ace=0A> =0A> > suffix is actually termed the=0A> > >> > =0A> "connection-sp=
ecific DNS=0A> > suffix" to distinguish it from the=0A> =0A> > >> > "primar=
y DNS suffix" of=0A> > the machine. =A0I think =0A> that's why=0A> > >> > "=
interface-specific" was=0A> > =0A> repeated in the first bullet.=0A> > >>=
=0A> > =0A> >>=0A> >=0A> > >>=0A> > >> In =0A> draft-montenegro-mif-multiho=
ming, there are two=0A> >=0A> > =0A> purposes and terms=0A> > >> that=0A> >=
 >> seem to =0A> be=0A> > intermingled using the term "DNS suffix".=0A> > =
=0A> >>=0A> > >> One=0A> > purpose is the suffix for =0A> non-FQDN names, l=
ike=0A> > "payroll" or=0A> > "mail",=0A> > =0A> >> which will have a suffix=
 added to them (e.g., > =0A> target=3D"_blank"=0A> href=3D"http://example.c=
om">> href=3D"http://example.com">example.com).=0A> > >=0A> =0A> >=0A> > > =
That's what windows calls the "DNS Suffix Search List" =0A> (see the=0A> >=
=0A> > > sample output I sent previously below). =0A> =A0It's called the=0A=
> > >=0A> > "domain search list" in other =0A> places (like RFC 3397), or j=
ust=0A> > >=0A> > "search list" =0A> (RFC 1123).=0A> > >=0A> > >> The=0A> >=
 =0A> >>=0A> > other purpose is deciding which DNS server will be be =0A> s=
ent=0A> > a query=0A> > for=0A> > >> a certain FQDN =0A> (e.g., queries for=
 *.>=0A> href=3D"http://example.net">> target=3D"_blank" href=3D"http://exa=
mple.net">example.net go to one=0A> > =0A> DNS server=0A> >=0A> > >> and qu=
eries for *.example.com go =0A> to a different DNS server).=0A> >=0A> > >=
=0A> > > =0A> Another purpose is deciding which DNS server will receive a=
=0A> > =0A> dynamic=0A> > > update for a name with a certain suffix (e.g., =
=0A> Windows=0A> >=0A> > supports dynamic=0A> > > updates for =0A> the prim=
ary DNS name, and=0A> > optionally also the=0A> > =0A> connection-=0A> > > =
specific DNS name of the=0A> > =0A> machine).=0A> > >=0A> > >>=0A> > >>=0A>=
 =0A> > >> In=0A> > draft-ietf-mif-current-practices-00, which is the =0A> =
WG document=0A> > >>=0A> > that seems to have boiled down =0A> draft-monten=
egro-mif-multihoming,=0A> >=0A> > >> but =0A> draft-ietf-mif-current-practi=
ces-00 also does not clearly=0A> >=0A> =0A> > >> separate the two purposes.=
=0A> > >=0A> > > =0A> Yep=0A> >=0A> > >=0A> > > -Dave=0A> > =0A> >>=0A> > >=
> -d=0A> >=0A> > >>=0A> =0A> > >>=0A> > >> > Example on Windows, extracted=
=0A> =0A> > from "ipconfig /all" output:=0A> > >> >=0A> > =0A> >> > Windows=
=0A> > IP Configuration=0A> > >> =0A> >=0A> > >> > =A0 =A0Host Name . . .=
=0A> > . . . . . . . . =0A> . : dthaler-win7=0A> > >> > =A0 =A0Primary Dns =
Suffix =A0.=0A> =0A> > . . . . . . : >=0A> href=3D"http://ntdev.corp.micros=
oft.com">> target=3D"_blank" =0A> href=3D"http://ntdev.corp.microsoft.com">=
ntdev.corp.microsoft.com=0A> =0A> >=0A> > >> >=0A> > =0A> =A0^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A> > =0A> >>=0A> > > =A0 =
=A0Node Type . . . . . . . . . . . . : Hybrid=0A> =0A> > >> > =A0 =A0IP=0A>=
 > Routing Enabled. . . . . . . . : =0A> No=0A> > >> > =A0 =A0WINS Proxy En=
abled.=0A> > . . . . . . . =0A> : No=0A> > >> > =A0 =A0DNS Suffix Search Li=
st. . . . . . :=0A> =0A> > ntdev.corp.microsoft.com=0A> > >> >=0A> > =A0 =
=A0 =0A> =A0>=0A> href=3D"http://redmond.corp.microsoft.com">> href=3D"http=
://redmond.corp.microsoft.com">redmond.corp.microsoft.com=0A> =0A> >=0A> > =
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =0A> =A0>=0A> href=3D"http://ntdev.microsoft.com">> href=3D"http://=
ntdev.microsoft.com">ntdev.microsoft.com=0A> > >> =0A> >=0A> > =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0>=0A> =
=0A> href=3D"http://dns.corp.microsoft.com">> href=3D"http://dns.corp.micro=
soft.com">dns.corp.microsoft.com=0A> > =0A> >>=0A> > > =A0 =A0System Quaran=
tine State . . . . . : Not =0A> Restricted=0A> > >>=0A> > >=0A> > >> > =0A>=
 Wireless LAN adapter Wireless Network=0A> > Connection:=0A> > =0A> >> >=0A=
> > >> > =A0 =A0Connection-specific=0A> > DNS =0A> Suffix =A0. : >=0A> href=
=3D"http://hsd1.wa.comcast.net">> href=3D"http://hsd1.wa.comcast.net">hsd1.=
wa.comcast.net.=0A> > >> =0A> >=0A> > =A0 =0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A> > =0A> >>=0A> > > =A0 =A0Description . =
. . . . . . . . . . : Intel(R) =0A> Wireless WiFi=0A> >=0A> > >> > Link 496=
5AGN=0A> > =0A> >> > =A0 =A0Physical Address. . . . . .=0A> > . . . : =0A> =
00-1D-E0-34-4F-6F=0A> > >> > =A0 =A0DHCP Enabled. . . . . . . . =0A> .=0A> =
> . . : Yes=0A> > >> > =A0 =A0Autoconfiguration Enabled =0A> . . . . :=0A> =
> Yes=0A> > >> > =A0 =A0Link-local IPv6 Address =0A> . . . . . :=0A> >=0A> =
> >> > =0A> fe80::4853:4753:9d8d:3b45%13(Preferred)=0A> > >> >=0A> > =0A> =
=A0IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)=0A> > =0A> =
>>=0A> > > =A0 =A0Subnet Mask . . . . . . . . . . . : =0A> 255.255.255.0=0A=
> > >> >=0A> > =A0 =A0Lease Obtained. . . . . =0A> . . . . . : Monday, Apri=
l 05, 2010=0A> > >>=0A> > > =0A> 10:19:02 PM=0A> > >> > =A0 =A0Lease Expire=
s . . . . . . . . . . =0A> :=0A> > Tuesday, April 06,=0A> > >> > 2010 10:19=
:02 =0A> PM=0A> > >> >=0A> > =A0 =A0Default Gateway . . . . . . . . . =0A> =
: 192.168.0.1=0A> > >> > =A0 =A0DHCP=0A> > Server . . . . . . =0A> . . . . =
. : 192.168.0.1=0A> > >> > =A0 =A0DHCPv6 IAID=0A> > . =0A> . . . . . . . . =
. . : 335551968=0A> > >> > =A0 =A0DHCPv6 Client =0A> DUID. .=0A> > . . . . =
. . :=0A> > >> >=0A> > =0A> 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD=0A> >=
 >> >=0A> =0A> > >>=0A> > > =A0 =A0DNS Servers . . . . . . . . . . . : =0A>=
 2001:df8:0:1::25=0A> > >>=0A> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =0A> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.0.1=0A> > >> >=0A> > =
=0A> =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=0A> > >> =0A> >=0A>=
 > =A0NetBIOS over Tcpip. . . . . . . . : Enabled=0A> > =0A> >> >=0A> >=0A>=
 > >> > -Dave=0A> > =0A> >> >=0A> > >> > >=0A> > -----Original =0A> Message=
-----=0A> > >> > > From: Hui Deng [mailto:> =0A> ymailto=3D"mailto:> href=
=3D"mailto:denghui02@gmail.com">denghui02@gmail.com"=0A> > =0A> href=3D"mai=
lto:> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com">> ymailto=3D=
"mailto:denghui02@gmail.com" =0A> href=3D"mailto:denghui02@gmail.com">dengh=
ui02@gmail.com]=0A> > >> =0A> >=0A> > > Sent: Monday, April 05, 2010 7:40 P=
M=0A> > =0A> >> > > To: Dan=0A> > Wing; Gabriel Montenegro; Dave =0A> Thale=
r=0A> > >> > > Cc: > ymailto=3D"mailto:> ymailto=3D"mailto:mif@ietf.org" =
=0A> href=3D"mailto:mif@ietf.org">mif@ietf.org"=0A> > href=3D"mailto:> ymai=
lto=3D"mailto:mif@ietf.org" href=3D"mailto:mif@ietf.org">mif@ietf.org">> ym=
ailto=3D"mailto:mif@ietf.org" =0A> href=3D"mailto:mif@ietf.org">mif@ietf.or=
g=0A> > >> > > =0A> Subject:=0A> > Re: [mif] draft-ietf-mif-current-practic=
es-00=0A> > =0A> >> > >=0A> >=0A> > >> > > DNS server =0A> always has speci=
fic interface related=0A> > information,=0A> > =0A> >> > > but the final DN=
S server will still be=0A> > host =0A> based, I=0A> > wouldn't say=0A> > >>=
 it=0A> > =0A> >> >=0A> > > is not correct.=0A> > >> > =0A> >=0A> > >> > > =
one=0A> > example would be you have =0A> internet connection and vpn=0A> > =
>>=0A> > =0A> connection=0A> > >> > > at the same time,=0A> > =0A> >> >=0A>=
 > > good VPN implementation will always rely on VPN =0A> DNS server=0A> > =
>>=0A> > > information=0A> > =0A> >> > > for Internet connection.=0A> >=0A>=
 > >> =0A> > >=0A> > >> > > -Hui=0A> > >> =0A> >=0A> > >=0A> > >> > > 2010/=
3/31 Dan Wing =0A> <> ymailto=3D"mailto:> href=3D"mailto:dwing@cisco.com">d=
wing@cisco.com"=0A> > href=3D"mailto:> ymailto=3D"mailto:dwing@cisco.com" =
=0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com">> ymailto=3D"mailto:d=
wing@cisco.com" =0A> href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:=0A> =
> >> =0A> >=0A> > > > Section 3.2.1.3 of describes the DNS =0A> configurati=
on=0A> > of=0A> > Windows,=0A> > >> =0A> and=0A> > >> > > says:=0A> > >>=0A=
> > =0A> > > >=0A> > >> > > > =A0"Interface specific =0A> DNS=0A> > configu=
ration can be input=0A> > via static=0A> > =0A> >> > > >=0A> > configuratio=
n or via DHCP. =A0It =0A> includes:=0A> > >> > > >=0A> >=0A> > =0A> >> > > =
> =A0 o =A0An interface-specific suffix list.=0A> > =0A> >>=0A> > > > >=0A>=
 > >> > > > =A0 o =A0A =0A> list of DNS server IP=0A> > addresses."=0A> > >=
> > > =0A> >=0A> > >> > > > It=0A> > is curious that the =0A> first bullet =
repeats "interface=0A> > >> >=0A> > =0A> specific", but=0A> > >> > > the=0A=
> > >> > =0A> > >=0A> > second bullet does not repeat it. =A0A reasonable=
=0A> =0A> > interpretation=0A> > is=0A> > >> > > that =0A> the=0A> > >> > >=
 > second=0A> > bullet is not =0A> interface-specific, but the=0A> > lead-i=
n sentence=0A> >=0A> =0A> > >> > > says this is=0A> > >> > > =0A> >=0A> > i=
nterface-specific. =A0I was hoping=0A> > >> =0A> >=0A> > draft-montenegro-m=
if-multihoming-00=0A> > >> > =0A> > would=0A> >=0A> > >> > > > clarify, but=
 it =0A> doesn't.=0A> > >> > >=0A> > >=0A> > >> =0A> > > > -d=0A> > >> > > =
>=0A> >=0A> > =0A> >> > > > _______________________________________________=
=0A> =0A> >=0A> > >> > > > mif mailing list=0A> > >> =0A> > > > > ymailto=
=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org"=0A> > href=3D"mailt=
o:> ymailto=3D"mailto:mif@ietf.org" href=3D"mailto:mif@ietf.org">mif@ietf.o=
rg">> ymailto=3D"mailto:mif@ietf.org" =0A> href=3D"mailto:mif@ietf.org">mif=
@ietf.org=0A> > >> > > > =0A> > href=3D"> >https://www.ietf.org/mailman/lis=
tinfo/mif"=0A> target=3D_blank=0A> =0A> > >> >https://www.ietf.org/mailman/=
listinfo/mif=0A> > >> > =0A> >=0A> > >=0A> > >> >=0A> > >>=0A> =0A> > >=0A>=
 >=0A> > >=0A> =0A> =0A> _______________________________________________=0A=
> mif mailing=0A> > =0A> list=0A> > href=3D"mailto:> href=3D"mailto:mif@iet=
f.org">mif@ietf.org">> href=3D"mailto:mif@ietf.org">mif@ietf.org=0A> > href=
=3D"> href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank =
=0A> >https://www.ietf.org/mailman/listinfo/mif" target=3D_blank=0A> > =0A>=
 >> >https://www.ietf.org/mailman/listinfo/mif=0A> =0A> ___________________=
____________________________=0A> mif mailing list=0A> =0A> > href=3D"mailto=
:mif@ietf.org">mif@ietf.org=0A> > href=3D"https://www.ietf.org/mailman/list=
info/mif" target=3D_blank =0A> >https://www.ietf.org/mailman/listinfo/mif

From denghui02@gmail.com  Mon Apr 12 17:58:08 2010
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 A13243A6AE3 for <mif@core3.amsl.com>; Mon, 12 Apr 2010 17:58:08 -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=[AWL=0.000,  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 3KtiKEACGwCC for <mif@core3.amsl.com>; Mon, 12 Apr 2010 17:58:07 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 5D3863A69B3 for <mif@ietf.org>; Mon, 12 Apr 2010 17:58:07 -0700 (PDT)
Received: by gyh4 with SMTP id 4so3263103gyh.31 for <mif@ietf.org>; Mon, 12 Apr 2010 17:57:58 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ryeYuGFSqj3XkJL964/RdcncOl1NjNTrllNW21UuGvI=; b=fcPP8yo5N5fCtb3LlfH1wAV50+/fU2kI4ddX/4x2WyNIwWRs5HbXusmbZzSakEiW4w caFtCBfuMWKixAB07NZ5SWuAfyDXE+ZzBaTsQTgItJlqdmyWvAIWqzG/H2JUiCUCO/Nh GvvJBqG337aD1Gwr302AUrPb1zRYkzkNHuWJ4=
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=d3Kh5pwYgeN/6zSRq8bFYfqx8eGl4OKw5rwYsjrUU+rMwlPBaaCrG3rPj0y4nyEEE4 mhCYiMDD+qSVJ0n7NJeqBYbHDO43s7dTfI2vDUcqX2TwyeiaQzAWK7h3+II7F+R98gE8 2oq+XZEp8IV8czpGJJ9vVYCVI+NoysgNcX1w8=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Mon, 12 Apr 2010 17:57:58 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AB47E4F@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com> <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47E4F@NALASEXMB04.na.qualcomm.com>
Date: Tue, 13 Apr 2010 08:57:58 +0800
Received: by 10.101.150.5 with SMTP id c5mr8296546ano.158.1271120278262; Mon,  12 Apr 2010 17:57:58 -0700 (PDT)
Message-ID: <y2v1d38a3351004121757nd3ceaafdx8802735dfedfcc25@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>, Margaret Wasserman <mrw@sandstorm.net>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 13 Apr 2010 00:58:08 -0000

Hi Julien

What I mean is I sent one email to clarify the AMSS/Brew several days ago
http://www.ietf.org/mail-archive/web/mif/current/msg00714.html
would like to clarify more detail before adding into the current practice d=
raft,

thanks

-Hui

2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:

2010/4/13 Laganier, Julien <julienl@qualcomm.com>:
> Hi Hui,
>
> I do not understand what is meant here. Can you clarify?
>
> Thanks.
>
> --julien
>
> Hui Deng wrote:
>>
>> Hi Julien
>>
>> As I asked the question yesterday,
>> it is expected that Qualcomm has more detail clarification about the
>> text,
>>
>> Regards,
>>
>> -Hui
>>
>>
>> 2010/4/10 Laganier, Julien <julienl@qualcomm.com>:
>> > Hi Margaret -
>> >
>> > I notice this text is not included in the current rev. of the current
>> practice draft. Are you going to include it?
>> >
>> > Thanks.
>> >
>> > --julien
>> >
>> >> -----Original Message-----
>> >> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf
>> Of
>> >> Margaret Wasserman
>> >> Sent: Sunday, August 16, 2009 7:04 AM
>> >> To: George Tsirtsis
>> >> Cc: mif
>> >> Subject: Re: [mif] AMSS/Brew Multi-interface handling
>> >>
>> >>
>> >> Hi George,
>> >>
>> >> Thanks for sending this!
>> >>
>> >> I'll add it to the next version of the draft.
>> >>
>> >> Margaret
>> >>
>> >> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
>> >>
>> >> > Hi all,
>> >> >
>> >> > I sent this to Margaret during the IETF meeting but I did not hear
>> >> > back from her. Maybe it got lost in the IETF noise so I thought I
>> >> > might as well forward this to the list.
>> >> >
>> >> > I hope it helps.
>> >> >
>> >> > George
>> >> >
>> >> > ---------- Forwarded message ----------
>> >> > From: George Tsirtsis <tsirtsis@googlemail.com>
>> >> > Date: Wed, Jul 29, 2009 at 9:58 AM
>> >> > Subject: AMSS/Brew Multi-interface handling
>> >> > To: mrw@sandstorm.net
>> >> >
>> >> >
>> >> > Hi Margaret,
>> >> >
>> >> > Here is a description of how multi-interface support is handled by
>> >> > Advanced Mobile Station Software (AMSS) that comes with Brew OS
>> for
>> >> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
>> >> > helpful information for draft-mrw-mif-current-practices.
>> >> >
>> >> > Let me know if you have any questions.
>> >> >
>> >> > Regards
>> >> > George Tsirtsis (wearing a Qualcomm hat)
>> >> >
>> >> > ------------------------------------------------------------------
>> ---
>> >> --------------------------------
>> >> >
>> >> >
>> >> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
>> >> >
>> >> > AMSS supports a concept of "netpolicy" which allows each
>> application
>> >> > to specify the type of network connectivity desired. =A0The
>> netpolicy
>> >> > contains parameters such as access technology, IP version type and
>> >> > network profile. =A0Access technology could be a specific technolog=
y
>> >> > type such as CDMA or WiFi or could be a group of technologies,
>> such
>> >> as
>> >> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4,
>> Ipv6
>> >> > or Default. =A0The network profile identifies a type of network
>> domain
>> >> > or service within a certain network technology, such as 3GPP APN
>> or
>> >> > Mobile IP Home Agent. =A0It also specifies all the mandatory
>> parameters
>> >> > required to connect to the domain such authentication credentials
>> and
>> >> > other optional parameters such as QoS attributes. =A0Network Profil=
e
>> is
>> >> > technology specific and set of parameters contained in the profile
>> >> > could vary for different technologies.
>> >> >
>> >> > Two models of network usage are supported.
>> >> >
>> >> > Applications requiring network connectivity specify an appropriate
>> >> > netpolicy in order to select the desired network. =A0The netpolicy
>> may
>> >> > match one or more network interfaces. =A0AMSS system selection
>> module
>> >> > selects the best interface out of the ones that match the
>> netpolicy
>> >> > based on various criteria such as cost, speed or other provisioned
>> >> > rules. =A0Application explicitly starts the selected network
>> interface
>> >> > and, as a result, the application also gets bound to the
>> >> corresponding
>> >> > network interface. =A0All outbound packets from this application ar=
e
>> >> > always routed over this bound interface using the source address
>> of
>> >> > the interface.
>> >> > Alternately, applications may rely on a separate connection
>> manager
>> >> to
>> >> > control (start/stop) the network interface. =A0 =A0In this method,
>> >> > applications are not necessarily bound to any one interface. =A0All
>> >> > outbound packets from such applications are routed on one of the
>> >> > interfaces that match its netpolicy. =A0The routing decision is mad=
e
>> >> > individually for each packet and =A0selects the best interface base=
d
>> on
>> >> > the criteria described above and the destination address. =A0 Sourc=
e
>> >> > address is always that assigned to the interface used to transmit
>> the
>> >> > packet.
>> >> >
>> >> > Note that all of the routing/interface selection decisions are
>> based
>> >> > on the netpolicy and not just destination address to avoid
>> >> overlapping
>> >> > private Ipv4 address issue. =A0This also allows multiple (logical)
>> >> > interfaces to be configured with the same IP address, for example,
>> to
>> >> > handle certain tunnelling scenarios. =A0 Applications that do not
>> >> > specify a netpolicy are routed by AMSS to the best possible
>> interface
>> >> > using the default netpolicy. =A0Default netpolicy could be pre-
>> defined
>> >> > or provisioned by the administrator or operator. =A0Hence default
>> >> > interface could vary from device to device and also depends upon
>> the
>> >> > available networks at any given time.
>> >> > AMSS allows each interface to be configured with its own set of
>> DNS
>> >> > configuration parameters - a list of DNS servers, domain names etc.
>> >> > Interface selected to make a DNS resolution is the one to which
>> >> > application making the DNS query is bound. =A0Applications can also
>> >> > specify a different netpolicy as part of DNS request to select
>> >> another
>> >> > interface for DNS resolution. =A0Regardless, all the DNS queries ar=
e
>> >> > sent only over this selected interface using the DNS configuration
>> >> > from the interface. =A0 DNS resolution is first attempted with the
>> >> > primary server configured in the interface. =A0If a response is not
>> >> > received, the queries are sent to all the other servers configured
>> in
>> >> > the interface in a sequential manner using a backoff mechanism.
>> >> > _______________________________________________
>> >> > mif mailing list
>> >> > mif@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/mif
>> >> >
>> >>
>> >> _______________________________________________
>> >> mif mailing list
>> >> mif@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/mif
>> > _______________________________________________
>> > mif mailing list
>> > mif@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mif
>> >
>

From teemu.savolainen@nokia.com  Mon Apr 12 22:57:02 2010
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 9702E3A6802 for <mif@core3.amsl.com>; Mon, 12 Apr 2010 22:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.857
X-Spam-Level: 
X-Spam-Status: No, score=-5.857 tagged_above=-999 required=5 tests=[AWL=0.559,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_OBFU_SPLIT_HR2=0.183]
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 UFpusTQP1oIa for <mif@core3.amsl.com>; Mon, 12 Apr 2010 22:57:00 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 9F6A43A6774 for <mif@ietf.org>; Mon, 12 Apr 2010 22:56:59 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o3D5ueAf029949; Tue, 13 Apr 2010 08:56:47 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 13 Apr 2010 08:56:29 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 13 Apr 2010 08:56:29 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 13 Apr 2010 08:56:24 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Tue, 13 Apr 2010 07:56:24 +0200
From: <teemu.savolainen@nokia.com>
To: <g_e_montenegro@yahoo.com>, <dwing@cisco.com>, <denghui02@gmail.com>, <dthaler@microsoft.com>
Date: Tue, 13 Apr 2010 07:56:22 +0200
Thread-Topic: [mif] draft-ietf-mif-current-practices-00
Thread-Index: AcralmXnV+Bbxj1GQhOb0jPGEtr30AANEQqg
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F726@NOK-EUMSG-01.mgdnok.nokia.com>
References: <044f01cad05d$22cdd090$c6f0200a@cisco.com> <n2h1d38a3351004051939m78d84b11qe9f58c4228886d2e@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF651392747A@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <07e201cad5ba$4d53eea0$7893150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF6513928B14@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <h2t1d38a3351004071928n8d88b955u5de0dfcd63a9f625@mail.gmail.com> <0f7701cad726$e8e28990$7893150a@cisco.com> <294720.31470.qm@web82601.mail.mud.yahoo.com> <18034D4D7FE9AE48BF19AB1B0EF2729F59D5D5F4FD@NOK-EUMSG-01.mgdnok.nokia.com> <350270.96614.qm@web82603.mail.mud.yahoo.com>
In-Reply-To: <350270.96614.qm@web82603.mail.mud.yahoo.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: 13 Apr 2010 05:56:24.0789 (UTC) FILETIME=[0CE45850:01CADACE]
X-Nokia-AV: Clean
Cc: mif@ietf.org
Subject: Re: [mif] draft-ietf-mif-current-practices-00
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, 13 Apr 2010 05:57:02 -0000

Gabriel,

>From my point of view NRPT is about (roaming) host simultaneously being con=
nected to multiple administrative domains..

What I'm after is that even if NRPT with DirectAccess is maybe closer to si=
ngle-interfaced host than multi-interfaced hosts (as a host can just have s=
ingle source IP address, and even if it has multiple, any one of those can =
be used with the globally unique IP address of NRPT matching destination, I=
 believe), very similar DNS things are in MIF domain, such as split-DNS.

With NRPT it is probably not possible for administrators of different acces=
s networks to configure (conflicting) rules to a host, but with a more gene=
ric option (see draft-savolainen-mif-dns-server-selection-02) and multiple =
interfaces there could be conflicting rules that need to be sorted out.

Therefore I'd just like to check whether you agree the namespaces/split-DNS=
 is in MIF scope generally, even if you say NRPT with DirectAccess would no=
t be?

Now, if a new DHCP-option would be defined as proposed, there could be conf=
lict between policies configured via DHCP (on attached network) and NRPT. I=
 think NRPT policies should override conflicting policies of access network=
s. I.e. the logic would be to check whether FQDN matches to NRPT, and then =
if it matches to any specific access network policies, and only then use th=
e "default" DNS server? What do you think?

Best regards,

Teemu

> -----Original Message-----
> From: ext gabriel montenegro [mailto:g_e_montenegro@yahoo.com]
> Sent: 13. huhtikuuta 2010 02:18
> To: Savolainen Teemu (Nokia-D/Tampere); dwing@cisco.com;
> denghui02@gmail.com; dthaler@microsoft.com
> Cc: mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
>
> Hi Teemu,
>
> I don't consider NRPT a MIF-specific technology as the whole point is
> to enable *namespace-specific DNS servers*, in addition to the well-
> known
> interface-specific DNS servers.
>
> Also, NRPT is not specific to DirectAccess. For example, it is also
> used for DNSSEC.
> Even when used for DirectAccess, it is even harder than with VPNs to
> consider
> it an "interface". For example, DirectAccess can use IPsec transport
> mode to access
> intranet resources. Whereas VPN's that use IPsec in tunnel mode are
> sometimes
> thought of as constituting an "interface", I'm not sure I've seen that
> for
> IPsec in *transport* mode.
>
> NRPT can be managed remotely by Group Policy.
>
> thanks,
>
> Gabriel
>
> ----- Original Message ----
> > From: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
> > To: g_e_montenegro@yahoo.com; dwing@cisco.com; denghui02@gmail.com;
> dthaler@microsoft.com
> > Cc: mif@ietf.org
> > Sent: Mon, April 12, 2010 1:52:55 PM
> > Subject: RE: [mif] draft-ietf-mif-current-practices-00
> >
> > Hi,
>
> Why do you think #4 is not mif-specific? What possible use NRPT has
> > for single interfaced host? Or is the idea such that a host could
> have single
> > interface, but just use different DNS server for queries matching
> > NRPT?
> ....hmm...
> Do you consider a host using DirectAccess single or
> > multi-interfaced? From my quick reading of the DirectAccess feature,
> it sounds
> > to be somewhere in between - not obviously multi-interface like the
> VPN-case is,
> > but not quite single-interfaced either.
>
> Is there a way to configure NRPT
> > policies remotely via some protocol?
>
> Thanks for
> > explanation,
>
> Teemu
>
> > -----Original Message-----
> > From:
> > > href=3D"mailto:mif-bounces@ietf.org">mif-bounces@ietf.org [mailto:>
> ymailto=3D"mailto:mif-bounces@ietf.org"
> > href=3D"mailto:mif-bounces@ietf.org">mif-bounces@ietf.org] On Behalf
> > Of
> > ext gabriel montenegro
> > Sent: 08. huhtikuuta 2010
> > 23:17
> > To: Dan Wing; Hui Deng; Dave Thaler
> > Cc: > ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > Subject: Re: [mif]
> > draft-ietf-mif-current-practices-00
> >
> > In addition to those three
> > usages of "suffix":
> >
> > 1. Domain Search list suffix
> > 2. For
> > interface-specific suffix list
> > 3. Suffix to control Dynamic
> > DNS Updates
> >
> > There is yet another usage in Windows introduced in
> > windows 7 and its
> > server counterpart, Windows Server 2008 R2:
> >
> >
> > 4. Suffix in the NRPT [1] to aid in identifying a Namespace
> > that
> > requires special handling,
> > as used for DirectAccess [2].
> > This is not MIF-specific either.
> >
> > Only #2 is MIF-specific (and
> > this should be called out), but it makes
> > sense to clarify the
> >
> > other uses of "suffix" otherwise #2 won't be clear.
> >
> > [1] NRPT:
> > See http://technet.microsoft.com/en-us/magazine/ff394369.aspx
> > [2]
> > DirectAcess: http://technet.microsoft.com/en-
> >
> > us/magazine/2009.05.cableguy.aspx
> >
> > Gabriel
> >
> >
> > ----- Original Message ----
> > > From: Dan Wing <> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>
> > > To: Hui Deng
> > <> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com>; Dave
> > Thaler
> > <> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>
> > >
> > Cc: > href=3D"mailto:mif@ietf.org">mif@ietf.org; Gabriel Montenegro <>
> ymailto=3D"mailto:gmonte@microsoft.com"
> > href=3D"mailto:gmonte@microsoft.com">gmonte@microsoft.com>
> > >
> > Sent: Thu, April 8, 2010 7:22:23 AM
> > > Subject: Re: [mif]
> > draft-ietf-mif-current-practices-00
> > >
> > >
> >
> >
> > > -----Original Message-----
> > > From: Hui Deng [mailto:>
> > ymailto=3D"mailto:>
> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com"
> > >
> > href=3D"mailto:>
> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com">>
> ymailto=3D"mailto:denghui02@gmail.com"
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > >
> > Sent:
> > > Wednesday, April 07, 2010 7:29 PM
> > > To: Dave
> > Thaler
> > > Cc: Dan Wing;
> > > Gabriel Montenegro; >
> > href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > Subject: Re:
> > [mif]
> > > draft-ietf-mif-current-practices-00
> > >
> > >
> > 2nd purpose has been
> > > documented in the current practice
> > draft,
> > > whether 1st and 3rd purpose
> > > need to be
> > documented as well? it may not
> > > directly related to
> > >
> > MIF?
> >
> > Some operating systems -- e.g., most flavors of Unix -- do
> > not
> > > support the
> > ability for sending different DNS queries
> > to different DNS
> > > servers.
> >
> > It would be helpful if
> > the draft more clearly described the
> > > functionality.
> > Someone
> > unfamiliar with the Windows functionality, reading the
> > > draft,
> > assumes
> > it is merely talking about the 'domain search list' --
> > because
> > > that is what
> > they are familiar with.
> >
> >
> > I don't care how the draft
> > > is fixed to make it clearer.  I
> > propose describing
> > the 2 (and, as Dave
> > > pointed out, 3)
> > functions.  If you want to adjust the
> > document to
> > > instead
> > talk about the per-interface stuff, that's great -- my
> > point is
> > that
> > > right now it is insufficiently clear in explaining it.
> >
> >
> > -d
> >
> > >
> > > -Hui
> > >
> > >
> > 2010/4/7 Dave Thaler <> ymailto=3D"mailto:>
> ymailto=3D"mailto:dthaler@microsoft.com"
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com"
> > >
> > href=3D"mailto:>
> href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com">>
> ymailto=3D"mailto:dthaler@microsoft.com"
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com>:
> >
> > >
> > > >> -----Original Message-----
> > > >>
> > From: Dan Wing [mailto:> ymailto=3D"mailto:>
> href=3D"mailto:dwing@cisco.com">dwing@cisco.com"
> > > href=3D"mailto:> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com">>
> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com]
> > > >>
> > Sent:
> > > Tuesday, April 06, 2010 11:52 AM
> > > >> To:
> > Dave Thaler; 'Hui Deng';
> > > Gabriel Montenegro
> > > >>
> > Cc: > href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> Subject: RE:
> > [mif]
> > > draft-ietf-mif-current-practices-00
> > >
> > >>
> > > >>
> > >
> > > >>
> > >
> > >> > -----Original Message-----
> > > >> >
> > >
> > From: Dave Thaler [mailto:>
> > href=3D"mailto:> ymailto=3D"mailto:dthaler@microsoft.com"
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com">>
> ymailto=3D"mailto:dthaler@microsoft.com"
> > href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com]
> > >
> > >>
> > > > Sent: Tuesday, April 06, 2010 10:06 AM
> > >
> > >> > To: Hui Deng;
> > > Dan Wing; Gabriel Montenegro
> >
> > > >> > Cc: > ymailto=3D"mailto:>
> href=3D"mailto:mif@ietf.org">mif@ietf.org"
> > > href=3D"mailto:> ymailto=3D"mailto:mif@ietf.org"
> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > Subject:
> > RE:
> > > [mif] draft-ietf-mif-current-practices-00
> > > >>
> > >
> > > >>
> > > > Hui is correct, Windows has
> > per-interface DNS server lists
> > > >>
> > >
> > configured.
> > > >> >
> > > >> > It then uses a
> > host-wide
> > > "effective" server list for an
> > > actual
> > query,
> > > >> >
> > > where the effective server list
> > may be different for
> > > different
> > > names.
> > >
> > >> >
> > > >> > On Windows the per-interface
> >
> > > suffix is actually termed the
> > > >> >
> > "connection-specific DNS
> > > suffix" to distinguish it from the
> >
> > > >> > "primary DNS suffix" of
> > > the machine.  I think
> > that's why
> > > >> > "interface-specific" was
> > >
> > repeated in the first bullet.
> > > >>
> > >
> > >>
> > >
> > > >>
> > > >> In
> > draft-montenegro-mif-multihoming, there are two
> > >
> > >
> > purposes and terms
> > > >> that
> > > >> seem to
> > be
> > > intermingled using the term "DNS suffix".
> > >
> > >>
> > > >> One
> > > purpose is the suffix for
> > non-FQDN names, like
> > > "payroll" or
> > > "mail",
> > >
> > >> which will have a suffix added to them (e.g., >
> > target=3D"_blank"
> > href=3D"http://example.com">> href=3D"http://example.com">example.com).
> > > >
> >
> > >
> > > > That's what windows calls the "DNS Suffix Search List"
> > (see the
> > >
> > > > sample output I sent previously below).
> >  It's called the
> > > >
> > > "domain search list" in other
> > places (like RFC 3397), or just
> > > >
> > > "search list"
> > (RFC 1123).
> > > >
> > > >> The
> > >
> > >>
> > > other purpose is deciding which DNS server will be be
> > sent
> > > a query
> > > for
> > > >> a certain FQDN
> > (e.g., queries for *.>
> > href=3D"http://example.net">> target=3D"_blank"
> href=3D"http://example.net">example.net go to one
> > >
> > DNS server
> > >
> > > >> and queries for *.example.com go
> > to a different DNS server).
> > >
> > > >
> > > >
> > Another purpose is deciding which DNS server will receive a
> > >
> > dynamic
> > > > update for a name with a certain suffix (e.g.,
> > Windows
> > >
> > > supports dynamic
> > > > updates for
> > the primary DNS name, and
> > > optionally also the
> > >
> > connection-
> > > > specific DNS name of the
> > >
> > machine).
> > > >
> > > >>
> > > >>
> >
> > > >> In
> > > draft-ietf-mif-current-practices-00, which is the
> > WG document
> > > >>
> > > that seems to have boiled down
> > draft-montenegro-mif-multihoming,
> > >
> > > >> but
> > draft-ietf-mif-current-practices-00 also does not clearly
> > >
> >
> > > >> separate the two purposes.
> > > >
> > > >
> > Yep
> > >
> > > >
> > > > -Dave
> > >
> > >>
> > > >> -d
> > >
> > > >>
> >
> > > >>
> > > >> > Example on Windows, extracted
> >
> > > from "ipconfig /all" output:
> > > >> >
> > >
> > >> > Windows
> > > IP Configuration
> > > >>
> > >
> > > >> >    Host Name . . .
> > > . . . . . . . .
> > . : dthaler-win7
> > > >> >    Primary Dns Suffix  .
> >
> > > . . . . . . : >
> > href=3D"http://ntdev.corp.microsoft.com">> target=3D"_blank"
> > href=3D"http://ntdev.corp.microsoft.com">ntdev.corp.microsoft.com
> >
> > >
> > > >> >
> > >
> >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >
> > >>
> > > >    Node Type . . . . . . . . . . . . : Hybrid
> >
> > > >> >    IP
> > > Routing Enabled. . . . . . . . :
> > No
> > > >> >    WINS Proxy Enabled.
> > > . . . . . . .
> > : No
> > > >> >    DNS Suffix Search List. . . . . . :
> >
> > > ntdev.corp.microsoft.com
> > > >> >
> > >
> >  >
> > href=3D"http://redmond.corp.microsoft.com">>
> href=3D"http://redmond.corp.microsoft.com">redmond.corp.microsoft.com
> >
> > >
> > > >> >
> >  >
> > href=3D"http://ntdev.microsoft.com">>
> href=3D"http://ntdev.microsoft.com">ntdev.microsoft.com
> > > >>
> > >
> > >                                        >
> >
> > href=3D"http://dns.corp.microsoft.com">>
> href=3D"http://dns.corp.microsoft.com">dns.corp.microsoft.com
> > >
> > >>
> > > >    System Quarantine State . . . . . : Not
> > Restricted
> > > >>
> > > >
> > > >> >
> > Wireless LAN adapter Wireless Network
> > > Connection:
> > >
> > >> >
> > > >> >    Connection-specific
> > > DNS
> > Suffix  . : >
> > href=3D"http://hsd1.wa.comcast.net">>
> href=3D"http://hsd1.wa.comcast.net">hsd1.wa.comcast.net.
> > > >>
> > >
> > >
> >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >
> > >>
> > > >    Description . . . . . . . . . . . : Intel(R)
> > Wireless WiFi
> > >
> > > >> > Link 4965AGN
> > >
> > >> >    Physical Address. . . . . .
> > > . . . :
> > 00-1D-E0-34-4F-6F
> > > >> >    DHCP Enabled. . . . . . . .
> > .
> > > . . : Yes
> > > >> >    Autoconfiguration Enabled
> > . . . . :
> > > Yes
> > > >> >    Link-local IPv6 Address
> > . . . . . :
> > >
> > > >> >
> > fe80::4853:4753:9d8d:3b45%13(Preferred)
> > > >> >
> > >
> >  IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
> > >
> > >>
> > > >    Subnet Mask . . . . . . . . . . . :
> > 255.255.255.0
> > > >> >
> > >    Lease Obtained. . . . .
> > . . . . . : Monday, April 05, 2010
> > > >>
> > > >
> > 10:19:02 PM
> > > >> >    Lease Expires . . . . . . . . . .
> > :
> > > Tuesday, April 06,
> > > >> > 2010 10:19:02
> > PM
> > > >> >
> > >    Default Gateway . . . . . . . . .
> > : 192.168.0.1
> > > >> >    DHCP
> > > Server . . . . . .
> > . . . . . : 192.168.0.1
> > > >> >    DHCPv6 IAID
> > > .
> > . . . . . . . . . . : 335551968
> > > >> >    DHCPv6 Client
> > DUID. .
> > > . . . . . . :
> > > >> >
> > >
> > 00-01-00-01-12-0C-E2-7A-00-1E-37-CC-8D-DD
> > > >> >
> >
> > > >>
> > > >    DNS Servers . . . . . . . . . . . :
> > 2001:df8:0:1::25
> > > >>
> > > >
> >                192.168.0.1
> > > >> >
> > >
> >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >>
> > >
> > >  NetBIOS over Tcpip. . . . . . . . : Enabled
> > >
> > >> >
> > >
> > > >> > -Dave
> > >
> > >> >
> > > >> > >
> > > -----Original
> > Message-----
> > > >> > > From: Hui Deng [mailto:>
> > ymailto=3D"mailto:>
> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com"
> > >
> > href=3D"mailto:>
> href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com">>
> ymailto=3D"mailto:denghui02@gmail.com"
> > href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com]
> > > >>
> > >
> > > > Sent: Monday, April 05, 2010 7:40 PM
> > >
> > >> > > To: Dan
> > > Wing; Gabriel Montenegro; Dave
> > Thaler
> > > >> > > Cc: > ymailto=3D"mailto:> ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org"
> > > href=3D"mailto:> ymailto=3D"mailto:mif@ietf.org"
> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > >
> > Subject:
> > > Re: [mif] draft-ietf-mif-current-practices-00
> > >
> > >> > >
> > >
> > > >> > > DNS server
> > always has specific interface related
> > > information,
> > >
> > >> > > but the final DNS server will still be
> > > host
> > based, I
> > > wouldn't say
> > > >> it
> > >
> > >> >
> > > > is not correct.
> > > >> >
> > >
> > > >> > > one
> > > example would be you have
> > internet connection and vpn
> > > >>
> > >
> > connection
> > > >> > > at the same time,
> > >
> > >> >
> > > > good VPN implementation will always rely on VPN
> > DNS server
> > > >>
> > > > information
> > >
> > >> > > for Internet connection.
> > >
> > > >>
> > > >
> > > >> > > -Hui
> > > >>
> > >
> > > >
> > > >> > > 2010/3/31 Dan Wing
> > <> ymailto=3D"mailto:> href=3D"mailto:dwing@cisco.com">dwing@cisco.com"
> > > href=3D"mailto:> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com">>
> ymailto=3D"mailto:dwing@cisco.com"
> > href=3D"mailto:dwing@cisco.com">dwing@cisco.com>:
> > > >>
> > >
> > > > > Section 3.2.1.3 of describes the DNS
> > configuration
> > > of
> > > Windows,
> > > >>
> > and
> > > >> > > says:
> > > >>
> > >
> > > > >
> > > >> > > >  "Interface specific
> > DNS
> > > configuration can be input
> > > via static
> > >
> > >> > > >
> > > configuration or via DHCP.  It
> > includes:
> > > >> > > >
> > >
> > >
> > >> > > >   o  An interface-specific suffix list.
> > >
> > >>
> > > > > >
> > > >> > > >   o  A
> > list of DNS server IP
> > > addresses."
> > > >> > >
> > >
> > > >> > > > It
> > > is curious that the
> > first bullet repeats "interface
> > > >> >
> > >
> > specific", but
> > > >> > > the
> > > >> >
> > > >
> > > second bullet does not repeat it.  A reasonable
> >
> > > interpretation
> > > is
> > > >> > > that
> > the
> > > >> > > > second
> > > bullet is not
> > interface-specific, but the
> > > lead-in sentence
> > >
> >
> > > >> > > says this is
> > > >> > >
> > >
> > > interface-specific.  I was hoping
> > > >>
> > >
> > > draft-montenegro-mif-multihoming-00
> > > >> >
> > > would
> > >
> > > >> > > > clarify, but it
> > doesn't.
> > > >> > >
> > > >
> > > >>
> > > > > -d
> > > >> > > >
> > >
> > >
> > >> > > > _______________________________________________
> >
> > >
> > > >> > > > mif mailing list
> > > >>
> > > > > > ymailto=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org"
> > > href=3D"mailto:> ymailto=3D"mailto:mif@ietf.org"
> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> ymailto=3D"mailto:mif@ietf.org"
> > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > >> > > >
> > > href=3D"> >https://www.ietf.org/mailman/listinfo/mif"
> > target=3D_blank
> >
> > > >> >https://www.ietf.org/mailman/listinfo/mif
> > > >> >
> > >
> > > >
> > > >> >
> > > >>
> >
> > > >
> > >
> > > >
> >
> >
> > _______________________________________________
> > mif mailing
> > >
> > list
> > > href=3D"mailto:> href=3D"mailto:mif@ietf.org">mif@ietf.org">>
> href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > href=3D"> href=3D"https://www.ietf.org/mailman/listinfo/mif"
> target=3D_blank
> > >https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
> > >
> > >> >https://www.ietf.org/mailman/listinfo/mif
> >
> > _______________________________________________
> > mif mailing list
> >
> > > href=3D"mailto:mif@ietf.org">mif@ietf.org
> > > href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D_blank
> > >https://www.ietf.org/mailman/listinfo/mif

From julienl@qualcomm.com  Tue Apr 13 13:27:36 2010
Return-Path: <julienl@qualcomm.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 8FF4928C1B7 for <mif@core3.amsl.com>; Tue, 13 Apr 2010 13:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.239
X-Spam-Level: 
X-Spam-Status: No, score=-106.239 tagged_above=-999 required=5 tests=[AWL=0.360, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RSfGelBfYCby for <mif@core3.amsl.com>; Tue, 13 Apr 2010 13:27:35 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 4AB1B28C1AD for <mif@ietf.org>; Tue, 13 Apr 2010 13:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1271190356; x=1302726356; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Hui=20Deng=20<denghui02@gmail.com>,=20George=20Tsi rtsis=20<tsirtsis@googlemail.com>|CC:=20mif=20<mif@ietf.o rg>|Date:=20Tue,=2013=20Apr=202010=2013:25:39=20-0700 |Subject:=20RE:=20[mif]=20AMSS/Brew=20Multi-interface=20h andling|Thread-Topic:=20[mif]=20AMSS/Brew=20Multi-interfa ce=20handling|Thread-Index:=20AcrX+b5/cR6Aye9sRouiNyKiU6e DagDTTDCw|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F 1C6AB47F1D@NALASEXMB04.na.qualcomm.com>|References:=20<d3 886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com >=0D=0A=09<d3886a520908160241k52ede41bpad57325a1c741f3b@m ail.gmail.com>=0D=0A=20<w2i1d38a3351004090831gc64ac111ia0 baf446f61e443f@mail.gmail.com>|In-Reply-To:=20<w2i1d38a33 51004090831gc64ac111ia0baf446f61e443f@mail.gmail.com> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"iso-8 859-1"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=cLimadpuNhWUYJB4/cP3TR+z3MI/0R22Td1Vl4OIMUk=; b=NKnm9L+Gu17WcoYQX8FaF+/9Ajmt0WCF7lNFkmJEF9riQ5nhKm3EX0Ok QH+Fsj4hTA7WFG80AHzF1C5S9RhiC8I2EEHgU6ZXu9S9r4IXjyn9J4HWo EvtVStsQrO+4ulZHcCOdzLPT+w3181tPposGWYr1myNtVe0RfVDmvlDp/ A=;
X-IronPort-AV: E=McAfee;i="5400,1158,5950"; a="38704266"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine01.qualcomm.com with ESMTP; 13 Apr 2010 13:25:40 -0700
X-IronPort-AV: E=Sophos;i="4.52,199,1270450800"; d="scan'208";a="13777058"
Received: from nasanexhub03.na.qualcomm.com ([10.46.93.98]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 13 Apr 2010 13:25:41 -0700
Received: from nalasexhc01.na.qualcomm.com (10.47.129.185) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 13 Apr 2010 13:25:41 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc01.na.qualcomm.com ([10.47.129.185]) with mapi; Tue, 13 Apr 2010 13:25:40 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Hui Deng <denghui02@gmail.com>, George Tsirtsis <tsirtsis@googlemail.com>
Date: Tue, 13 Apr 2010 13:25:39 -0700
Thread-Topic: [mif] AMSS/Brew Multi-interface handling
Thread-Index: AcrX+b5/cR6Aye9sRouiNyKiU6eDagDTTDCw
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com>
In-Reply-To: <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 13 Apr 2010 20:27:36 -0000

Hui Deng wrote:
>=20
> Hi, George,
>=20
> just two clarifications AMSS/Brew DNS configuration is
> interface based other than host based?

Quoting the text George sent:

   AMSS allows each interface to be configured with its own set of DNS=20
   configuration parameters - a list of DNS servers, domain names etc.
=20
> secondly, network profile could identify only APN other than PDP
> context?

Quoting the text George sent:=20

   The network profile identifies a type of network domain=20
   or service within a certain network technology, such as 3GPP APN or=20
   Mobile IP Home Agent.  It also specifies all the mandatory parameters=20
   required to connect to the domain such authentication credentials and=20
   other optional parameters such as QoS attributes.  Network Profile is=20
   technology specific and set of parameters contained in the profile=20
   could vary for different technologies.

--julien

> 2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:
> > Hi all,
> >
> > I sent this to Margaret during the IETF meeting but I did not hear
> > back from her. Maybe it got lost in the IETF noise so I thought I
> > might as well forward this to the list.
> >
> > I hope it helps.
> >
> > George
> >
> > ---------- Forwarded message ----------
> > From: George Tsirtsis <tsirtsis@googlemail.com>
> > Date: Wed, Jul 29, 2009 at 9:58 AM
> > Subject: AMSS/Brew Multi-interface handling
> > To: mrw@sandstorm.net
> >
> >
> > Hi Margaret,
> >
> > Here is a description of how multi-interface support is handled by
> > Advanced Mobile Station Software (AMSS) that comes with Brew OS for
> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
> > helpful information for draft-mrw-mif-current-practices.
> >
> > Let me know if you have any questions.
> >
> > Regards
> > George Tsirtsis (wearing a Qualcomm hat)
> >
> > ---------------------------------------------------------------------
> --------------------------------
> >
> >
> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
> >
> > AMSS supports a concept of "netpolicy" which allows each application
> > to specify the type of network connectivity desired. =A0The netpolicy
> > contains parameters such as access technology, IP version type and
> > network profile. =A0Access technology could be a specific technology
> > type such as CDMA or WiFi or could be a group of technologies, such
> as
> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4, Ipv6
> > or Default. =A0The network profile identifies a type of network domain
> > or service within a certain network technology, such as 3GPP APN or
> > Mobile IP Home Agent. =A0It also specifies all the mandatory parameters
> > required to connect to the domain such authentication credentials and
> > other optional parameters such as QoS attributes. =A0Network Profile is
> > technology specific and set of parameters contained in the profile
> > could vary for different technologies.
> >
> > Two models of network usage are supported.
> >
> > Applications requiring network connectivity specify an appropriate
> > netpolicy in order to select the desired network. =A0The netpolicy may
> > match one or more network interfaces. =A0AMSS system selection module
> > selects the best interface out of the ones that match the netpolicy
> > based on various criteria such as cost, speed or other provisioned
> > rules. =A0Application explicitly starts the selected network interface
> > and, as a result, the application also gets bound to the
> corresponding
> > network interface. =A0All outbound packets from this application are
> > always routed over this bound interface using the source address of
> > the interface.
> > Alternately, applications may rely on a separate connection manager
> to
> > control (start/stop) the network interface. =A0 =A0In this method,
> > applications are not necessarily bound to any one interface. =A0All
> > outbound packets from such applications are routed on one of the
> > interfaces that match its netpolicy. =A0The routing decision is made
> > individually for each packet and =A0selects the best interface based on
> > the criteria described above and the destination address. =A0 Source
> > address is always that assigned to the interface used to transmit the
> > packet.
> >
> > Note that all of the routing/interface selection decisions are based
> > on the netpolicy and not just destination address to avoid
> overlapping
> > private Ipv4 address issue. =A0This also allows multiple (logical)
> > interfaces to be configured with the same IP address, for example, to
> > handle certain tunnelling scenarios. =A0 Applications that do not
> > specify a netpolicy are routed by AMSS to the best possible interface
> > using the default netpolicy. =A0Default netpolicy could be pre-defined
> > or provisioned by the administrator or operator. =A0Hence default
> > interface could vary from device to device and also depends upon the
> > available networks at any given time.
> > AMSS allows each interface to be configured with its own set of DNS
> > configuration parameters - a list of DNS servers, domain names etc.
> > Interface selected to make a DNS resolution is the one to which
> > application making the DNS query is bound. =A0Applications can also
> > specify a different netpolicy as part of DNS request to select
> another
> > interface for DNS resolution. =A0Regardless, all the DNS queries are
> > sent only over this selected interface using the DNS configuration
> > from the interface. =A0 DNS resolution is first attempted with the
> > primary server configured in the interface. =A0If a response is not
> > received, the queries are sent to all the other servers configured in
> > the interface in a sequential manner using a backoff mechanism.
> > _______________________________________________
> > mif mailing list
> > mif@ietf.org
> > https://www.ietf.org/mailman/listinfo/mif
> >
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From julienl@qualcomm.com  Tue Apr 13 13:28:39 2010
Return-Path: <julienl@qualcomm.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 C63783A68EE for <mif@core3.amsl.com>; Tue, 13 Apr 2010 13:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.291
X-Spam-Level: 
X-Spam-Status: No, score=-106.291 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Mmy9LtSMuDBM for <mif@core3.amsl.com>; Tue, 13 Apr 2010 13:28:38 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id D9DFA28C16A for <mif@ietf.org>; Tue, 13 Apr 2010 13:28:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1271190480; x=1302726480; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Hui=20Deng=20<denghui02@gmail.com>|CC:=20Margaret =20Wasserman=20<mrw@sandstorm.net>,=20George=20Tsirtsis =0D=0A=09<tsirtsis@googlemail.com>,=20mif=20<mif@ietf.org >|Date:=20Tue,=2013=20Apr=202010=2013:27:59=20-0700 |Subject:=20RE:=20[mif]=20AMSS/Brew=20Multi-interface=20h andling|Thread-Topic:=20[mif]=20AMSS/Brew=20Multi-interfa ce=20handling|Thread-Index:=20AcrapF0EfuKzZLenSn2jZw4YycH 2TwAozCfA|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F 1C6AB47F1F@NALASEXMB04.na.qualcomm.com>|References:=20<d3 886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com >=0D=0A=09=20<d3886a520908160241k52ede41bpad57325a1c741f3 b@mail.gmail.com>=0D=0A=09=20<424FB149-AE77-4F63-9C18-EF0 4B2A20937@sandstorm.net>=0D=0A=09=20<BF345F63074F8040B58C 00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com>=0D=0A =09=20<s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@ma il.gmail.com>=0D=0A=09=20<BF345F63074F8040B58C00A186FCA57 F1C6AB47E4F@NALASEXMB04.na.qualcomm.com>=0D=0A=20<y2v1d38 a3351004121757nd3ceaafdx8802735dfedfcc25@mail.gmail.com> |In-Reply-To:=20<y2v1d38a3351004121757nd3ceaafdx8802735df edfcc25@mail.gmail.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"iso-8859-1" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=mEZaU+fQ1loQz7h0gwO9Ba6CP+y7Bja4vJOJYE/uxD8=; b=YQTEjskrrqRFfB+G/852N+ndpxlOjrvrL5Hm0M1QP47kzXS9IEXga/rC kV2fz4aNpfNTU+BzIRW40UaEs3kDdSJHaOt07Mo5Eh37en9xlv/jgfVJ9 FtAz1pzNVuGZ6jw3p4Q5gV32j4TAikYgo50KZJsp/Ifb4/wduSgFJCKdJ c=;
X-IronPort-AV: E=McAfee;i="5400,1158,5950"; a="38704410"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine01.qualcomm.com with ESMTP; 13 Apr 2010 13:28:00 -0700
X-IronPort-AV: E=Sophos;i="4.52,199,1270450800"; d="scan'208";a="13778087"
Received: from nasanexhub03.na.qualcomm.com ([10.46.93.98]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 13 Apr 2010 13:28:01 -0700
Received: from nalasexhub01.na.qualcomm.com (10.47.130.49) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 13 Apr 2010 13:28:01 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhub01.na.qualcomm.com ([10.47.130.49]) with mapi; Tue, 13 Apr 2010 13:28:00 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Hui Deng <denghui02@gmail.com>
Date: Tue, 13 Apr 2010 13:27:59 -0700
Thread-Topic: [mif] AMSS/Brew Multi-interface handling
Thread-Index: AcrapF0EfuKzZLenSn2jZw4YycH2TwAozCfA
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AB47F1F@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com> <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47E4F@NALASEXMB04.na.qualcomm.com> <y2v1d38a3351004121757nd3ceaafdx8802735dfedfcc25@mail.gmail.com>
In-Reply-To: <y2v1d38a3351004121757nd3ceaafdx8802735dfedfcc25@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mif <mif@ietf.org>, Margaret Wasserman <mrw@sandstorm.net>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 13 Apr 2010 20:28:39 -0000

I have replied to your other email; it's not clear to me what needs to be c=
larified.

--julien

Hui Deng wrote:
>=20
> Hi Julien
>=20
> What I mean is I sent one email to clarify the AMSS/Brew several days
> ago
> http://www.ietf.org/mail-archive/web/mif/current/msg00714.html
> would like to clarify more detail before adding into the current
> practice draft,
>=20
> thanks
>=20
> -Hui
>=20
> 2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:
>=20
> 2010/4/13 Laganier, Julien <julienl@qualcomm.com>:
> > Hi Hui,
> >
> > I do not understand what is meant here. Can you clarify?
> >
> > Thanks.
> >
> > --julien
> >
> > Hui Deng wrote:
> >>
> >> Hi Julien
> >>
> >> As I asked the question yesterday,
> >> it is expected that Qualcomm has more detail clarification about the
> >> text,
> >>
> >> Regards,
> >>
> >> -Hui
> >>
> >>
> >> 2010/4/10 Laganier, Julien <julienl@qualcomm.com>:
> >> > Hi Margaret -
> >> >
> >> > I notice this text is not included in the current rev. of the
> current
> >> practice draft. Are you going to include it?
> >> >
> >> > Thanks.
> >> >
> >> > --julien
> >> >
> >> >> -----Original Message-----
> >> >> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On
> Behalf
> >> Of
> >> >> Margaret Wasserman
> >> >> Sent: Sunday, August 16, 2009 7:04 AM
> >> >> To: George Tsirtsis
> >> >> Cc: mif
> >> >> Subject: Re: [mif] AMSS/Brew Multi-interface handling
> >> >>
> >> >>
> >> >> Hi George,
> >> >>
> >> >> Thanks for sending this!
> >> >>
> >> >> I'll add it to the next version of the draft.
> >> >>
> >> >> Margaret
> >> >>
> >> >> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
> >> >>
> >> >> > Hi all,
> >> >> >
> >> >> > I sent this to Margaret during the IETF meeting but I did not
> hear
> >> >> > back from her. Maybe it got lost in the IETF noise so I thought
> I
> >> >> > might as well forward this to the list.
> >> >> >
> >> >> > I hope it helps.
> >> >> >
> >> >> > George
> >> >> >
> >> >> > ---------- Forwarded message ----------
> >> >> > From: George Tsirtsis <tsirtsis@googlemail.com>
> >> >> > Date: Wed, Jul 29, 2009 at 9:58 AM
> >> >> > Subject: AMSS/Brew Multi-interface handling
> >> >> > To: mrw@sandstorm.net
> >> >> >
> >> >> >
> >> >> > Hi Margaret,
> >> >> >
> >> >> > Here is a description of how multi-interface support is handled
> by
> >> >> > Advanced Mobile Station Software (AMSS) that comes with Brew OS
> >> for
> >> >> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this
> is
> >> >> > helpful information for draft-mrw-mif-current-practices.
> >> >> >
> >> >> > Let me know if you have any questions.
> >> >> >
> >> >> > Regards
> >> >> > George Tsirtsis (wearing a Qualcomm hat)
> >> >> >
> >> >> > ---------------------------------------------------------------
> ---
> >> ---
> >> >> --------------------------------
> >> >> >
> >> >> >
> >> >> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile
> Platform
> >> >> >
> >> >> > AMSS supports a concept of "netpolicy" which allows each
> >> application
> >> >> > to specify the type of network connectivity desired. =A0The
> >> netpolicy
> >> >> > contains parameters such as access technology, IP version type
> and
> >> >> > network profile. =A0Access technology could be a specific
> technology
> >> >> > type such as CDMA or WiFi or could be a group of technologies,
> >> such
> >> >> as
> >> >> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4,
> >> Ipv6
> >> >> > or Default. =A0The network profile identifies a type of network
> >> domain
> >> >> > or service within a certain network technology, such as 3GPP
> APN
> >> or
> >> >> > Mobile IP Home Agent. =A0It also specifies all the mandatory
> >> parameters
> >> >> > required to connect to the domain such authentication
> credentials
> >> and
> >> >> > other optional parameters such as QoS attributes. =A0Network
> Profile
> >> is
> >> >> > technology specific and set of parameters contained in the
> profile
> >> >> > could vary for different technologies.
> >> >> >
> >> >> > Two models of network usage are supported.
> >> >> >
> >> >> > Applications requiring network connectivity specify an
> appropriate
> >> >> > netpolicy in order to select the desired network. =A0The
> netpolicy
> >> may
> >> >> > match one or more network interfaces. =A0AMSS system selection
> >> module
> >> >> > selects the best interface out of the ones that match the
> >> netpolicy
> >> >> > based on various criteria such as cost, speed or other
> provisioned
> >> >> > rules. =A0Application explicitly starts the selected network
> >> interface
> >> >> > and, as a result, the application also gets bound to the
> >> >> corresponding
> >> >> > network interface. =A0All outbound packets from this application
> are
> >> >> > always routed over this bound interface using the source
> address
> >> of
> >> >> > the interface.
> >> >> > Alternately, applications may rely on a separate connection
> >> manager
> >> >> to
> >> >> > control (start/stop) the network interface. =A0 =A0In this method=
,
> >> >> > applications are not necessarily bound to any one
> interface. =A0All
> >> >> > outbound packets from such applications are routed on one of
> the
> >> >> > interfaces that match its netpolicy. =A0The routing decision is
> made
> >> >> > individually for each packet and =A0selects the best interface
> based
> >> on
> >> >> > the criteria described above and the destination
> address. =A0 Source
> >> >> > address is always that assigned to the interface used to
> transmit
> >> the
> >> >> > packet.
> >> >> >
> >> >> > Note that all of the routing/interface selection decisions are
> >> based
> >> >> > on the netpolicy and not just destination address to avoid
> >> >> overlapping
> >> >> > private Ipv4 address issue. =A0This also allows multiple
> (logical)
> >> >> > interfaces to be configured with the same IP address, for
> example,
> >> to
> >> >> > handle certain tunnelling scenarios. =A0 Applications that do not
> >> >> > specify a netpolicy are routed by AMSS to the best possible
> >> interface
> >> >> > using the default netpolicy. =A0Default netpolicy could be pre-
> >> defined
> >> >> > or provisioned by the administrator or operator. =A0Hence default
> >> >> > interface could vary from device to device and also depends
> upon
> >> the
> >> >> > available networks at any given time.
> >> >> > AMSS allows each interface to be configured with its own set of
> >> DNS
> >> >> > configuration parameters - a list of DNS servers, domain names
> etc.
> >> >> > Interface selected to make a DNS resolution is the one to which
> >> >> > application making the DNS query is bound. =A0Applications can
> also
> >> >> > specify a different netpolicy as part of DNS request to select
> >> >> another
> >> >> > interface for DNS resolution. =A0Regardless, all the DNS queries
> are
> >> >> > sent only over this selected interface using the DNS
> configuration
> >> >> > from the interface. =A0 DNS resolution is first attempted with
> the
> >> >> > primary server configured in the interface. =A0If a response is
> not
> >> >> > received, the queries are sent to all the other servers
> configured
> >> in
> >> >> > the interface in a sequential manner using a backoff mechanism.
> >> >> > _______________________________________________
> >> >> > mif mailing list
> >> >> > mif@ietf.org
> >> >> > https://www.ietf.org/mailman/listinfo/mif
> >> >> >
> >> >>
> >> >> _______________________________________________
> >> >> mif mailing list
> >> >> mif@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/mif
> >> > _______________________________________________
> >> > mif mailing list
> >> > mif@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/mif
> >> >
> >

From denghui02@gmail.com  Tue Apr 13 18:58:32 2010
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 4BD2E3A6AE7 for <mif@core3.amsl.com>; Tue, 13 Apr 2010 18:58:32 -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 fzm0jfehjkrY for <mif@core3.amsl.com>; Tue, 13 Apr 2010 18:58:31 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 083B43A6839 for <mif@ietf.org>; Tue, 13 Apr 2010 18:58:30 -0700 (PDT)
Received: by gwb1 with SMTP id 1so2185128gwb.31 for <mif@ietf.org>; Tue, 13 Apr 2010 18:58:21 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2CaY2M4HKIGEkUEVxY3mraZtdX/vbMmH38iSJvFtbTI=; b=rn2uYYCKiniOsjsjPof7F/JYYbCm5lzBMlcbGZMK1/g+y7qy2E58UKTQ7sL0HPRUW3 C68HEeYMSNREsZ284tK7zRirhTmWcDuReiDzy3z51iTuxCeOz8eiWBDyEThb2itCB8p2 glHrDL40lMMQnOyqNkx7WRsoCefGyFJE0MpKM=
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=jQrOZAI/fRccXKTWDRLG2iviH7hZoyIlMCuzO+w0J985lik6m5jgHH5fC9vS86/7r8 MTxsDp8sXDy1Awu2l0tvvegQEv0+N7eqKN1vkFreSeS2w6QqYlKwAcQk8APbYzEA90Kq RTaY9kLgXbgqwBezZEJx+ez8EaBY0m8H121mo=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Tue, 13 Apr 2010 18:58:17 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcomm.com>
Date: Wed, 14 Apr 2010 09:58:17 +0800
Received: by 10.101.144.30 with SMTP id w30mr7536485ann.77.1271210297841; Tue,  13 Apr 2010 18:58:17 -0700 (PDT)
Message-ID: <g2m1d38a3351004131858t3f0b2aeax7c0a03d94f803ed6@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 14 Apr 2010 01:58:32 -0000

inline please,

2010/4/14 Laganier, Julien <julienl@qualcomm.com>:
> Hui Deng wrote:
>>
>> Hi, George,
>>
>> just two clarifications AMSS/Brew DNS configuration is
>> interface based other than host based?
>
> Quoting the text George sent:
>
> =A0 AMSS allows each interface to be configured with its own set of DNS
> =A0 configuration parameters - a list of DNS servers, domain names etc.
As you can see from the MIF discussion, even configuration could be
interface based,
but final DNS server selection could be host based, does AMSS/Brew
works similar?

>
>> secondly, network profile could identify only APN other than PDP
>> context?
>
> Quoting the text George sent:
>
> =A0 The network profile identifies a type of network domain
> =A0 or service within a certain network technology, such as 3GPP APN or
> =A0 Mobile IP Home Agent. =A0It also specifies all the mandatory paramete=
rs
> =A0 required to connect to the domain such authentication credentials and
> =A0 other optional parameters such as QoS attributes. =A0Network Profile =
is
> =A0 technology specific and set of parameters contained in the profile
> =A0 could vary for different technologies.
wifi has two type connections:connected through APN, or directed
connected with Internet
assume you have 3G+Wifi Connections,
in your profile, it would be the same APN for 3G and Wfi, then you
have to rely on access type?
but access type will differentiate 3g and wifi.
So who will be high priority? access type or APN(profile).

thanks for your clarification.

-Hui

>
> --julien
>
>> 2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:
>> > Hi all,
>> >
>> > I sent this to Margaret during the IETF meeting but I did not hear
>> > back from her. Maybe it got lost in the IETF noise so I thought I
>> > might as well forward this to the list.
>> >
>> > I hope it helps.
>> >
>> > George
>> >
>> > ---------- Forwarded message ----------
>> > From: George Tsirtsis <tsirtsis@googlemail.com>
>> > Date: Wed, Jul 29, 2009 at 9:58 AM
>> > Subject: AMSS/Brew Multi-interface handling
>> > To: mrw@sandstorm.net
>> >
>> >
>> > Hi Margaret,
>> >
>> > Here is a description of how multi-interface support is handled by
>> > Advanced Mobile Station Software (AMSS) that comes with Brew OS for
>> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is
>> > helpful information for draft-mrw-mif-current-practices.
>> >
>> > Let me know if you have any questions.
>> >
>> > Regards
>> > George Tsirtsis (wearing a Qualcomm hat)
>> >
>> > ---------------------------------------------------------------------
>> --------------------------------
>> >
>> >
>> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform
>> >
>> > AMSS supports a concept of "netpolicy" which allows each application
>> > to specify the type of network connectivity desired. =A0The netpolicy
>> > contains parameters such as access technology, IP version type and
>> > network profile. =A0Access technology could be a specific technology
>> > type such as CDMA or WiFi or could be a group of technologies, such
>> as
>> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4, Ipv6
>> > or Default. =A0The network profile identifies a type of network domain
>> > or service within a certain network technology, such as 3GPP APN or
>> > Mobile IP Home Agent. =A0It also specifies all the mandatory parameter=
s
>> > required to connect to the domain such authentication credentials and
>> > other optional parameters such as QoS attributes. =A0Network Profile i=
s
>> > technology specific and set of parameters contained in the profile
>> > could vary for different technologies.
>> >
>> > Two models of network usage are supported.
>> >
>> > Applications requiring network connectivity specify an appropriate
>> > netpolicy in order to select the desired network. =A0The netpolicy may
>> > match one or more network interfaces. =A0AMSS system selection module
>> > selects the best interface out of the ones that match the netpolicy
>> > based on various criteria such as cost, speed or other provisioned
>> > rules. =A0Application explicitly starts the selected network interface
>> > and, as a result, the application also gets bound to the
>> corresponding
>> > network interface. =A0All outbound packets from this application are
>> > always routed over this bound interface using the source address of
>> > the interface.
>> > Alternately, applications may rely on a separate connection manager
>> to
>> > control (start/stop) the network interface. =A0 =A0In this method,
>> > applications are not necessarily bound to any one interface. =A0All
>> > outbound packets from such applications are routed on one of the
>> > interfaces that match its netpolicy. =A0The routing decision is made
>> > individually for each packet and =A0selects the best interface based o=
n
>> > the criteria described above and the destination address. =A0 Source
>> > address is always that assigned to the interface used to transmit the
>> > packet.
>> >
>> > Note that all of the routing/interface selection decisions are based
>> > on the netpolicy and not just destination address to avoid
>> overlapping
>> > private Ipv4 address issue. =A0This also allows multiple (logical)
>> > interfaces to be configured with the same IP address, for example, to
>> > handle certain tunnelling scenarios. =A0 Applications that do not
>> > specify a netpolicy are routed by AMSS to the best possible interface
>> > using the default netpolicy. =A0Default netpolicy could be pre-defined
>> > or provisioned by the administrator or operator. =A0Hence default
>> > interface could vary from device to device and also depends upon the
>> > available networks at any given time.
>> > AMSS allows each interface to be configured with its own set of DNS
>> > configuration parameters - a list of DNS servers, domain names etc.
>> > Interface selected to make a DNS resolution is the one to which
>> > application making the DNS query is bound. =A0Applications can also
>> > specify a different netpolicy as part of DNS request to select
>> another
>> > interface for DNS resolution. =A0Regardless, all the DNS queries are
>> > sent only over this selected interface using the DNS configuration
>> > from the interface. =A0 DNS resolution is first attempted with the
>> > primary server configured in the interface. =A0If a response is not
>> > received, the queries are sent to all the other servers configured in
>> > the interface in a sequential manner using a backoff mechanism.
>> > _______________________________________________
>> > mif mailing list
>> > mif@ietf.org
>> > https://www.ietf.org/mailman/listinfo/mif
>> >
>> _______________________________________________
>> mif mailing list
>> mif@ietf.org
>> https://www.ietf.org/mailman/listinfo/mif
>

From denghui02@gmail.com  Tue Apr 13 18:59:14 2010
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 B5C5D3A6AE9 for <mif@core3.amsl.com>; Tue, 13 Apr 2010 18:59:14 -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=[AWL=0.000,  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 VlJMoE1NTigP for <mif@core3.amsl.com>; Tue, 13 Apr 2010 18:59:13 -0700 (PDT)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id 3B0853A6AE7 for <mif@ietf.org>; Tue, 13 Apr 2010 18:59:13 -0700 (PDT)
Received: by gxk9 with SMTP id 9so4526260gxk.8 for <mif@ietf.org>; Tue, 13 Apr 2010 18:59:04 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=voadBYnIITFcPmCPBCLWAZrO1ytp1ts6NIMtaGnP6Uo=; b=j5qYrBlX/L7FpqzK68cicZlfhr2Za2ZcSL2Hea8/BoZIuZoba3V6H6egWd5X7sJ+To JhA8FuO3DcQ5vzUXQwP57MXcKDJ6Abt5c77yRw5kyed9vPnjpW2nRxBDqI0VPSALMWdt u7UsTN16s1uEVEMZ89iYno7LSbHLQdNVJeUS4=
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=bT/2Fr6yWWKYCYP2tMCKZtUr70YoDwVwRHE7/eQutlZ9vT1a26b6sJ1zUZQZvvJXJb K8km0MV2zqlO5/vnSUgTeAAUcs0/Si1/3MEB+7HB7UMbNq/xio0yrUpsYM/NXHLxghbr JB0CSGGxGJmJCv/6olyaYPS2/pdvRoVly2G/Y=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Tue, 13 Apr 2010 18:59:04 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AB47F1F@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <424FB149-AE77-4F63-9C18-EF04B2A20937@sandstorm.net> <BF345F63074F8040B58C00A186FCA57F1C6AB47D62@NALASEXMB04.na.qualcomm.com> <s2u1d38a3351004100557i3b4b7027r395b6e306ced299a@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47E4F@NALASEXMB04.na.qualcomm.com> <y2v1d38a3351004121757nd3ceaafdx8802735dfedfcc25@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47F1F@NALASEXMB04.na.qualcomm.com>
Date: Wed, 14 Apr 2010 09:59:04 +0800
Received: by 10.100.39.20 with SMTP id m20mr11923084anm.110.1271210344431;  Tue, 13 Apr 2010 18:59:04 -0700 (PDT)
Message-ID: <r2j1d38a3351004131859v4c4c9e5r13909bc8766e2b8c@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>, Margaret Wasserman <mrw@sandstorm.net>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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, 14 Apr 2010 01:59:14 -0000

I have explained as well, hope it clarify the question.

-Hui

2010/4/14 Laganier, Julien <julienl@qualcomm.com>:
> I have replied to your other email; it's not clear to me what needs to be=
 clarified.
>
> --julien
>
> Hui Deng wrote:
>>
>> Hi Julien
>>
>> What I mean is I sent one email to clarify the AMSS/Brew several days
>> ago
>> http://www.ietf.org/mail-archive/web/mif/current/msg00714.html
>> would like to clarify more detail before adding into the current
>> practice draft,
>>
>> thanks
>>
>> -Hui
>>
>> 2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>:
>>
>> 2010/4/13 Laganier, Julien <julienl@qualcomm.com>:
>> > Hi Hui,
>> >
>> > I do not understand what is meant here. Can you clarify?
>> >
>> > Thanks.
>> >
>> > --julien
>> >
>> > Hui Deng wrote:
>> >>
>> >> Hi Julien
>> >>
>> >> As I asked the question yesterday,
>> >> it is expected that Qualcomm has more detail clarification about the
>> >> text,
>> >>
>> >> Regards,
>> >>
>> >> -Hui
>> >>
>> >>
>> >> 2010/4/10 Laganier, Julien <julienl@qualcomm.com>:
>> >> > Hi Margaret -
>> >> >
>> >> > I notice this text is not included in the current rev. of the
>> current
>> >> practice draft. Are you going to include it?
>> >> >
>> >> > Thanks.
>> >> >
>> >> > --julien
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On
>> Behalf
>> >> Of
>> >> >> Margaret Wasserman
>> >> >> Sent: Sunday, August 16, 2009 7:04 AM
>> >> >> To: George Tsirtsis
>> >> >> Cc: mif
>> >> >> Subject: Re: [mif] AMSS/Brew Multi-interface handling
>> >> >>
>> >> >>
>> >> >> Hi George,
>> >> >>
>> >> >> Thanks for sending this!
>> >> >>
>> >> >> I'll add it to the next version of the draft.
>> >> >>
>> >> >> Margaret
>> >> >>
>> >> >> On Aug 16, 2009, at 5:41 AM, George Tsirtsis wrote:
>> >> >>
>> >> >> > Hi all,
>> >> >> >
>> >> >> > I sent this to Margaret during the IETF meeting but I did not
>> hear
>> >> >> > back from her. Maybe it got lost in the IETF noise so I thought
>> I
>> >> >> > might as well forward this to the list.
>> >> >> >
>> >> >> > I hope it helps.
>> >> >> >
>> >> >> > George
>> >> >> >
>> >> >> > ---------- Forwarded message ----------
>> >> >> > From: George Tsirtsis <tsirtsis@googlemail.com>
>> >> >> > Date: Wed, Jul 29, 2009 at 9:58 AM
>> >> >> > Subject: AMSS/Brew Multi-interface handling
>> >> >> > To: mrw@sandstorm.net
>> >> >> >
>> >> >> >
>> >> >> > Hi Margaret,
>> >> >> >
>> >> >> > Here is a description of how multi-interface support is handled
>> by
>> >> >> > Advanced Mobile Station Software (AMSS) that comes with Brew OS
>> >> for
>> >> >> > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this
>> is
>> >> >> > helpful information for draft-mrw-mif-current-practices.
>> >> >> >
>> >> >> > Let me know if you have any questions.
>> >> >> >
>> >> >> > Regards
>> >> >> > George Tsirtsis (wearing a Qualcomm hat)
>> >> >> >
>> >> >> > ---------------------------------------------------------------
>> ---
>> >> ---
>> >> >> --------------------------------
>> >> >> >
>> >> >> >
>> >> >> > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile
>> Platform
>> >> >> >
>> >> >> > AMSS supports a concept of "netpolicy" which allows each
>> >> application
>> >> >> > to specify the type of network connectivity desired. =A0The
>> >> netpolicy
>> >> >> > contains parameters such as access technology, IP version type
>> and
>> >> >> > network profile. =A0Access technology could be a specific
>> technology
>> >> >> > type such as CDMA or WiFi or could be a group of technologies,
>> >> such
>> >> >> as
>> >> >> > ANY_Cellular or ANY_Wireless. =A0IP version could be one of Ipv4=
,
>> >> Ipv6
>> >> >> > or Default. =A0The network profile identifies a type of network
>> >> domain
>> >> >> > or service within a certain network technology, such as 3GPP
>> APN
>> >> or
>> >> >> > Mobile IP Home Agent. =A0It also specifies all the mandatory
>> >> parameters
>> >> >> > required to connect to the domain such authentication
>> credentials
>> >> and
>> >> >> > other optional parameters such as QoS attributes. =A0Network
>> Profile
>> >> is
>> >> >> > technology specific and set of parameters contained in the
>> profile
>> >> >> > could vary for different technologies.
>> >> >> >
>> >> >> > Two models of network usage are supported.
>> >> >> >
>> >> >> > Applications requiring network connectivity specify an
>> appropriate
>> >> >> > netpolicy in order to select the desired network. =A0The
>> netpolicy
>> >> may
>> >> >> > match one or more network interfaces. =A0AMSS system selection
>> >> module
>> >> >> > selects the best interface out of the ones that match the
>> >> netpolicy
>> >> >> > based on various criteria such as cost, speed or other
>> provisioned
>> >> >> > rules. =A0Application explicitly starts the selected network
>> >> interface
>> >> >> > and, as a result, the application also gets bound to the
>> >> >> corresponding
>> >> >> > network interface. =A0All outbound packets from this application
>> are
>> >> >> > always routed over this bound interface using the source
>> address
>> >> of
>> >> >> > the interface.
>> >> >> > Alternately, applications may rely on a separate connection
>> >> manager
>> >> >> to
>> >> >> > control (start/stop) the network interface. =A0 =A0In this metho=
d,
>> >> >> > applications are not necessarily bound to any one
>> interface. =A0All
>> >> >> > outbound packets from such applications are routed on one of
>> the
>> >> >> > interfaces that match its netpolicy. =A0The routing decision is
>> made
>> >> >> > individually for each packet and =A0selects the best interface
>> based
>> >> on
>> >> >> > the criteria described above and the destination
>> address. =A0 Source
>> >> >> > address is always that assigned to the interface used to
>> transmit
>> >> the
>> >> >> > packet.
>> >> >> >
>> >> >> > Note that all of the routing/interface selection decisions are
>> >> based
>> >> >> > on the netpolicy and not just destination address to avoid
>> >> >> overlapping
>> >> >> > private Ipv4 address issue. =A0This also allows multiple
>> (logical)
>> >> >> > interfaces to be configured with the same IP address, for
>> example,
>> >> to
>> >> >> > handle certain tunnelling scenarios. =A0 Applications that do no=
t
>> >> >> > specify a netpolicy are routed by AMSS to the best possible
>> >> interface
>> >> >> > using the default netpolicy. =A0Default netpolicy could be pre-
>> >> defined
>> >> >> > or provisioned by the administrator or operator. =A0Hence defaul=
t
>> >> >> > interface could vary from device to device and also depends
>> upon
>> >> the
>> >> >> > available networks at any given time.
>> >> >> > AMSS allows each interface to be configured with its own set of
>> >> DNS
>> >> >> > configuration parameters - a list of DNS servers, domain names
>> etc.
>> >> >> > Interface selected to make a DNS resolution is the one to which
>> >> >> > application making the DNS query is bound. =A0Applications can
>> also
>> >> >> > specify a different netpolicy as part of DNS request to select
>> >> >> another
>> >> >> > interface for DNS resolution. =A0Regardless, all the DNS queries
>> are
>> >> >> > sent only over this selected interface using the DNS
>> configuration
>> >> >> > from the interface. =A0 DNS resolution is first attempted with
>> the
>> >> >> > primary server configured in the interface. =A0If a response is
>> not
>> >> >> > received, the queries are sent to all the other servers
>> configured
>> >> in
>> >> >> > the interface in a sequential manner using a backoff mechanism.
>> >> >> > _______________________________________________
>> >> >> > mif mailing list
>> >> >> > mif@ietf.org
>> >> >> > https://www.ietf.org/mailman/listinfo/mif
>> >> >> >
>> >> >>
>> >> >> _______________________________________________
>> >> >> mif mailing list
>> >> >> mif@ietf.org
>> >> >> https://www.ietf.org/mailman/listinfo/mif
>> >> > _______________________________________________
>> >> > mif mailing list
>> >> > mif@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/mif
>> >> >
>> >
>

From julienl@qualcomm.com  Fri Apr 16 17:43:02 2010
Return-Path: <julienl@qualcomm.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 817DD3A6AA1 for <mif@core3.amsl.com>; Fri, 16 Apr 2010 17:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.472
X-Spam-Level: 
X-Spam-Status: No, score=-106.472 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 TA1v7qMrtpzD for <mif@core3.amsl.com>; Fri, 16 Apr 2010 17:43:01 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 4A18C3A6A9F for <mif@ietf.org>; Fri, 16 Apr 2010 17:43:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1271464974; x=1303000974; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Hui=20Deng=20<denghui02@gmail.com>|CC:=20George=20 Tsirtsis=20<tsirtsis@googlemail.com>,=20mif=20<mif@ietf.o rg>|Date:=20Fri,=2016=20Apr=202010=2017:42:53=20-0700 |Subject:=20RE:=20[mif]=20AMSS/Brew=20Multi-interface=20h andling|Thread-Topic:=20[mif]=20AMSS/Brew=20Multi-interfa ce=20handling|Thread-Index:=20Acrbdf2uZwf+PBKJR72R9VJC7ts 5zQCTjYZQ|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F 1C6AB48285@NALASEXMB04.na.qualcomm.com>|References:=20<d3 886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com >=0D=0A=09=20<d3886a520908160241k52ede41bpad57325a1c741f3 b@mail.gmail.com>=0D=0A=09=20<w2i1d38a3351004090831gc64ac 111ia0baf446f61e443f@mail.gmail.com>=0D=0A=09=20<BF345F63 074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcom m.com>=0D=0A=20<g2m1d38a3351004131858t3f0b2aeax7c0a03d94f 803ed6@mail.gmail.com>|In-Reply-To:=20<g2m1d38a3351004131 858t3f0b2aeax7c0a03d94f803ed6@mail.gmail.com> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"iso-8 859-1"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=LZ3EJnVy9fWisbjP+e7ElrgWxHVoSl0gtPL/aJoWxFo=; b=W4kFQ2ZbLxpWMcywugVKLwz0vy3vVapHIEe4uYNSOZHJT9dRNFYdLDZ0 VADlZjBUjj3FwLQJSrTQiEtgG5flp4GecLt54WjVylcP8Rz1ImJUgHZJE 4DsCqQf5EpMPsdTSPSxRBDICBm/TcucyNTsiVsjCnyLErgEEpuOBHJTBO g=;
X-IronPort-AV: E=McAfee;i="5400,1158,5953"; a="38956369"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine02.qualcomm.com with ESMTP; 16 Apr 2010 17:42:54 -0700
X-IronPort-AV: E=Sophos;i="4.52,221,1270450800"; d="scan'208";a="16461549"
Received: from nasanexhub05.na.qualcomm.com ([129.46.134.219]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 16 Apr 2010 17:42:53 -0700
Received: from nalasexhc01.na.qualcomm.com (10.47.129.185) by nasanexhub05.na.qualcomm.com (129.46.134.219) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 16 Apr 2010 17:42:53 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc01.na.qualcomm.com ([10.47.129.185]) with mapi; Fri, 16 Apr 2010 17:42:53 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Hui Deng <denghui02@gmail.com>
Date: Fri, 16 Apr 2010 17:42:53 -0700
Thread-Topic: [mif] AMSS/Brew Multi-interface handling
Thread-Index: Acrbdf2uZwf+PBKJR72R9VJC7ts5zQCTjYZQ
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AB48285@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcomm.com> <g2m1d38a3351004131858t3f0b2aeax7c0a03d94f803ed6@mail.gmail.com>
In-Reply-To: <g2m1d38a3351004131858t3f0b2aeax7c0a03d94f803ed6@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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 Apr 2010 00:43:02 -0000

Hello Hui,

Pls. see inline:

Hui Deng wrote:
>=20
> inline please,
>=20
> 2010/4/14 Laganier, Julien <julienl@qualcomm.com>:
> > Hui Deng wrote:
> >>
> >> Hi, George,
> >>
> >> just two clarifications AMSS/Brew DNS configuration is
> >> interface based other than host based?
> >
> > Quoting the text George sent:
> >
> > =A0 AMSS allows each interface to be configured with its own set of DNS
> > =A0 configuration parameters - a list of DNS servers, domain names etc.
>
> As you can see from the MIF discussion, even configuration could be
> interface based, but final DNS server selection could be host based,=20
> does AMSS/Brew works similar?

Quoting the text George sent:

> Interface selected to make a DNS resolution is the one to which=20
> application making the DNS query is bound.  Applications can also=20
> specify a different netpolicy as part of DNS request to select another
> interface for DNS resolution.  Regardless, all the DNS queries are=20
> sent only over this selected interface using the DNS configuration
> from the interface.

This seems to answer your question, doesn't it?
=20
> >> secondly, network profile could identify only APN other than PDP
> >> context?
> >
> > Quoting the text George sent:
> >
> > =A0 The network profile identifies a type of network domain
> > =A0 or service within a certain network technology, such as 3GPP APN or
> > =A0 Mobile IP Home Agent. =A0It also specifies all the mandatory parame=
ters
> > =A0 required to connect to the domain such authentication credentials
> > =A0 and other optional parameters such as QoS attributes. =A0Network Pr=
ofile
> > =A0 is technology specific and set of parameters contained in the profi=
le
> > =A0 could vary for different technologies.
>
> wifi has two type connections:connected through APN, or directed
> connected with Internet
> assume you have 3G+Wifi Connections,
> in your profile, it would be the same APN for 3G and Wfi, then you
> have to rely on access type?
> but access type will differentiate 3g and wifi.
> So who will be high priority? access type or APN(profile).

I am not sure I follow you. Let me try to sketch what happens:

An application specifying an APN in its network profile means that it desir=
e to connect to the PDN named by this APN.=20

As a result, only interfaces connecting to that APN will be selected, which=
 rules out WiFi by itself and keeps in 3G, and any of the 3GPP accesses ove=
r WiFi (such as 3GPP I-WLAN or either of the various non-3GPP accesses over=
 S2a/b/c interfaces.)

If the application has specified a preference for an ANY_Cellular access te=
chnology (or say HSDPA) then 3G will be selected, if the application has sp=
ecified a preference for an ANY_Wireless access technology (or say IEEE 802=
.11) the 3GPP I-WLAN application will be selected. If the application hasn'=
t specified anything, the default access will be selected.

Does the above clarify the situation?

--julien

From denghui02@gmail.com  Tue Apr 20 08:49:34 2010
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 8E9B63A6B21 for <mif@core3.amsl.com>; Tue, 20 Apr 2010 08:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930,  BAYES_20=-0.74]
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 vujyXD1Hgabf for <mif@core3.amsl.com>; Tue, 20 Apr 2010 08:49:33 -0700 (PDT)
Received: from mail-pz0-f191.google.com (mail-pz0-f191.google.com [209.85.222.191]) by core3.amsl.com (Postfix) with ESMTP id 16E0D3A6B07 for <mif@ietf.org>; Tue, 20 Apr 2010 08:49:33 -0700 (PDT)
Received: by pzk29 with SMTP id 29so5254647pzk.29 for <mif@ietf.org>; Tue, 20 Apr 2010 08:49:22 -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:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=l48UsPAgo5yRjcIkY69Dla2J5NkfW8bqJdaic7Jaslg=; b=cAafTJc/CGCYibDreWUJ7Npb7jB1hxRAWVkmwhNBY/vS/3nvtRYCBr023g3/p7Yt3n Eycbwje+/D4up/AR9Gssgq4OQupmkdya0LZGoGLUcgdcTyHi+jbKC+/j1myo7uX/9rjY XaSihe8L+1O5v83N6wD3tQj6uTDL+ikfvGFZg=
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=Ud0N3cs2D6DECAK6kGta7m5WdhISOiIgFs0/q3jPTrSg29UjgUNpViQPrL+cEW5iW0 aMUzHSJsWlheYOXFySm9U1n3kvjCO/va82NtNWpat0SaLui6LwlQpnZwwZ0yf9ofbduw kIGoJHh+3M+TENhhQLx0MUruzG3d7efFczeTo=
MIME-Version: 1.0
Received: by 10.231.152.10 with HTTP; Tue, 20 Apr 2010 08:49:21 -0700 (PDT)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AB48285@NALASEXMB04.na.qualcomm.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com> <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB47F1D@NALASEXMB04.na.qualcomm.com> <g2m1d38a3351004131858t3f0b2aeax7c0a03d94f803ed6@mail.gmail.com> <BF345F63074F8040B58C00A186FCA57F1C6AB48285@NALASEXMB04.na.qualcomm.com>
Date: Tue, 20 Apr 2010 23:49:21 +0800
Received: by 10.114.33.18 with SMTP id g18mr5889290wag.2.1271778561787; Tue,  20 Apr 2010 08:49:21 -0700 (PDT)
Message-ID: <q2u1d38a3351004200849v70db43b2p1f586473a82540f8@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
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 Apr 2010 15:49:34 -0000

Hello Julien,

inline please

2010/4/17 Laganier, Julien <julienl@qualcomm.com>:
> Hello Hui,
>
> Pls. see inline:
>
> Hui Deng wrote:
>>
>> inline please,
>>
>> 2010/4/14 Laganier, Julien <julienl@qualcomm.com>:
>> > Hui Deng wrote:
>> >>
>> >> Hi, George,
>> >>
>> >> just two clarifications AMSS/Brew DNS configuration is
>> >> interface based other than host based?
>> >
>> > Quoting the text George sent:
>> >
>> > =A0 AMSS allows each interface to be configured with its own set of DN=
S
>> > =A0 configuration parameters - a list of DNS servers, domain names etc=
.
>>
>> As you can see from the MIF discussion, even configuration could be
>> interface based, but final DNS server selection could be host based,
>> does AMSS/Brew works similar?
>
> Quoting the text George sent:
>
>> Interface selected to make a DNS resolution is the one to which
>> application making the DNS query is bound. =A0Applications can also
>> specify a different netpolicy as part of DNS request to select another
>> interface for DNS resolution. =A0Regardless, all the DNS queries are
>> sent only over this selected interface using the DNS configuration
>> from the interface.
>
> This seems to answer your question, doesn't it?
It still not clear to me, like the last sentence, it doesn't say applicatio=
n
like web browser which could use multiple interfaces, which interface
will this application be bound to?

>
>> >> secondly, network profile could identify only APN other than PDP
>> >> context?
>> >
>> > Quoting the text George sent:
>> >
>> > =A0 The network profile identifies a type of network domain
>> > =A0 or service within a certain network technology, such as 3GPP APN o=
r
>> > =A0 Mobile IP Home Agent. =A0It also specifies all the mandatory param=
eters
>> > =A0 required to connect to the domain such authentication credentials
>> > =A0 and other optional parameters such as QoS attributes. =A0Network P=
rofile
>> > =A0 is technology specific and set of parameters contained in the prof=
ile
>> > =A0 could vary for different technologies.
>>
>> wifi has two type connections:connected through APN, or directed
>> connected with Internet
>> assume you have 3G+Wifi Connections,
>> in your profile, it would be the same APN for 3G and Wfi, then you
>> have to rely on access type?
>> but access type will differentiate 3g and wifi.
>> So who will be high priority? access type or APN(profile).
>
> I am not sure I follow you. Let me try to sketch what happens:
>
> An application specifying an APN in its network profile means that it des=
ire to connect to the PDN named by this APN.
>
> As a result, only interfaces connecting to that APN will be selected, whi=
ch rules out WiFi by itself and keeps in 3G, and any of the 3GPP accesses o=
ver WiFi (such as 3GPP I-WLAN or either of the various non-3GPP accesses ov=
er S2a/b/c interfaces.)
>
> If the application has specified a preference for an ANY_Cellular access =
technology (or say HSDPA) then 3G will be selected, if the application has =
specified a preference for an ANY_Wireless access technology (or say IEEE 8=
02.11) the 3GPP I-WLAN application will be selected. If the application has=
n't specified anything, the default access will be selected.
>
> Does the above clarify the situation?
Could I understand that access type is more high priority than APN,
if that is what it is designed, please kind help to clarify the text,

thanks

-hui

>
> --julien
>

From denghui02@gmail.com  Mon Apr 26 23:30:36 2010
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 38B223A6C5A for <mif@core3.amsl.com>; Mon, 26 Apr 2010 23:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 Vp02wXTZ6AUv for <mif@core3.amsl.com>; Mon, 26 Apr 2010 23:30:35 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 07A733A6ACC for <mif@ietf.org>; Mon, 26 Apr 2010 23:30:33 -0700 (PDT)
Received: by pwj2 with SMTP id 2so9118694pwj.31 for <mif@ietf.org>; Mon, 26 Apr 2010 23:30:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=B5eHVJj8JyerllogrckOMLhIiFkPtxB+zQQaPp5OsCU=; b=vCHhnSXajOyAk5Yv1W5k398rjdO1eLG9ju47nfmeEFjdiXN0so2RJtPBL4KzYHVTMv eaXSd15EU+CC4+33Y3d1YlNZn3RQ/D+oyF8wtZtAcFpdubLbqcNgO+UnZU6qe5W5jnJX gWVRyRzfMRgXnkHWX7R4fphwKS9XKN1gNJfr0=
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=LncH7GAOy8RmPtbdxd6jxWqI0/ZSXOqj0JTIF8qjJOjkUV2zIGhci0aoVMVPVM2rS3 Qvb8Ke0pwetdjX1jZZIgHnGovr09LUMWeoVZBuruYTzphwv2gGe/sEN0PgOyNieNWxTF nJKeWJp+xrZdQnFZN2oUEBo6oQdj4XcyNvatk=
MIME-Version: 1.0
Received: by 10.143.87.6 with SMTP id p6mr2717106wfl.19.1272349817375; Mon, 26  Apr 2010 23:30:17 -0700 (PDT)
Received: by 10.142.192.1 with HTTP; Mon, 26 Apr 2010 23:30:17 -0700 (PDT)
Date: Tue, 27 Apr 2010 14:30:17 +0800
Message-ID: <y2g1d38a3351004262330y1f525a80i6338199e4971297f@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Hui Deng <denghui02@hotmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mif@ietf.org, Margaret Wasserman <mrw@sandstorm.net>
Subject: [mif] 77th MIF minutes
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 Apr 2010 06:30:36 -0000

Hello, all

Thanks Carl for taking minutes,  Behcet for jabber.

Draft minutes about last ietf meeting,
http://www.ietf.org/proceedings/10mar/minutes/mif.txt

Please review and comments on it,

Best regards,

-Margaret & Hui
