Re: [lisp] Fwd: Comments about draft-cheng-lisp-shdht-01

Michael Hoefling <hoefling@informatik.uni-tuebingen.de> Fri, 27 July 2012 09:09 UTC

Return-Path: <hoefling@informatik.uni-tuebingen.de>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B6621F855A for <lisp@ietfa.amsl.com>; Fri, 27 Jul 2012 02:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level:
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448]
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 yeyYr0RmZqJY for <lisp@ietfa.amsl.com>; Fri, 27 Jul 2012 02:09:58 -0700 (PDT)
Received: from mx5.informatik.uni-tuebingen.de (mx5.Informatik.Uni-Tuebingen.De [134.2.12.32]) by ietfa.amsl.com (Postfix) with SMTP id EC88321F8505 for <lisp@ietf.org>; Fri, 27 Jul 2012 02:09:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8B048528A for <lisp@ietf.org>; Fri, 27 Jul 2012 11:09:51 +0200 (MEST)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx5.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx5.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNfE9zq3SzLh for <lisp@ietf.org>; Fri, 27 Jul 2012 11:09:48 +0200 (MEST)
Received: from zcs-bs.informatik.uni-tuebingen.de (zcs-bs.Informatik.Uni-Tuebingen.De [134.2.12.62]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id 06D84525F for <lisp@ietf.org>; Fri, 27 Jul 2012 11:09:47 +0200 (MEST)
Received: from [134.2.11.130] (thanatos.Informatik.Uni-Tuebingen.De [134.2.11.130]) by zcs-bs.informatik.uni-tuebingen.de (Postfix) with ESMTP id D121C4B77373 for <lisp@ietf.org>; Fri, 27 Jul 2012 11:09:47 +0200 (CEST)
Message-ID: <50125AFA.4060802@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2012 11:10:18 +0200
From: Michael Hoefling <hoefling@informatik.uni-tuebingen.de>
Organization: Unversity of Tuebingen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: lisp@ietf.org
References: <20120727035927.0A19218C104@mercury.lcs.mit.edu>
In-Reply-To: <20120727035927.0A19218C104@mercury.lcs.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [lisp] Fwd: Comments about draft-cheng-lisp-shdht-01
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 09:09:59 -0000

Hello Noel,

Am 27.07.2012 05:59, schrieb Noel Chiappa:
>      >> From: Michael Hoefling <hoefling@informatik.uni-tuebingen.de>
>
>      >> Noel Chiappa write two drafts about the overall LISP architecture:
>      >>
>      >> There, it is stated that - in accordance to the standard documents -
>      >> ETRs are the only authoritative source for mapping information.
>
> Well, they are introductions, not protocol specifications, so do not expect to
> see every last detail in them. And they are also initial drafts, so there
> might be minor errors in them. So you should be wary of citing them as
> authorities on anything! :-)

Noted :)

> Also, in the introduction document I do in fact note there that there are
> _some_ circumstances in which the MS replies on behalf of the ETR: "in some
> circumstances it is advantageous to allow the MS to proxy reply on the ETR's
> behalf to Map-Request messages".

I had the proxy case in the back of my head but also my understanding 
and interpretation of the current LISP drafts - and your introduction of 
course.

However, I assume that the proxy reply mode should not be the default 
operation mode.

>      > From: cheng.li2@zte.com.cn
>
>      > In our drat, ETRs are still the authoritative source for mapping
>      > information.
>      >  ...
>      >  When an ETR sends a Map-Register Message requesting for the Map-Server
>      >  to proxy Map-Reply, it will set the p bit to 1.
>      > In our draft, SHDHT Nodes could be considered as Map-Servers which
>      > implement the "Proxy Map Reply" mode.
>
> I am not sure I understand what you mean here. Does the SHDHT node _always_
> reply to the ITR on behalf of the ETR? That is what I understand from reading
> the -00 version of the I-D, and you seem to confirm that above.
>
> However, the 'proxy reply' mode is only done when the _ETR asks_ for the MS
> to do it; the MS does not get to do it whenever it wants. If the ETR does not
> set the 'P' bit, the MS _cannot_ proxy reply on behalf of the ETR.

As I assumed above - no P-bit not proxy. Thanks for clarification.

> This is necessary for things like 'source-specific mappings' (where an ETR
> returns different mappings to different ITRs).

Isn't this possible in proxy mode as well or is the selection logic 
specific for ETRs? How is this currently achieved in DNS?

Regards,
Michael

-- 
Dipl.-Inform. Michael Hoefling, M.Sc.
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70507, fax: (+49)-7071/29-5220
mailto: hoefling@informatik.uni-tuebingen.de
http://kn.inf.uni-tuebingen.de/staff/hoefling