Re: [mif] New Charter Items

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Wed, 02 March 2016 23:51 UTC

Return-Path: <sgundave@cisco.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 734D51B355F for <mif@ietfa.amsl.com>; Wed, 2 Mar 2016 15:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.507
X-Spam-Level:
X-Spam-Status: No, score=-14.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 2zdGM3eeNUCU for <mif@ietfa.amsl.com>; Wed, 2 Mar 2016 15:51:55 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEDFD1B355E for <mif@ietf.org>; Wed, 2 Mar 2016 15:51:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2468; q=dns/txt; s=iport; t=1456962715; x=1458172315; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=5BHCn6uS9S7c+E8n/1/qdhcyqSong1qNn/4jVi0Slq4=; b=evRB2klXPNx4u1qoBXqCrVMjGlqAjbLphdoealnmsP1HslzPKlmj39Of LbiS3n2OFJGSD07opw5pW/u4Lkv8xbh7IX0L9xA81SE4RDb7krU8ejU0E v+/HUf0lYESSsugIJRPy4qrf7PVitVPxpBLBvd+VkNN3oFMysLJZ6D4jj w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AQBlfNdW/5ldJa1egzpSbagDkiMBD?= =?us-ascii?q?YFnFwqFbgKBPzgUAQEBAQEBAWQnhEEBAQEDAQEBATc0CwULAgEIGB4QIQYLJQI?= =?us-ascii?q?EDgWIDAMKCA63TA2ENQEBAQEBAQEBAQEBAQEBAQEBAQEBAREEhhKBbIJOgjqBY?= =?us-ascii?q?xaDLYEPBY0siWYBiEiDJoF0jnaHCIdDAR4BAUKDZGqIYAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.22,531,1449532800"; d="scan'208";a="243428026"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2016 23:51:55 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u22NpsdG021280 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 2 Mar 2016 23:51:55 GMT
Received: from xch-aln-007.cisco.com (173.36.7.17) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 2 Mar 2016 17:51:54 -0600
Received: from xch-aln-007.cisco.com ([173.36.7.17]) by XCH-ALN-007.cisco.com ([173.36.7.17]) with mapi id 15.00.1104.009; Wed, 2 Mar 2016 17:51:53 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
Thread-Topic: [mif] New Charter Items
Thread-Index: AQHRdH6KMsB4v/QegEWXN3aRhswPTZ9HNeEA//+eIFc=
Date: Wed, 2 Mar 2016 23:51:53 +0000
Message-ID: <3B16CA0F-EA15-4CBD-93FA-DCFD65FE7204@cisco.com>
References: <39E5345B-04C4-4149-A1A6-F0F5F4988C16@gmail.com>, <56D77A54.60408@gmail.com>
In-Reply-To: <56D77A54.60408@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/ICbxN8n0PX4yk7vD5GBilxG9lf4>
Cc: "mif@ietf.org List" <mif@ietf.org>, Margaret Cullen <margaretw42@gmail.com>
Subject: Re: [mif] New Charter Items
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Mar 2016 23:51:57 -0000

+1

I missed the last meeting and looks like I missed this discussion and the conclusions around this new approach.




Sent from my iPad

> On Mar 3, 2016, at 5:12 AM, Jouni Korhonen <jouni.nospam@gmail.com>; wrote:
> 
> Got questions & observations here..
> 
> 3/2/2016, 4:24 AM, Margaret Cullen kirjoitti:
>> 
>> At the last IETF meeting, and later on the mailing list, we reached consensus that we would use a two-step approach for the configuration of explicit PVDs.  RAs would be used to provide the information to do a second-step look up, including the PVD name.  Then a second step would be used to look up further information about the PVD.
>> 
>> The only proposal we currently have on the table for a second-step look-up is a DNS look-up, and no one seems to proposing any other second step, so I believe there are three things that we need to define in order for this to work:
>> 
>> - An NTP server option for RAs, so that DNSSEC can be used for the lookup.
>> - A PVD Name option for RAs, so that we can tell hosts what PVD to look up.
> 
> I thought we already got a WG I-D that is able to carry required name information if needed - maybe not in the "format" at the moment folks want it to be but it is up to WG to steer the content, right?
> 
>> - What PVD information can be stored in the DNS and how it will be retrieved.
> 
> While DNS is a good thing and actually a good idea in the context we are discussing here, few things to think in addition to those already found in the meeting minutes: does not quite work if DNS is not there and going to DNS all time even for the simplies form of PVD configuration seems a bit unefficient. These are not really concern of homenet type setups but maybe for other deployments where links come and go.
> 
> My 0.02ZWD,
>    Jouni
> 
> 
> 
>> 
>> Those things would need to be added to our charter, so that we can accept corresponding work items.
>> 
>> Does anyone have any objection to adding these three things to the MIF charter?  If not, the chairs and the AD will put together a propos
>> 
>> _______________________________________________
>> 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