From teemu.savolainen@nokia.com Fri Jun 10 07:29:46 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BE911E817C for ; Fri, 10 Jun 2011 07:29:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPdUuxCHxC2r for ; Fri, 10 Jun 2011 07:29:46 -0700 (PDT) Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1BB1F0C67 for ; Fri, 10 Jun 2011 07:29:46 -0700 (PDT) Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p5AETRXp005998 for ; Fri, 10 Jun 2011 17:29:45 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 10 Jun 2011 17:29:44 +0300 Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 10 Jun 2011 16:29:43 +0200 Received: from 008-AM1MPN1-031.mgdnok.nokia.com ([169.254.1.208]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0289.008; Fri, 10 Jun 2011 16:29:43 +0200 From: To: Thread-Topic: Conluding this question RE: [mif] DNS server selection and whether to support DHCPv4 or not Thread-Index: AcwnehgQBg+UkV/eSEGf2KbnnKB2og== Date: Fri, 10 Jun 2011 14:29:43 +0000 Message-ID: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.162.89.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 10 Jun 2011 14:29:44.0482 (UTC) FILETIME=[D7ACC820:01CC277A] X-Nokia-AV: Clean Subject: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 14:29:47 -0000 Hi, So.. is there anyone who really wants to have DHCPv4 option for DNS server = selection? I don't see real need for it, but this is one big question that = needs to be sorted out - preferably before last call:) Best regards, Teemu From maxpassion@gmail.com Sun Jun 12 10:34:45 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F4E11E80AE for ; Sun, 12 Jun 2011 10:34:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0wW6EkEXG4J for ; Sun, 12 Jun 2011 10:34:45 -0700 (PDT) Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3AC11E80E8 for ; Sun, 12 Jun 2011 10:34:45 -0700 (PDT) Received: by vxg33 with SMTP id 33so4658223vxg.31 for ; Sun, 12 Jun 2011 10:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=23PP/L4Yvppvxf52tM3yAYMEjAy330YDvR2xyoMUxZ4=; b=OajVNj19VYQPXvWelFgYuEApdF8vse8h8fjvm9OxmbRJU7RqqixYFJW8YcbP4WuXkB fpmPHo4Fe6SGVkkJgvVCD3IrKIT++EOEd3/WXwb4q0LPacPdiyhcYC6MWeieGiSrcWZK grLe3hsFS5iCpjb65AtzB24vUVP3QSM2AKf8A= 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; b=lRCTSbTzy7VKivx8DNWMr6TAxZnHHJuI8u98149thv713pXmstbIst5RzwvvyZG0Jq fLX11VUfxy0sybKUl5I1vjJU/4epeVEVH361+gRczS4/QH1QXpaOKotSqymG8Gv3Ox5j zTLbHNwwhW9p9K0+/DS9CVQgyn5a0c6hTZgWU= MIME-Version: 1.0 Received: by 10.52.31.227 with SMTP id d3mr3194894vdi.126.1307900084678; Sun, 12 Jun 2011 10:34:44 -0700 (PDT) Received: by 10.52.156.164 with HTTP; Sun, 12 Jun 2011 10:34:44 -0700 (PDT) In-Reply-To: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> Date: Mon, 13 Jun 2011 01:34:44 +0800 Message-ID: From: liu dapeng To: teemu.savolainen@nokia.com Content-Type: text/plain; charset=ISO-8859-1 Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2011 17:34:46 -0000 Hi Teemu, Since DHCPv4 is currently widely used, I think it would be helpful to support DHCPv4 option for DNS server selection. BR, Dapeng Liu 2011/6/10, teemu.savolainen@nokia.com : > Hi, > > So.. is there anyone who really wants to have DHCPv4 option for DNS server > selection? I don't see real need for it, but this is one big question that > needs to be sorted out - preferably before last call:) > > Best regards, > > Teemu > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif > -- ------ Best Regards, Dapeng Liu From Ted.Lemon@nominum.com Sun Jun 12 12:33:42 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A73B621F847F for ; Sun, 12 Jun 2011 12:33:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.98 X-Spam-Level: X-Spam-Status: No, score=-105.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVQ9TOMYMkij for ; Sun, 12 Jun 2011 12:33:42 -0700 (PDT) Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id EAA7F21F847E for ; Sun, 12 Jun 2011 12:33:41 -0700 (PDT) Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTfUUlalbxLl+qoZi3lSQD+Yo5dCLM7eh@postini.com; Sun, 12 Jun 2011 12:33:42 PDT Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2CD4D1B8592 for ; Sun, 12 Jun 2011 12:33:41 -0700 (PDT) Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EBABF190052; Sun, 12 Jun 2011 12:33:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com) Received: from [192.168.128.201] (209.117.47.253) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 12 Jun 2011 12:33:40 -0700 MIME-Version: 1.0 (Apple Message framework v1237.1) Content-Type: text/plain; charset="us-ascii" From: Ted Lemon In-Reply-To: Date: Sun, 12 Jun 2011 15:33:40 -0400 Content-Transfer-Encoding: quoted-printable Message-ID: <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> To: liu dapeng X-Mailer: Apple Mail (2.1237.1) Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2011 19:33:42 -0000 On Jun 12, 2011, at 1:34 PM, liu dapeng wrote: > Since DHCPv4 is currently widely used, I think it would be helpful to > support DHCPv4 option for DNS server selection. You raise a good point. As long as we define the DHCPv4 option to only = send IPv4 addresses, it should be straightforward. Hm, except that it = can only be a single option, so we need to define the format so that it = can contain multiple "delegations." From teemu.savolainen@nokia.com Tue Jun 14 07:49:50 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED8622801B for ; Tue, 14 Jun 2011 07:49:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.099 X-Spam-Level: X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9qIzNmvv7Ri for ; Tue, 14 Jun 2011 07:49:49 -0700 (PDT) Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id BBBAA22800F for ; Tue, 14 Jun 2011 07:49:49 -0700 (PDT) Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p5EEn7EP002236; Tue, 14 Jun 2011 17:49:45 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 14 Jun 2011 17:49:43 +0300 Received: from 008-AM1MMR1-001.mgdnok.nokia.com (65.54.30.56) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 14 Jun 2011 16:49:42 +0200 Received: from 008-AM1MPN1-031.mgdnok.nokia.com ([169.254.1.208]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.01.0289.008; Tue, 14 Jun 2011 16:49:42 +0200 From: To: , Thread-Topic: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not Thread-Index: AQHMKqJLCV2XVgORTku+MAZo42HqUw== Date: Tue, 14 Jun 2011 14:49:42 +0000 Message-ID: <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> In-Reply-To: <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.162.78.119] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 14 Jun 2011 14:49:43.0559 (UTC) FILETIME=[4C086970:01CC2AA2] X-Nokia-AV: Clean Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2011 14:49:50 -0000 Something like this, perhaps, for DHCPv4 option format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Code | Len |prf| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | DNS-recursive-name-server (IPv4 address) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + DNS suffixes and prefixes | | (variable length) | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Or is there need to have multiple DNS server IPv4 addresses included in an = option? Teemu > -----Original Message----- > From: ext Ted Lemon [mailto:Ted.Lemon@nominum.com] > Sent: 12. kes=E4kuuta 2011 22:34 > To: liu dapeng > Cc: Savolainen Teemu (Nokia-CTO/Tampere); mif@ietf.org > Subject: Re: [mif] Conluding this question RE: DNS server selection and w= hether > to support DHCPv4 or not >=20 > On Jun 12, 2011, at 1:34 PM, liu dapeng wrote: > > Since DHCPv4 is currently widely used, I think it would be helpful to > > support DHCPv4 option for DNS server selection. >=20 > You raise a good point. As long as we define the DHCPv4 option to only = send > IPv4 addresses, it should be straightforward. Hm, except that it can on= ly be a > single option, so we need to define the format so that it can contain mul= tiple > "delegations." From Ted.Lemon@nominum.com Tue Jun 14 09:57:57 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C415411E8098 for ; Tue, 14 Jun 2011 09:57:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDg-nHyAqFzD for ; Tue, 14 Jun 2011 09:57:57 -0700 (PDT) Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF9A11E807F for ; Tue, 14 Jun 2011 09:57:57 -0700 (PDT) Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTfeTFC2IX6DNep78Zrs4wiodYt3A5jp/@postini.com; Tue, 14 Jun 2011 09:57:57 PDT Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DA711F8063 for ; Tue, 14 Jun 2011 09:57:55 -0700 (PDT) Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CEE9719005D; Tue, 14 Jun 2011 09:57:55 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com) Received: from kali.ddns.nominum.com (64.89.225.121) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 14 Jun 2011 09:57:55 -0700 MIME-Version: 1.0 (Apple Message framework v1237.1) Content-Type: text/plain; charset="iso-8859-1" From: Ted Lemon In-Reply-To: <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> Date: Tue, 14 Jun 2011 09:57:54 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: <55AF032A-2918-4ECD-B50D-C65EF6189325@nominum.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> To: X-Mailer: Apple Mail (2.1237.1) Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2011 16:57:57 -0000 On Jun 14, 2011, at 7:49 AM, wrote: > Or is there need to have multiple DNS server IPv4 addresses included = in an option? Isn't that a feature of the DHCPv6 option? That is, I thought I = understood the draft to be saying that you could send more than one of = these options, and by doing so, provide more than one server/domain set. = In DHCPv4, if you send two of the same option, the DHCP client will = concatenate them and treat the payload as if it were a single option. From teemu.savolainen@nokia.com Wed Jun 15 08:15:19 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87ACF11E815F for ; Wed, 15 Jun 2011 08:15:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.766 X-Spam-Level: X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uH71HSEMVZy2 for ; Wed, 15 Jun 2011 08:15:19 -0700 (PDT) Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5940311E815D for ; Wed, 15 Jun 2011 08:15:13 -0700 (PDT) Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p5FFF7n9004399; Wed, 15 Jun 2011 18:15:10 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 Jun 2011 18:14:44 +0300 Received: from 008-AM1MMR1-006.mgdnok.nokia.com (65.54.30.61) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 15 Jun 2011 17:14:44 +0200 Received: from 008-AM1MPN1-031.mgdnok.nokia.com ([169.254.1.208]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0289.008; Wed, 15 Jun 2011 17:14:44 +0200 From: To: Thread-Topic: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not Thread-Index: AQHMKqJLCV2XVgORTku+MAZo42HqU5S88ZwAgAGWLuA= Date: Wed, 15 Jun 2011 15:14:43 +0000 Message-ID: <916CE6CF87173740BC8A2CE44309696207579C@008-AM1MPN1-031.mgdnok.nokia.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> <55AF032A-2918-4ECD-B50D-C65EF6189325@nominum.com> In-Reply-To: <55AF032A-2918-4ECD-B50D-C65EF6189325@nominum.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.162.91.110] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jun 2011 15:14:44.0601 (UTC) FILETIME=[F522FE90:01CC2B6E] X-Nokia-AV: Clean Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 15:15:19 -0000 Yes.. I understand feature parity is a nice thing, but a container option (= or nested option) for DHCPv4 sounds complex.. So does feature parity justif= y this complexity, or would it be enough with DHCPv4 learn just one DNS ser= ver capable of serving certain namespaces? Or do you have some idea how this option could be formatted nicely for DHCP= v4? Teemu > -----Original Message----- > From: ext Ted Lemon [mailto:Ted.Lemon@nominum.com] > Sent: 14. kes=E4kuuta 2011 19:58 > To: Savolainen Teemu (Nokia-CTO/Tampere) > Cc: maxpassion@gmail.com; mif@ietf.org > Subject: Re: [mif] Conluding this question RE: DNS server selection and w= hether > to support DHCPv4 or not >=20 > On Jun 14, 2011, at 7:49 AM, wrote: > > Or is there need to have multiple DNS server IPv4 addresses included in= an > option? >=20 > Isn't that a feature of the DHCPv6 option? That is, I thought I understo= od the > draft to be saying that you could send more than one of these options, an= d by > doing so, provide more than one server/domain set. In DHCPv4, if you se= nd > two of the same option, the DHCP client will concatenate them and treat t= he > payload as if it were a single option. From Ted.Lemon@nominum.com Wed Jun 15 08:40:08 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5722A21F8479 for ; Wed, 15 Jun 2011 08:40:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vAGb5024b51U for ; Wed, 15 Jun 2011 08:40:07 -0700 (PDT) Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 51AF921F8474 for ; Wed, 15 Jun 2011 08:39:59 -0700 (PDT) Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTfjST34eu2VhL9zd05Sk8VyER7N/wxXb@postini.com; Wed, 15 Jun 2011 08:40:00 PDT Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CADD51B8510 for ; Wed, 15 Jun 2011 08:39:58 -0700 (PDT) Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C0FF4190060; Wed, 15 Jun 2011 08:39:58 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com) Received: from kali.ddns.nominum.com (64.89.225.121) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 15 Jun 2011 08:39:58 -0700 MIME-Version: 1.0 (Apple Message framework v1237.1) Content-Type: text/plain; charset="iso-8859-1" From: Ted Lemon In-Reply-To: <916CE6CF87173740BC8A2CE44309696207579C@008-AM1MPN1-031.mgdnok.nokia.com> Date: Wed, 15 Jun 2011 08:39:58 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: <8D8BA88A-F079-4A64-A923-8B8FBA4CCD04@nominum.com> References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> <55AF032A-2918-4ECD-B50D-C65EF6189325@nominum.com> <916CE6CF87173740BC8A2CE44309696207579C@008-AM1MPN1-031.mgdnok.nokia.com> To: X-Mailer: Apple Mail (2.1237.1) Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 15:40:08 -0000 On Jun 15, 2011, at 8:14 AM, wrote: > Yes.. I understand feature parity is a nice thing, but a container = option (or nested option) for DHCPv4 sounds complex.. So does feature = parity justify this complexity, or would it be enough with DHCPv4 learn = just one DNS server capable of serving certain namespaces? It seems as though if the feature is useful in IPv6, it's also useful in = IPv4. I can't think of a reason why you'd care less about it in IPv4. > Or do you have some idea how this option could be formatted nicely for = DHCPv4? I think if you just add a count field for the number of suffixes, it = should work. From teemu.savolainen@nokia.com Wed Jun 15 10:19:11 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113F59E8006 for ; Wed, 15 Jun 2011 10:19:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.724 X-Spam-Level: X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHOPb6UY-kxy for ; Wed, 15 Jun 2011 10:19:10 -0700 (PDT) Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4556B9E8004 for ; Wed, 15 Jun 2011 10:19:10 -0700 (PDT) Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com [10.160.244.23]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p5FHJ2UD021391; Wed, 15 Jun 2011 20:19:07 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 Jun 2011 20:19:06 +0300 Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 15 Jun 2011 19:19:06 +0200 Received: from 008-AM1MPN1-031.mgdnok.nokia.com ([169.254.1.208]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0289.008; Wed, 15 Jun 2011 19:19:06 +0200 From: To: Thread-Topic: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not Thread-Index: AQHMKqJLCV2XVgORTku+MAZo42HqU5S88ZwAgAGWLuD//+ZgAIAAPTmI Date: Wed, 15 Jun 2011 17:19:05 +0000 Message-ID: References: <916CE6CF87173740BC8A2CE44309696206FDC8@008-AM1MPN1-031.mgdnok.nokia.com> <6E289438-9A9C-49DD-BE22-535F5493D3D8@nominum.com> <916CE6CF87173740BC8A2CE443096962074B0C@008-AM1MPN1-031.mgdnok.nokia.com> <55AF032A-2918-4ECD-B50D-C65EF6189325@nominum.com> <916CE6CF87173740BC8A2CE44309696207579C@008-AM1MPN1-031.mgdnok.nokia.com>, <8D8BA88A-F079-4A64-A923-8B8FBA4CCD04@nominum.com> In-Reply-To: <8D8BA88A-F079-4A64-A923-8B8FBA4CCD04@nominum.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jun 2011 17:19:06.0849 (UTC) FILETIME=[54FBAD10:01CC2B80] X-Nokia-AV: Clean Cc: mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whether to support DHCPv4 or not X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 17:19:11 -0000 Because with IPv4 multihoming is painful.. I'm not sure how count field for suffixes help.... Or does it hint receiver= 's parser to notice where to expect next preference field etc after multipl= e option instances have been concatenated? How the concatenation btw works?= Receiver sums options up and creates one large with one code field, total = length field, and the payloads are then just concatenated? And suffix count= helps to find beginning of next instance? Teemu -----Original Message----- From: ext Ted Lemon Sent: 15/06/2011, 18:40 To: Savolainen Teemu (Nokia-CTO/Tampere) Cc: maxpassion@gmail.com; mif@ietf.org Subject: Re: [mif] Conluding this question RE: DNS server selection and whe= ther to support DHCPv4 or not On Jun 15, 2011, at 8:14 AM, wrote: > Yes.. I understand feature parity is a nice thing, but a container option= (or nested option) for DHCPv4 sounds complex.. So does feature parity just= ify this complexity, or would it be enough with DHCPv4 learn just one DNS s= erver capable of serving certain namespaces? It seems as though if the feature is useful in IPv6, it's also useful in IP= v4. I can't think of a reason why you'd care less about it in IPv4. > Or do you have some idea how this option could be formatted nicely for DH= CPv4? I think if you just add a count field for the number of suffixes, it should= work. From internet-drafts@ietf.org Wed Jun 22 01:45:53 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB569E8007; Wed, 22 Jun 2011 01:45:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.571 X-Spam-Level: X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCI9kdWWYObK; Wed, 22 Jun 2011 01:45:52 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867B19E8004; Wed, 22 Jun 2011 01:45:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.55 Message-ID: <20110622084552.941.48860.idtracker@ietfa.amsl.com> Date: Wed, 22 Jun 2011 01:45:52 -0700 Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-dns-server-selection-03.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 08:45:53 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Multiple Interfaces Working Group of = the IETF. Title : Improved DNS Server Selection for Multi-Homed Nodes Author(s) : Teemu Savolainen Jun-ya Kato Ted Lemon Filename : draft-ietf-mif-dns-server-selection-03.txt Pages : 24 Date : 2011-06-22 A multi-homed node can be connected to multiple networks that may utilize different DNS namespaces. The node commonly receives DNS server configuration information from all connected networks. Some of the DNS servers may have information about namespaces other servers do not have. When the multi-homed node needs to utilize DNS, it has to choose which of the servers to contact to. This document describes a policy based method for helping on selection of DNS server, for both forward and reverse DNS lookup procedures, with help of DNS suffix and IPv6 prefix information received via DHCPv6 or DHCPv4. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-03.= txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-03.t= xt From teemu.savolainen@nokia.com Wed Jun 22 04:10:57 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A0411E80F8 for ; Wed, 22 Jun 2011 04:10:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.766 X-Spam-Level: X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0M-r5hr8Nk7 for ; Wed, 22 Jun 2011 04:10:57 -0700 (PDT) Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id ADC0911E8080 for ; Wed, 22 Jun 2011 04:10:55 -0700 (PDT) Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p5MBAqi9005476 for ; Wed, 22 Jun 2011 14:10:53 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Jun 2011 14:10:27 +0300 Received: from 008-AM1MMR1-001.mgdnok.nokia.com (65.54.30.56) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 22 Jun 2011 13:10:26 +0200 Received: from 008-AM1MPN1-031.mgdnok.nokia.com ([169.254.1.208]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.01.0289.008; Wed, 22 Jun 2011 13:10:26 +0200 From: To: Thread-Topic: [mif] I-D Action: draft-ietf-mif-dns-server-selection-03.txt Thread-Index: AQHMMLkZNOSoFw6kx0uWJjUqCQeOpZTJOF9Q Date: Wed, 22 Jun 2011 11:10:25 +0000 Message-ID: <916CE6CF87173740BC8A2CE443096962078F2D@008-AM1MPN1-031.mgdnok.nokia.com> References: <20110622084552.941.48860.idtracker@ietfa.amsl.com> In-Reply-To: <20110622084552.941.48860.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.162.27.108] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 22 Jun 2011 11:10:27.0131 (UTC) FILETIME=[FD7ED0B0:01CC30CC] X-Nokia-AV: Clean Subject: Re: [mif] I-D Action: draft-ietf-mif-dns-server-selection-03.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 11:10:58 -0000 Hi all, There seemed to be interest for DHCPv4 support, hence the 03 version now ha= s first stab on the topic. Comments welcome, Teemu > -----Original Message----- > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of ext > internet-drafts@ietf.org > Sent: 22. kes=E4kuuta 2011 11:46 > To: i-d-announce@ietf.org > Cc: mif@ietf.org > Subject: [mif] I-D Action: draft-ietf-mif-dns-server-selection-03.txt >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Multiple Interfaces Working Group of the= IETF. >=20 > Title : Improved DNS Server Selection for Multi-Homed Nodes > Author(s) : Teemu Savolainen > Jun-ya Kato > Ted Lemon > Filename : draft-ietf-mif-dns-server-selection-03.txt > Pages : 24 > Date : 2011-06-22 >=20 > A multi-homed node can be connected to multiple networks that may > utilize different DNS namespaces. The node commonly receives DNS > server configuration information from all connected networks. Some > of the DNS servers may have information about namespaces other > servers do not have. When the multi-homed node needs to utilize DNS, > it has to choose which of the servers to contact to. This document > describes a policy based method for helping on selection of DNS > server, for both forward and reverse DNS lookup procedures, with help > of DNS suffix and IPv6 prefix information received via DHCPv6 or > DHCPv4. >=20 >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-0= 3.txt >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > This Internet-Draft can be retrieved at: > ftp://ftp.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-03= .txt > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif From denghui02@hotmail.com Fri Jun 24 21:23:37 2011 Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E13C321F8492 for ; Fri, 24 Jun 2011 21:23:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycqoTljY5b8G for ; Fri, 24 Jun 2011 21:23:36 -0700 (PDT) Received: from col0-omc2-s8.col0.hotmail.com (col0-omc2-s8.col0.hotmail.com [65.55.34.82]) by ietfa.amsl.com (Postfix) with ESMTP id AB1E221F848E for ; Fri, 24 Jun 2011 21:23:36 -0700 (PDT) Received: from COL118-W31 ([65.55.34.71]) by col0-omc2-s8.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 24 Jun 2011 21:23:36 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_1192e159-368b-4fc3-b3db-7f226e6746c2_" X-Originating-IP: [222.129.49.250] From: Hui Deng To: Date: Sat, 25 Jun 2011 12:23:36 +0800 Importance: Normal In-Reply-To: <20110624183513.7035311E81A8@ietfa.amsl.com> References: <20110624183513.7035311E81A8@ietfa.amsl.com> MIME-Version: 1.0 X-OriginalArrivalTime: 25 Jun 2011 04:23:36.0515 (UTC) FILETIME=[A6DFA930:01CC32EF] Subject: [mif] FW: Please help the Nomcom X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jun 2011 04:23:38 -0000 --_1192e159-368b-4fc3-b3db-7f226e6746c2_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 8bit > From: nomcom-chair@ietf.org > To: wgchairs@ietf.org > Subject: Please help the Nomcom > Date: Fri, 24 Jun 2011 11:35:13 -0700 > > Hi WG chairs, > We have had a good response to the first call for volunteers but the > rate at which new volunteers are coming in is slowing down. The Nomcom > process is best served by a large pool of volunteers drawn from a wide > spectrum of IETF attendees. Where else would we find this wide spectrum > if not in the WG mailing lists. > > I would really appreciate it if you can forward the message onto your > working group mailing lists. > > The latest volunteer status and the second call for volunteers can be > found at > https://datatracker.ietf.org/ann/nomcom/2964/ > > Thanks in advance for your help. > > Suresh Krishnan > Nomcom Chair 2011-2012 > Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com --_1192e159-368b-4fc3-b3db-7f226e6746c2_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: 8bit
> From: nomcom-chair@ietf.org
> To: wgchairs@ietf.org
> Subject: Please help the Nomcom
> Date: Fri, 24 Jun 2011 11:35:13 -0700
>
> Hi WG chairs,
> We have had a good response to the first call for volunteers but the
> rate at which new volunteers are coming in is slowing down. The Nomcom
> process is best served by a large pool of volunteers drawn from a wide
> spectrum of IETF attendees. Where else would we find this wide spectrum
> if not in the WG mailing lists.
>
> I would really appreciate it if you can forward the message onto your
> working group mailing lists.
>
> The latest volunteer status and the second call for volunteers can be
> found at
> https://datatracker.ietf.org/ann/nomcom/2964/
>
> Thanks in advance for your help.
>
> Suresh Krishnan
> Nomcom Chair 2011-2012
> Email: nomcom-chair@ietf.org, suresh.krishnan@ ericsson.com

--_1192e159-368b-4fc3-b3db-7f226e6746c2_--