Re: [mif] comment about draft-mrw-mif-current-practices-01.txt

Behcet Sarikaya <behcetsarikaya@yahoo.com> Mon, 16 March 2009 20:52 UTC

Return-Path: <behcetsarikaya@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 9FC0C3A6C0D for <mif@core3.amsl.com>; Mon, 16 Mar 2009 13:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level:
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Psl1jahXhSq8 for <mif@core3.amsl.com>; Mon, 16 Mar 2009 13:52:32 -0700 (PDT)
Received: from web111407.mail.gq1.yahoo.com (web111407.mail.gq1.yahoo.com [67.195.15.168]) by core3.amsl.com (Postfix) with SMTP id BCE923A684E for <mif@ietf.org>; Mon, 16 Mar 2009 13:52:32 -0700 (PDT)
Received: (qmail 93797 invoked by uid 60001); 16 Mar 2009 20:53:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1237236795; bh=pQSsUnvQom7GEXMCV5bQts/SeER8xTmaW6/fYTug+UU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=G9EdBEqik1ZOp3lwbvuPPZsDeNobJ38Qz5VMBGNuJ7HbuARroq4SZBh/ioeXdlDDRbiY+jKR5TFWv4PjiosJ9FryVPyD5MvWGa8sirwGN/YX9VjUxCEm5ZDzndV9/lMqfdE54Ueg3JTkIARzP0OT1KJSZxSSt4HvICVCjL4jf8E=
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:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Er2zLB3SLwzUoKY4VYCboJp7cqQGPLOkA2BCYBGNWiT4pIG/aHLzM0Ctr8nJ0DQOhvTDrhJ/J77D2WY33uH5VaQu9iokvfYWIOSJbF5MpGU/kOvkPx+P6qJKLtCCA+0PHXIbzfbqhnWdktv7CRAUzt0uK4ZHks6eVh0bUzTphZ0=;
Message-ID: <126951.92563.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: lj31RQAVM1nzLt_IjRpoSXlZ_ZtKmdIdz5miOSj8vR9C37aWukoWXL9kxjT3hC5TmDrjdUDRwFXUD4_Xs6FTRy1pRJO5kYCXbX3x0V.6zEvhT16e7zpT2WfPJlFTT..b2ah3GVq8PNkdpoyTQJfzB7S9mhcv6GPFAfU6zozoWEV4g_CE.enoDpqfm_cAthyVcNI__IvRBlGlQltby6tToCRCp_pTNDVC8DKOrmYhUEGdCJW.A0ppqhm5iUyhDnggdLMU80vFYTZkaQ--
Received: from [206.16.17.212] by web111407.mail.gq1.yahoo.com via HTTP; Mon, 16 Mar 2009 13:53:14 PDT
X-Mailer: YahooMailRC/1277.32 YahooMailWebService/0.7.289.1
References: <49BEB858.5030205@it.uc3m.es>
Date: Mon, 16 Mar 2009 13:53:14 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>, mif <mif@ietf.org>
In-Reply-To: <49BEB858.5030205@it.uc3m.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2142482461-1237236794=:92563"
Subject: Re: [mif] comment about draft-mrw-mif-current-practices-01.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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, 16 Mar 2009 20:52:33 -0000

Marcelo, 
  I think that this draft tries to do a difficult thing in documenting on OSs with some outside knowledge.
  Also I find Iphone OS which is not exactly Mac OS X covered in Sec. 2.8 is missing and it is very relevant to mif work.

Regards,

Behcet




________________________________
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
To: mif <mif@ietf.org>
Sent: Monday, March 16, 2009 3:36:40 PM
Subject: [mif] comment about draft-mrw-mif-current-practices-01.txt

Hi,

This document includes very interesting information about how current implementations deal with the different problems.
One suggestion that i think it would help improve the document would be to link it more directly to the problems described in the problem statement. Of course, we need to decide on one problem statement document before, but..

What i mean, is that the problem statement documents describe a set of problems, like dealing with DNS issues, default router selection and so on and it is not directly obvious from the document in its current form how the current implementations deal with the issues. For instance, it is not obvious from this document how current implementations deal with the dual faced dns issue, which i guess many implementations actually handle pretty well.


So, i guess that once we have identified the relevant problems we want to work on, in the section for each implementation
it would be good to have a sub section for each of the problems identified in the problem statement and describing how the particular implementation deals with the particular problem.


Regards, marcelo

_______________________________________________
mif mailing list
mif@ietf.org
https://www.ietf.org/mailman/listinfo/mif