Return-Path: 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 E1AE01A89A2 for ; Mon, 29 Feb 2016 05:26:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.605 X-Spam-Level: X-Spam-Status: No, score=-1.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.006] autolearn=no 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 yKhCy0f5Lg1d for ; Mon, 29 Feb 2016 05:26:42 -0800 (PST) Received: from mail.zemris.fer.hr (gandalf.zemris.fer.hr [161.53.65.11]) by ietfa.amsl.com (Postfix) with ESMTP id ED0191A89A0 for ; Mon, 29 Feb 2016 05:26:40 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.zemris.fer.hr (Postfix) with ESMTP id B9CD53B7C096; Mon, 29 Feb 2016 14:26:38 +0100 (CET) X-Virus-Scanned: amavisd-new at zemris.fer.hr Received: from mail.zemris.fer.hr ([127.0.0.1]) by localhost (mail.zemris.fer.hr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhRH11OMfoDy; Mon, 29 Feb 2016 14:26:34 +0100 (CET) Received: from w540.sistemnet.local (Enel.zemris.fer.hr [161.53.65.34]) by mail.zemris.fer.hr (Postfix) with ESMTPSA id CB0553B7C077; Mon, 29 Feb 2016 14:26:34 +0100 (CET) To: mif@ietf.org References: From: =?UTF-8?Q?Stjepan_Gro=c5=a1?= Organization: UNIZG - FER Message-ID: <56D44703.7050700@fer.hr> Date: Mon, 29 Feb 2016 14:26:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rcx4xPDqN7734eBEjUCAbaV96mSmCSJaI" Archived-At: Subject: Re: [mif] next step for MIF PVD configuration X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 13:26:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rcx4xPDqN7734eBEjUCAbaV96mSmCSJaI Content-Type: multipart/alternative; boundary="------------020001000001090803000501" This is a multi-part message in MIME format. --------------020001000001090803000501 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi all! On 29.02.2016 11:21, Hui Deng wrote: > Hello all > > We had the concensus already about droping DHCP MPVD ID document,=20 > based on this, here chairs would like to understand whether MIF WG > has achieved the concensus on below two steps to deliver MPVD conf. > 1) step 1: using RA to get MPVD ID information > 2) step 2: using DNS to get other MPVD configuration. Since I didn't saw any discussions on this list about those proposals I have few questions/comments: 1. Is this only for IPv6, or it is for IPv4 too (step 2)? 2. Why only MPVD ID in RA? Why not other information too for which RA is a natural place to be? 3. Why turn DNS into a local network configuration protocol? SG --------------020001000001090803000501 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi all!

On 29.02.2016 11:21, Hui Deng wrote:
Hello all

We had the concensus already about droping DHCP MPVD ID document,=A0
based on this, here chairs would like to understand whether MIF WG
has achieved the concensus on below two steps to deliver MPVD conf.
1) step 1: using RA to get MPVD ID information
2) step 2: using DNS to get other MPVD configuration.

Since I didn't saw any discussions on this list about those proposals I have few questions/comments:

1. Is this only for IPv6, or it is for IPv4 too (step 2)?

2. Why only MPVD ID in RA? Why not other information too for which RA is a natural place to be?

3. Why turn DNS into a local network configuration protocol?

SG

--------------020001000001090803000501-- --rcx4xPDqN7734eBEjUCAbaV96mSmCSJaI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW1EcDAAoJEOggxEF22YTDAtMP/0TzxSwwAKtnVln8mbOPTakb 9lOoN7sHA77Z3H9+Y7uOQHPlS0ZA3KWEKJmGmk8v2gjlSvBBvIIAapF4qF03dGoH ggdRoNn/eMdXLqcfFLnzdNws3V0UIxPANyYyCvlXDlN47MW7QJawGEQCGQBn08Xf VgWDRCulcgn/ENptMFvFVJPbr9uvOxIYRTFoLeQ82vD83XjKxiXB9A66h+7N/k+K a/GW1RXzihMKlXkvmaSqk0a+d4JgpkSyiZxIYE71co37/oVrACQ9EmosCHnPJ0CE Hctcy5aTloY1b/cr4yJDngSqqjqgkae91koRsuc+gR1fDtQDhB/28CF5R0dWwDRE qtdjiHQa+NTcLySXHVivfm9x0qArmXSghG8X3TTzugy93OB7muODWSkBjcabNlDh MuD0hA+s0eO02RKNRgNBGLw6xjC3Cnniuz206PoOI2b0CWv3vkalt70IR7k7F+nG W/1pMlZV5Cj0ALZMUKH0JKJWD8hn/jR/x4c351teSO7+q8AJHG7HZ2sy6m3s/1SN n491Mu5Cz5LsPxs6BN9I8lMHMX/UplyDh2n5TGIayJxZhGLcR/Rr1pC/70CqFl7g 7y8UWV7DhCfz+fAWsHEr6UiNpbKGkcWWrlnR6mQcM/mb2f2I0N7z975yGhHJC95N yzSL03Tfki3HGjHBDJ1u =CE02 -----END PGP SIGNATURE----- --rcx4xPDqN7734eBEjUCAbaV96mSmCSJaI--