Re: [netmod] ipv6 config parameters

Ladislav Lhotka <lhotka@cesnet.cz> Mon, 14 November 2011 10:15 UTC

Return-Path: <lhotka@cesnet.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DFCD21F8D74 for <netmod@ietfa.amsl.com>; Mon, 14 Nov 2011 02:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599]
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 jSW0tRHWkTn0 for <netmod@ietfa.amsl.com>; Mon, 14 Nov 2011 02:15:02 -0800 (PST)
Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) by ietfa.amsl.com (Postfix) with ESMTP id F100421F8D65 for <netmod@ietf.org>; Mon, 14 Nov 2011 02:15:01 -0800 (PST)
Received: from dhcp-9227.meeting.ietf.org (dhcp-9227.meeting.ietf.org [130.129.10.39]) by office2.cesnet.cz (Postfix) with ESMTPSA id 317D82CDE058; Mon, 14 Nov 2011 11:14:39 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/signed; boundary="Apple-Mail=_890AF7AC-425F-46EA-A70B-94F61C3DCEA6"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Ladislav Lhotka <lhotka@cesnet.cz>
In-Reply-To: <20111114091433.GA17181@elstar.local>
Date: Mon, 14 Nov 2011 18:14:32 +0800
Message-Id: <D052699D-0DFE-413B-A40C-7CC4EB710DCB@cesnet.cz>
References: <20111114.093601.320467224258500807.mbj@tail-f.com> <20111114091433.GA17181@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.1251.1)
Cc: netmod@ietf.org
Subject: Re: [netmod] ipv6 config parameters
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 10:15:04 -0000

On Nov 14, 2011, at 5:14 PM, Juergen Schoenwaelder wrote:

> On Mon, Nov 14, 2011 at 09:36:01AM +0100, Martin Bjorklund wrote:
>> Hi,
>> 
>> Here are two issues for the draft-ietf-netmod-ip-cfg document.
>> 
>> 
>> RFC 4862 (IPv6 Stateless Address Autoconfiguration) states:
>> 
>>   A node MUST allow the following autoconfiguration-related variable to
>>   be configured by system management for each multicast-capable
>>   interface:
>> 
>>     DupAddrDetectTransmits
>> 
>> Should we add this leaf to our data model?
> 
> If RFC 4862 says so...
> 
>> RFC 4861 (Neighbor Discovery in IPv6) states:
>> 
>>   A router MUST allow for the following conceptual variables to be
>>   configured by system management.
>> 
>>     <list of a handful of config params>
>> 
>> Should we add these variables to our data model, conditional on an
>> if-feature?    They are present in the IP-MIB.
> 
> The question here is what is in scope of this work and what is out of
> scope. Are we limiting this data model to the configuration of
> interfaces or do we include things happening on routers, like the
> configuration of routing advertisements. In fact, if we take a broad
> definition of the scope, we will have to work through
> 
> draft-ietf-6man-node-req-bis-11.txt
> 
> and all the mandatory stuff it references. And also 4941 comes into my
> mind and there is ongoing work on source address selection and even
> discussion today how to handle situations where you get potentially
> conflicting information via RAs and DHCP. Since it is unlikely that we
> will be successful covering everything configurable in the IP layer,
> we should in my view have a plan how to put things into manageable
> pieces.

Yes, that's why I don't want to have an ietf-ipv6-unicast-routing module as a part of the routing-cfg draft.

Lada

> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

--
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C