Re: [mif-arch-dt] FW: New Version Notification for draft-anipko-mif-mpvd-arch-00.txt

["Dapeng Liu" <[e-mail]>]

Hi Dmitry,

If there is an idendification for PVD as a whole, then how to identify one
particular configuration element(for example, one DHCP server) belongs to
that PVD?

Thanks,

Regards,
Dapeng
-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Dmitry Anipko
Sent: Saturday, July 20, 2013 7:37 AM
To: Dapeng Liu; [e-mail]
Subject: Re: [mif-arch-dt] FW: New Version Notification for
draft-anipko-mif-mpvd-arch-00.txt

Hi Dapeng,

Thank you for reading the draft.

>> The question is: for each of the configuration elements, for example:
DNS, proxy, DHCP server etc there should be a PVD identification associates
with it or there is only one global identification for a PVD?

My reading of the pre-draft discussions and my thinking was that there is a
identification for PVD as a whole (I think what  you mean as the latter in
your sentence). Is there some scenario which, you think, requires identifier
for individual elements?

Thank you.


-----Original Message-----
From: Dapeng Liu [mailto:[e-mail]] 
Sent: Wednesday, July 17, 2013 8:51 PM
To: Dmitry Anipko; [e-mail]
Subject: RE: [mif-arch-dt] FW: New Version Notification for
draft-anipko-mif-mpvd-arch-00.txt

Hi Dmitry,

Thanks for posting the draft. I have a comment regarding how the PVD
identification works. As states in the draft, a PVD may have a PVD
identification with it, it may be a human readable identification. 
The question is: for each of the configuration elements, for example: DNS,
proxy, DHCP server etc there should be a PVD identification associates with
it or there is only one global identification for a PVD?

Thanks,
Dapeng
-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Dmitry Anipko
Sent: Sunday, July 14, 2013 12:24 PM
To: [e-mail]
Subject: [mif-arch-dt] FW: New Version Notification for
draft-anipko-mif-mpvd-arch-00.txt

Hi everyone.

I've just posted the first version of the MPD arch draft based on the
teleconfs and list discussions we've had so far. If possible, please take a
look before the Monday call and comment.

For some of the topics, which we touched but where I didn't feel like I had
enough information, for now I created placeholder sections with little / no
text.

Thank you,
Dmitry



________________________________________
From: [e-mail] <[e-mail]>
Sent: Saturday, July 13, 2013 9:19 PM
To: Dmitry Anipko
Subject: New Version Notification for draft-anipko-mif-mpvd-arch-00.txt

A new version of I-D, draft-anipko-mif-mpvd-arch-00.txt has been
successfully submitted by Dmitry Anipko and posted to the IETF repository.

Filename:        draft-anipko-mif-mpvd-arch
Revision:        00
Title:           Multiple Provisioning Domain Architecture
Creation date:   2013-07-13
Group:           Individual Submission
Number of pages: 9
URL:
http://www.ietf.org/internet-drafts/draft-anipko-mif-mpvd-arch-00.txt
Status:          http://datatracker.ietf.org/doc/draft-anipko-mif-mpvd-arch
Htmlized:        http://tools.ietf.org/html/draft-anipko-mif-mpvd-arch-00


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 Secretariat




_______________________________________________
mif-arch-dt mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mif-arch-dt








_______________________________________________
mif-arch-dt mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mif-arch-dt