From maxpassion@gmail.com Thu Jun 28 02:47:49 2012 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 EA0F121F89FB for ; Thu, 28 Jun 2012 02:47:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.522 X-Spam-Level: X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9I5B+mfECys for ; Thu, 28 Jun 2012 02:47:48 -0700 (PDT) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6A43B21F8A00 for ; Thu, 28 Jun 2012 02:47:44 -0700 (PDT) Received: by obbwc20 with SMTP id wc20so3217258obb.31 for ; Thu, 28 Jun 2012 02:47:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uV5LIfJhaHL6fpLLLa253Q9eeO1ZCRBpM0KdX+Wuy88=; b=iPgW5LkiTlpj/HT1ZIXWqlfomQ2XEKe9uI6F3njaN6CIWln8TlhrAtOZ27OzYoKpJD mOvZyUgI5eeTKit4j4eQr9JCfGA+VppSPh7HP9EKUzxQyrMux5kb9x5Bd11kC0P7bWDi R/FLxQm/LrnB2S08ETy5XJS6KTbQhx+a7vAVHmDpUwjoQPIwS+Sl2LDJySL7nmFG2gtz VVmvZa13HTAShNXM7Zod+NHIdC6UZ0KvvGLMsWjcM18oYfV4wDCOvJ4JvHzsRRP8HDj4 scbLEWhserDGq9sNhg6bImsaQI40hVjnRxHc9CY6wpTNh5o9sZIFKsPMkbje1b+tKDrt l/Wg== MIME-Version: 1.0 Received: by 10.60.1.37 with SMTP id 5mr1376414oej.10.1340876863946; Thu, 28 Jun 2012 02:47:43 -0700 (PDT) Received: by 10.76.1.46 with HTTP; Thu, 28 Jun 2012 02:47:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Jun 2012 17:47:43 +0800 Message-ID: From: liu dapeng To: Basavaraj.Patil@nokia.com Content-Type: text/plain; charset=ISO-8859-1 Cc: mif@ietf.org Subject: Re: [mif] References to link layer triggers specs 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: Thu, 28 Jun 2012 09:47:50 -0000 Hi Raj, Thanks for sending this reference but I am not sure it is relevent to MIF API. RFC4957 is about L2 triggers instead of APIs that tell the application of the L2 event. RFC5184 is not standard. Thanks, Best Regards, Dapeng 2012/3/30, Basavaraj.Patil@nokia.com : > > Hello, > > I had agreed to send some references to link layer triggers related > documents w.r.t the API discussion in the WG. > Please see: > > 1. RFC4957 - Link-Layer Event Notifications for Detecting Network > Attachments > 2. RFC5184 - Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven > Fast Handover > > > -Raj > > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif > -- ------ Best Regards, Dapeng Liu From pierrick.seite@orange.com Thu Jun 28 06:43:14 2012 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 E8E4C21F847D for ; Thu, 28 Jun 2012 06:43:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfwgbqS6r7FM for ; Thu, 28 Jun 2012 06:43:13 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 02C2F21F8445 for ; Thu, 28 Jun 2012 06:43:09 -0700 (PDT) Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 38CC418CAF7; Thu, 28 Jun 2012 15:43:08 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 10B374C015; Thu, 28 Jun 2012 15:43:08 +0200 (CEST) Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Thu, 28 Jun 2012 15:43:07 +0200 From: To: 'liu dapeng' , "Basavaraj.Patil@nokia.com" Thread-Topic: [mif] References to link layer triggers specs Thread-Index: AQHNVRMWXCFoul9y/ESFEb5OucHDypcPus1A Date: Thu, 28 Jun 2012 13:43:07 +0000 Message-ID: <25217_1340890988_4FEC5F6C_25217_1201_1_81C77F07008CA24F9783A98CFD706F71016D64@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.5] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.6.19.115414 Cc: "mif@ietf.org" Subject: Re: [mif] References to link layer triggers specs 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: Thu, 28 Jun 2012 13:43:14 -0000 Hi, Raj, thanks for the references. IMU, the MIF API should be able to receive information from L2 and rely on = L2 triggers to detect connectivity. Is that correct? If so, it makes sense = to define the MIF API using abstract L2 triggers and, thus, it may be worth= to consider RFC5184, even if experimental. BR, Pierrick > -----Message d'origine----- > De=A0: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] De la part de > liu dapeng > Envoy=E9=A0: jeudi 28 juin 2012 11:48 > =C0=A0: Basavaraj.Patil@nokia.com > Cc=A0: mif@ietf.org > Objet=A0: Re: [mif] References to link layer triggers specs >=20 > Hi Raj, >=20 > Thanks for sending this reference but I am not sure it is relevent to > MIF API. > RFC4957 is about L2 triggers instead of APIs that tell the application > of the L2 event. > RFC5184 is not standard. >=20 > Thanks, >=20 > Best Regards, > Dapeng >=20 > 2012/3/30, Basavaraj.Patil@nokia.com : > > > > Hello, > > > > I had agreed to send some references to link layer triggers related > > documents w.r.t the API discussion in the WG. > > Please see: > > > > 1. RFC4957 - Link-Layer Event Notifications for Detecting Network > > Attachments > > 2. RFC5184 - Unified Layer 2 (L2) Abstractions for Layer 3 (L3)- > Driven > > Fast Handover > > > > > > -Raj > > > > _______________________________________________ > > mif mailing list > > mif@ietf.org > > https://www.ietf.org/mailman/listinfo/mif > > >=20 >=20 > -- >=20 > ------ > Best Regards, > Dapeng Liu > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. From internet-drafts@ietf.org Fri Jun 29 01:22:40 2012 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 6811621F850B; Fri, 29 Jun 2012 01:22:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oyM4yHryNmmx; Fri, 29 Jun 2012 01:22:38 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD4921F86AF; Fri, 29 Jun 2012 01:22:16 -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: 4.21p1 Message-ID: <20120629082216.21479.75029.idtracker@ietfa.amsl.com> Date: Fri, 29 Jun 2012 01:22:16 -0700 Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-dns-server-selection-10.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: Fri, 29 Jun 2012 08:22:41 -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 Recursive DNS Server Selection for Multi-Interf= aced Nodes Author(s) : Teemu Savolainen Jun-ya Kato Ted Lemon Filename : draft-ietf-mif-dns-server-selection-10.txt Pages : 31 Date : 2012-06-29 Abstract: A multi-interfaced node is connected to multiple networks, some of which might be utilizing private DNS namespaces. A node commonly receives recursive DNS server configuration information from all connected networks. Some of the recursive DNS servers might have information about namespaces other servers do not have. When a multi-interfaced node needs to utilize DNS, the node has to choose which of the recursive DNS servers to use. This document describes DHCPv4 and DHCPv6 options that can be used to configure nodes with information required to perform informed recursive DNS server selection decisions. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mif-dns-server-selection There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mif-dns-server-selection-10 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mif-dns-server-selection-10 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/