Re: [netmod] ipv6 config parameters

Ladislav Lhotka <lhotka@cesnet.cz> Mon, 14 November 2011 14:40 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 3AAD311E8170 for <netmod@ietfa.amsl.com>; Mon, 14 Nov 2011 06:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 fFTiOJbtrZ9m for <netmod@ietfa.amsl.com>; Mon, 14 Nov 2011 06:40:14 -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 7585411E8090 for <netmod@ietf.org>; Mon, 14 Nov 2011 06:40:14 -0800 (PST)
Received: from dhcp-403d.meeting.ietf.org (dhcp-403d.meeting.ietf.org [130.129.64.61]) by office2.cesnet.cz (Postfix) with ESMTPSA id 9B1EF2CDE058; Mon, 14 Nov 2011 15:40:11 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/signed; boundary="Apple-Mail=_52A0DDD0-1DA8-41D0-A557-5F2A7E8AECA0"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Ladislav Lhotka <lhotka@cesnet.cz>
In-Reply-To: <20111114.121729.815594150126157417.mbj@tail-f.com>
Date: Mon, 14 Nov 2011 22:40:04 +0800
Message-Id: <51727BD7-C77D-4C69-85F6-3EDEAF0798C6@cesnet.cz>
References: <20111114103631.GA17767@elstar.local> <33B7505D-9F75-4FA2-9771-885FBEB60453@cesnet.cz> <20111114110428.GA17874@elstar.local> <20111114.121729.815594150126157417.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
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 14:40:15 -0000

On Nov 14, 2011, at 7:17 PM, Martin Bjorklund wrote:

> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>> On Mon, Nov 14, 2011 at 06:45:20PM +0800, Ladislav Lhotka wrote:
>>> Firstly, it should define analogical things as the
>>> ipv4-unicast-routing module now provides, such as IPv6 route content
>>> - in most cases this part would only require to replace
>>> inet:ipv4-{address,prefix} with the IPv6 counterpart. 
>>> 
>>> But beyond that, a whole bunch of other IPv6-specific parameters
>>> would be needed, as you wrote above. 
>>> 
>> 
>> OK. I think our disconnect is that I do not consider things like ND
>> parameters or RA config a subject of the routing module while you seem
>> to do.
> 
> Section 12 of draft-ietf-6man-node-req-bis-11 says:
> 
>   This section defines general host considerations for IPv6 nodes that
>   act as routers.  Currently, this section does not discuss routing-
>   specific requirements.
> 
> and then it talks about ND and RA etc.  So I believe we should not
> blur this distinction.

I don't mind if we agree on another organization, but I think it should be done in the same way for IPv4 and IPv6. So probably you should also define the contents of IPv4 & IPv6 unicast routes in the ip-cfg module. For IPv4, it is currently done in the ipv4-unicast-routing module.

Lada

> 
> 
> /martin

--
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C