[v6ops] comments about draft-townsley-troan-ipv6-ce-transitioning-02

Tassos Chatzithomaoglou <achatz@forthnetgroup.gr> Thu, 29 March 2012 12:41 UTC

Return-Path: <achatz@forthnetgroup.gr>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB0321F8AAA for <v6ops@ietfa.amsl.com>; Thu, 29 Mar 2012 05:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 kn8MY1UrbvwR for <v6ops@ietfa.amsl.com>; Thu, 29 Mar 2012 05:41:08 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.107]) by ietfa.amsl.com (Postfix) with ESMTP id 12C3D21F85B6 for <v6ops@ietf.org>; Thu, 29 Mar 2012 05:41:06 -0700 (PDT)
Received: from mx-av-06.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.14.4/8.14.4) with ESMTP id q2TCf5YS024257 for <v6ops@ietf.org>; Thu, 29 Mar 2012 15:41:05 +0300
Received: from MX-IN-01.forthnet.gr (mx-in-01.forthnet.gr [193.92.150.23]) by mx-av-06.forthnet.gr (8.14.4/8.14.4) with ESMTP id q2TCf5Z8004668 for <v6ops@ietf.org>; Thu, 29 Mar 2012 15:41:05 +0300
Received: from [10.216.6.237] ([93.158.43.148]) (authenticated bits=0) by MX-IN-01.forthnet.gr (8.14.4/8.14.4) with ESMTP id q2TCeo4W031662; Thu, 29 Mar 2012 15:40:52 +0300
Authentication-Results: MX-IN-01.forthnet.gr smtp.mail=achatz@forthnetgroup.gr; auth=pass (PLAIN)
Message-ID: <4F745859.50207@forthnetgroup.gr>
Date: Thu, 29 Mar 2012 14:40:57 +0200
From: Tassos Chatzithomaoglou <achatz@forthnetgroup.gr>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: v6ops@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [v6ops] comments about draft-townsley-troan-ipv6-ce-transitioning-02
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 12:41:09 -0000

Hi,

I had a quick look at this draft and i wanted to make some comments.

First, i believe it would be good to have some examples of the 
Information Bases (their structure) used under the Terminology paragraph.

>    SRIB                      A Source Address Routing Information Base
>                               containing an entry per delegated prefix.
>                               Each entry points to one or more
>                               Destination Address Routing Tables (DRIB).
Replace "Destination Address Routing Tables" with "Destination Address 
Routing Information Base (DRIB) tables "?


> MH-1:  An IPv6 CE router MUST create a separate DRIB for each WAN
>            interface (real or virtual) and installs a route for the
>            associated delegated prefix, default route and more specific
>            routes.

What kind of route is installed in the DRIB  (pointing to the WAN?) for 
the associated delegated prefix?
Or does this refer to a route pointing to a LAN interface?

> MH-2:  An IPv6 CE router MUST create an SRIB containing entries for
>            associated delegated prefixes.  Each entry points to one or
>            more DRIBs.  An entry points to multiple DRIBs only in the
>            case where an identical delegated prefix is associated with
>            multiple WAN interfaces.

I guess the last paragraph refers to when having two or more connections 
to the same ISP.
Can't the same DRIB be used in that case, especially if the NH is the same?
There is also the following reference under 3, which forbids it, but 
there could be a pointer from each WAN interface to the DRIB(s).

> The CE
>     router has a single SRIB, and one DRIB associated with each WAN
>     Interface.

> This is important not only
>     in order to choose the best path, but also because the networks that
>     the CE are connected to typically employ source address verification
>     mechanisms.

Replace "verification" with "validation" in order to be in accordance 
with savi?

>   MH-3:  When forwarding a packet from a LAN interface, the CE router
>            MUST do a longest matching lookup based on the packet's Source
>            Address in the SRIB.  A Destination Address lookup is then
>            performed in the corresponding DRIB or DRIBs.  When there are
>            multiple equal matches, the route with the lowest cost is
>            chosen.

Who defines the cost and what exactly is it?
Is this different from the following under 4.2?
> If more than one
>     interface is selected (which will be the case when more than one
>     active WAN interface programs a default route in the RIB), then
>     packets are sent via the interface with the highest configured
>     preference.  If the preference is the same, packets may be load-
>     balanced.

>   6RDS-2:  By default, the 6rd virtual interface MUST be assigned a
>              higher routing cost than a native IPv6 interface.

Is this the same as above too?
If i'm not mistaken, in your draft routes have costs/metrics (lower is 
better) and interfaces have preferences (higher is better), but it would 
be good to clarify that.


> As entries in
>     the NPIB table naturally time out, or if the Native interface is
>     deactivated, the CGN within the DS-Lite AFTR takes over the NAPT
>     state of the CE router.
Replace "state" with "functionality"?
One might think that the current state is "transferred" as it is.

> The following table indicates a basic ordering
>     (least to most preferred) for some of the known IPv4 extension and
>     IPv6 transition mechanisms under development today.

Since "Native IPv4" (which is neither IPv4 extension, nor IPv6 
transition) is also included in the table, maybe the above should be 
rephrased.

Also, i didn't notice any reference to the packets (or traffic in 
general) originating from or terminating to the CER itself. Shouldn't 
that be included too?

-- 
Tassos