IETF Logo Mail Archive

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

"Dan Wing" <dwing@cisco.com> Tue, 06 April 2010 18:44 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 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, 06 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

 

> -----Original Message-----
> From: gabriel montenegro [mailto:g_e_montenegro@yahoo.com] 
> Sent: Tuesday, April 06, 2010 9:13 AM
> To: Dan Wing; mif@ietf.org
> Subject: Re: [mif] draft-ietf-mif-current-practices-00
> 
> Re: draft-montenegro-mif-multihoming:
> 
> I would have thought that it is clear, given that this info 
> is found in section 4.2 which is called "interface-specific 
> 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 
> 4.1 which is called "host-wide DNS configuration".
> 
> 
> 
> ----- 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
> > 
> > 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
> > href="mailto:mif@ietf.org">mif@ietf.org
> > href="https://www.ietf.org/mailman/listinfo/mif" target=_blank 
> > >https://www.ietf.org/mailman/listinfo/mif

v2.23.0 | Report a Bug | By Email