Re: [mif] WG LC for MIF PS

Zhen Cao <zehn.cao@gmail.com> Sat, 20 March 2010 05:46 UTC

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 F27823A6890 for <mif@core3.amsl.com>; Fri, 19 Mar 2010 22:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.827
X-Spam-Level:
X-Spam-Status: No, score=-0.827 tagged_above=-999 required=5 tests=[AWL=-1.772, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
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 UtbUFZwAfele for <mif@core3.amsl.com>; Fri, 19 Mar 2010 22:46:12 -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 637073A6809 for <mif@ietf.org>; Fri, 19 Mar 2010 22:46:12 -0700 (PDT)
Received: by gwaa11 with SMTP id a11so650885gwa.31 for <mif@ietf.org>; Fri, 19 Mar 2010 22:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1siYdIb7k30RVWRMXWYeErxFQxKH1w3yTVgZDVbjqPA=; b=kHuPkaqkKKyMy9KgRo+FZ7SM72rfsJMZ5nVLDqa+FrBLY16DoKXqvbiQClNMX39S8x 2heRMO9CCQ2qYrhe/zqEtI4qcm6Iq/Mj1Y66tvsbFiwKXaMmhJwbRA1L05NlPZzKjxJO TO46zJOGA3ahoewyAA3BU3Hi2AS/Kk2nKAb9Y=
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=sxPmTIigWrSoiZBK4JR/v9WpKkdu8bW8IsC/3mUlEHo8PGu+IM2mC0lLxQ5OCpNwTb sqny0e2rjvD4kgvk6k83GIKZf1DPobSgKn4Q9g2VgfJPmkcOfVJ86VJRfEZMvc1KxVrx 54oSLBEE77nEybaiB08ykyWUeMwZZpMwvAwAU=
MIME-Version: 1.0
Received: by 10.101.98.8 with SMTP id a8mr9380836anm.175.1269063982873; Fri, 19 Mar 2010 22:46:22 -0700 (PDT)
In-Reply-To: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl>
References: <COL118-W43D1A92D6FAECE336508C6B1310@phx.gbl>
Date: Sat, 20 Mar 2010 13:46:22 +0800
Message-ID: <c549bac51003192246t62c91c1cw925afa82aae62d30@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Hui Deng <denghui02@hotmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Sat, 20 Mar 2010 05:46:14 -0000

Dear Authors,

Some comments below:

3.1 Below IP Interaction
Do we need to consider some below-ip layer techniques like Virtual interfaces?

3.4 Address selection
It is good to mention that some OS like OSX does not implement
3484-like policy table. 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.

3.5 Finding and Sharing IP Addresses with Peers
I do not think we need to consider the application referral behavior,
and it is out of scope of mif. I suggest removing the Grobj referral
to ip address referral generally.

4.1, bullet 6,
it is not a dns selection problem, rather it is the address selection problem.
The dns selection problem related to DNS64 is covered in
draft-wing-behave-dns64-config-02.

a typo here is "quaranteed", should be "guaranteed"

4.3 Address Selection Policy
I suggest add some text on IP family selection as one bullet, some
symptoms are introduced in draft-cao-mif-ifs.

"The inconsistency of host's application IP family, interface address
family and remote end's IP family makes the IP family selection
problem difficult.  Wrongly choosing the ip family will result into
communication failure. "


Thanks,
Zhen

2010/3/12 Hui Deng <denghui02@hotmail.com>:
>
> We appear ready to start the working group last call for our PS documents.
> This is a two-week WGLC.
> http://www.ietf.org/id/draft-ietf-mif-problem-statement-02.txt
>
> This is a two week WGLC finishing on March 26.  Please send substantive
> review comments to mif@ietf.org
>
> Thanks,
>
> -Hui
>
> ________________________________
> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now.
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
>