Re: [mif] FW: I-D Action: draft-ietf-mif-mpvd-arch-03.txt

GangChen <phdgang@gmail.com> Fri, 08 August 2014 07:42 UTC

Return-Path: <phdgang@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB3D1A0428 for <mif@ietfa.amsl.com>; Fri, 8 Aug 2014 00:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JH3uc3PSvg8R for <mif@ietfa.amsl.com>; Fri, 8 Aug 2014 00:41:58 -0700 (PDT)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E99511A019C for <mif@ietf.org>; Fri, 8 Aug 2014 00:41:57 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id k15so5238680qaq.13 for <mif@ietf.org>; Fri, 08 Aug 2014 00:41:57 -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=tpbxxsfyKpYEM8ciNApiEl5504q1Sb+YMrWHzgSmB9Y=; b=ijlNKDL58hOiZvf6z6Yk82LlQp49Dcky++bIn5JypfK8cIPb3Upguuz2CxKM2kq/ty 7A0CSwfSUbY+o9/X29k9vb4nKIKHvg+H5pwUX78yNKcJMifThxtsXbQiputMpiwXbM4E BoR5Wsg8FhLuvnO+WeHyPtSSyOkE24wmmCzBTu2xEb5cBC5UAjaBkR3YVZs4pLJkP/Fc Ltj/bA9iAom2uTCoVhI/zdcABFSEuyjJoSLqoyRuW71kKvadvwbvcickvIU2UR2vacx+ dPCXVcjCn4mBzeTFde9xNsnWzgBzP7BlSHRfmtx/0WilF8v8mDcGedGe44VwRQqbM/Hx 5xdg==
MIME-Version: 1.0
X-Received: by 10.224.11.9 with SMTP id r9mr35167420qar.43.1407483717193; Fri, 08 Aug 2014 00:41:57 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Fri, 8 Aug 2014 00:41:57 -0700 (PDT)
In-Reply-To: <220fd568124845328a43e21bf5d31e28@SN2PR03MB077.namprd03.prod.outlook.com>
References: <20140807014913.4706.73259.idtracker@ietfa.amsl.com> <220fd568124845328a43e21bf5d31e28@SN2PR03MB077.namprd03.prod.outlook.com>
Date: Fri, 8 Aug 2014 15:41:57 +0800
Message-ID: <CAM+vMETqu8n0YDWQvFNy_1RvkrELjQREr1t=mQ2JDWdtz+cTUA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/-RyQerO3tf5aGkhnHHHfYH9CZr0
Cc: MIF Mailing List <mif@ietf.org>
Subject: Re: [mif] FW: I-D Action: draft-ietf-mif-mpvd-arch-03.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 08 Aug 2014 07:42:01 -0000

Hello Dmitry,

I posted the questions in other two threads, but didn't get response.
Could you kindly consider following questions into WGLC comments

Is there any conclusion if PVD rules conflict with RFC6731 and RFC4191?

Two particular cases are:

1)  Name resolution

Let's say, host A receives RDNSS Selection DHCPv6 Option with domain
name of example.com on interface 1.
It also receives PVD-ID of example.com on interface 2.

If the host A makes query for a.example.com, which interface should be selected

2) next hop

draft-ietf-mif-mpvd-arch-01 states:

   For each obtained destination
   address, the node shall perform a next-hop lookup among routers,
   associated with that PVD.


BRs

Gang

2014-08-07 9:53 GMT+08:00, Dmitry Anipko <Dmitry.Anipko@microsoft.com>om>:
> This revision should address the WGLC comments. If there are no additional
> comments, we'll do the language review (thanks Ian for the kind offer), and
> I'm following up with authors of the 2 IDs mentioned in the text, which have
> expired, for the proper replacements.
>
> -Dmitry
>
> -----Original Message-----
> From: mif [mailto:mif-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Wednesday, August 6, 2014 6:49 PM
> To: i-d-announce@ietf.org
> Cc: mif@ietf.org
> Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Multiple Interfaces Working Group of the
> IETF.
>
>         Title           : Multiple Provisioning Domain Architecture
>         Author          : Dmitry Anipko
> 	Filename        : draft-ietf-mif-mpvd-arch-03.txt
> 	Pages           : 22
> 	Date            : 2014-08-06
>
> Abstract:
>    This document is a product of the work of MIF architecture design
>    team.  It outlines a solution framework for some of the issues,
>    experienced by nodes that can be attached to multiple networks.  The
>    framework defines the notion of a Provisioning Domain (PvD) - a
>    consistent set of network configuration information, and PvD-aware
>    nodes - nodes which learn PvDs from the attached network(s) and/or
>    other sources and manage and use multiple PvDs for connectivity
>    separately and consistently.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-mif-mpvd-arch-03
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>