Re: [multimob] draft-ietf-multimob-pmipv6-source-06

"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Mon, 06 January 2014 22:51 UTC

Return-Path: <prvs=07618bfa0=schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F061AE2B5 for <multimob@ietfa.amsl.com>; Mon, 6 Jan 2014 14:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.538] 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 x72QJbC84lEy for <multimob@ietfa.amsl.com>; Mon, 6 Jan 2014 14:51:28 -0800 (PST)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by ietfa.amsl.com (Postfix) with ESMTP id A08DF1AE2B2 for <multimob@ietf.org>; Mon, 6 Jan 2014 14:51:28 -0800 (PST)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 06 Jan 2014 23:51:19 +0100
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 9F3A010679D7; Mon, 6 Jan 2014 23:51:19 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19950-07; Mon, 6 Jan 2014 23:51:19 +0100 (CET)
Received: from [192.168.178.33] (g231224020.adsl.alicedsl.de [92.231.224.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id 0368F10679CF; Mon, 6 Jan 2014 23:51:18 +0100 (CET)
Message-ID: <52CB3363.1000407@informatik.haw-hamburg.de>
Date: Mon, 06 Jan 2014 23:51:15 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: sarikaya@ieee.org
References: <CAC8QAccA-Sa+apaX4AJBB7M0Pm1iWM5crmrCrZudXfBb+NdBzQ@mail.gmail.com> <52C9DBFB.2040803@informatik.haw-hamburg.de> <CAC8QAceSkfgfdap40dqEGEFS94gBA10dNnq=SbocFsBZQBPHxg@mail.gmail.com> <52CAF4E4.70203@informatik.haw-hamburg.de> <CAC8QAcdd_cR5zcgaaovr6_yBp0GXozFdZR+F=vmrivJghDsEJQ@mail.gmail.com>
In-Reply-To: <CAC8QAcdd_cR5zcgaaovr6_yBp0GXozFdZR+F=vmrivJghDsEJQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Cc: "multimob@ietf.org" <multimob@ietf.org>
Subject: Re: [multimob] draft-ietf-multimob-pmipv6-source-06
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob/>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 22:51:31 -0000

Hi Behcet,

I'll shorten the history to make things more readable ...

On 06.01.2014 23:22, Behcet Sarikaya wrote:

>         Sec. 3.2.4
>         the multicast
>              routing information base (MRIB) of the MAG - I thought this
>         was not
>         possible? later on seems to be clarified in Sec. 4.3 & 4.4 (I mean
>         according to our face-to-face conversations in the past?)
>
>
>     In this draft, we describe the setting of an MRIB in agreement with
>     the topology of the access network. Like a unicast RIB, an MRIB can
>     of course always express a regular, topology-oriented routing
>     according to destination addresses in IP headers.
>
>     Our discussions, which also took place on the mailing list earlier
>     and in WG meetings, were concerned with policy-based PMIP routing
>     according to source addresses. This cannot be expressed in a regular
>     MRIB.
>
>
> Where did you get this from? Any references?
>

Well, the relevant part in the context of this draft is that one can 
express regular, topology-oriented routing in an access network within a 
regular routing table (unicast as well as multicast). It is 'sort of the 
core of IP routing', so I guess there is no doubt about that and a 
reference is not needed (otherwise we would need to recall the 
fundamentals of IP routing).

The other side about policy-based routing in PMIP was discussed some 
time ago, but is not mentioned in the draft. So there is no need to make 
a reference to it.

If you are interested in the discussion, I think major parts have been 
on the list about two years ago. There were contributions from Sri and 
in particular Stig provided longer explanations on what can be possibly 
done and what not.

But this is all outside the current spec (and of any spec that is 
MULTIMOB WG Item), so no need to return to it.

Cheers,

Thomas


-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °