IETF Logo Mail Archive

[mif] draft-ietf-mif-current-practices-00

"Dan Wing" <dwing@cisco.com> Tue, 30 March 2010 23:02 UTC

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 7176A3A6980 for <mif@core3.amsl.com>; Tue, 30 Mar 2010 16:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.683
X-Spam-Level:
X-Spam-Status: No, score=-7.683 tagged_above=-999 required=5 tests=[AWL=0.297, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, 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 LFqdVJlmPd+h for <mif@core3.amsl.com>; Tue, 30 Mar 2010 16:02:27 -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 8A4103A6941 for <mif@ietf.org>; Tue, 30 Mar 2010 16:02:27 -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: AvkIAAcgsktAZnwN/2dsb2JhbACHWIEUhlWLZ3GnJJkehQAEgyA
X-IronPort-AV: E=Sophos;i="4.51,337,1267401600"; d="scan'208";a="97637753"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 30 Mar 2010 23:02:57 +0000
Received: from dwingwxp01 ([10.32.240.198]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2UN2tBm012721 for <mif@ietf.org>; Tue, 30 Mar 2010 23:02:56 GMT
From: Dan Wing <dwing@cisco.com>
To: mif@ietf.org
Date: Tue, 30 Mar 2010 16:02:55 -0700
Message-ID: <044f01cad05d$22cdd090$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcrQXSIWX7VrtDK7SBKyEB9Yj26v2Q==
Subject: [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, 30 Mar 2010 23:02:28 -0000

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

v2.23.0 | Report a Bug | By Email