IETF Logo Mail Archive

[mif] Last Call Documents

"Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov> Mon, 22 March 2010 23:30 UTC

Return-Path: <william.d.ivancic@nasa.gov>
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 9EB7528C24F for <mif@core3.amsl.com>; Mon, 22 Mar 2010 16:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.98
X-Spam-Level:
X-Spam-Status: No, score=-3.98 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, 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 NEdbQhqryUgY for <mif@core3.amsl.com>; Mon, 22 Mar 2010 16:30:20 -0700 (PDT)
Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [198.117.0.122]) by core3.amsl.com (Postfix) with ESMTP id CF77528C1E2 for <mif@ietf.org>; Mon, 22 Mar 2010 16:30:15 -0700 (PDT)
Received: from ndjsppt04.ndc.nasa.gov (ndjsppt04.ndc.nasa.gov [198.117.1.103]) by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id A2E0E108350 for <mif@ietf.org>; Mon, 22 Mar 2010 18:30:33 -0500 (CDT)
Received: from ndjshub01.ndc.nasa.gov (ndjshub01-pub.ndc.nasa.gov [198.117.1.160]) by ndjsppt04.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id o2MNUXmw032154 for <mif@ietf.org>; Mon, 22 Mar 2010 18:30:33 -0500
Received: from NDJSSCC03.ndc.nasa.gov ([198.117.4.170]) by ndjshub01.ndc.nasa.gov ([198.117.1.160]) with mapi; Mon, 22 Mar 2010 18:30:33 -0500
From: "Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov>
To: "mif@ietf.org" <mif@ietf.org>
Date: Mon, 22 Mar 2010 18:30:31 -0500
Thread-Topic: Last Call Documents
Thread-Index: AcrKF6mCdpUn2BcFQWGXxjLLxmdP4Q==
Message-ID: <3A5AA67A8B120B48825BFFCF544385619488119171@NDJSSCC03.ndc.nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-03-22_14:2010-02-06, 2010-03-22, 2010-03-22 signatures=0
Subject: [mif] Last Call Documents
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, 22 Mar 2010 23:30:26 -0000

Sorry, I have been watching this group but not terribly active due to other commitments so I may have missed something.  I reread some of the more recent emails on the list archive to try and bring myself up to date.

At today's meeting there was discussion for what documents are ready or near completion.

I read 
http://datatracker.ietf.org/doc/draft-ietf-mif-current-practices/
and
http://datatracker.ietf.org/doc/draft-ietf-mif-problem-statement/

and believe these are ready to go as a request for Last Call has been on the list (archives checked).

I was confused regarding a request for the analysis document and whether or not this is near completion.  Is this document
http://tools.ietf.org/html/draft-cao-mif-analysis-00

If so, per the naming convention, is this a working group document?  I understand this can be even though it is not named draft-ietf-mif....

I think the analysis document should have something in the security section about concerns and possible exploits when interfacing to multiple domains.  Configuration management and what may be permitted are a BIG concern for corporate and military networks.  I want to be able to use a wifi connection in the home and 3G or 4G while mobile.  I also want to do this in the office, but can I?  Will I be permitted to?  If not, how does one ensure such doesn't happen?

******************************
Will Ivancic

v2.23.0 | Report a Bug | By Email