IETF Logo Mail Archive

Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Wed, 12 September 2018 10:55 UTC

Return-Path: <ietf@kuehlewind.net>
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 E444F1294D7 for <lisp@ietfa.amsl.com>; Wed, 12 Sep 2018 03:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 ayTHhBhE_Wci for <lisp@ietfa.amsl.com>; Wed, 12 Sep 2018 03:55:22 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70D52130E28 for <lisp@ietf.org>; Wed, 12 Sep 2018 03:55:22 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=DlJKPoVrV+nxcljrdahJSILXD5HmRTEptntk54OjPlcZxFJWIRQacOa4jxEcXrqcAwxyaF31M1W8dMtsx+jjn9rkq0oY9Uch4sILuNdrIILdTs8R2mX6hTiYCFx68vqn2ramtEtDIEWls41TmK62VCvRjRdeelPKfDQwLkGRbd8=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 21056 invoked from network); 12 Sep 2018 12:48:39 +0200
Received: from mue-88-130-61-212.dsl.tropolys.de (HELO ?192.168.178.24?) (88.130.61.212) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 12 Sep 2018 12:48:39 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <00DCC7FC-096E-4822-A702-2EE4C70327EB@gigix.net>
Date: Wed, 12 Sep 2018 12:48:38 +0200
Cc: Dino Farinacci <farinacci@gmail.com>, The IESG <iesg@ietf.org>, draft-ietf-lisp-rfc6833bis@ietf.org, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F740BE5-63AF-4D18-BD79-D7D6A352B40A@kuehlewind.net>
References: <153667812809.16741.10796738054406466412.idtracker@ietfa.amsl.com> <9D08CA59-8AC4-4866-944E-98553C37E547@gmail.com> <00DCC7FC-096E-4822-A702-2EE4C70327EB@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.3445.9.1)
X-PPP-Message-ID: <20180912104839.21047.88549@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/CcjMk-E0pVeP7VzoaeQLKILFZfQ>
Subject: Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 12 Sep 2018 10:55:25 -0000

Hi Luigi,

please see below.

> Am 12.09.2018 um 09:30 schrieb Luigi Iannone <ggx@gigix.net>:
> 
> Hi,
> 
> two quick comments inline.
> 
> 
>> On 11 Sep 2018, at 20:13, Dino Farinacci <farinacci@gmail.com> wrote:
>> 
>>> 3) Given the following statement:
>>> "Note that while this document assumes a LISP-ALT database mapping
>>> infrastructure to illustrate certain aspects of Map-Server and Map-
>>> Resolver operation..."
>>> it seems that RFC6836 should be a normative reference, as it might not be
>>> possible to understand all details explained in this doc with knowing ALT.
>> 
>> I would like the lisp-chairs and/or Deborah to comment on this.
>> 
> 
> IMO We can completely delete that sentence. The documents does a pretty good job to talk in general terms about the mapping system and the use of its front-end Map-Servers/Map-Resolvers.
> 
> In the few cases where something specific to ALT and DDT can be said the document actually does it.

Actually I brought this up because there were more cases where I found that ALT knowledge is needed. If you don’t want this to be a normative reference and remove the sentence above (which I’m not sure is helpful), please also double-check all other occurrences of ALT and make sure the discussed case is also understandable without ALT knowledge.

> 
> 
> 
>>> 4) Further I would also think that I-D.ietf-lisp-mn and I-D.ietf-lisp-pubsub
>>> should be normative references as the meaning of the respective bits it not
>>> further specified in this doc. Or can these bits just be ignored if
>>> I-D.ietf-lisp-mn and I-D.ietf-lisp-pubsub are not implemented? If so that
>>> should be stated.
>> 
>> I would like the lisp-chairs and/or Deborah to comment on this.
>> 
> 
> Those bits can be ignored if an implementer choses not to support those mechanisms.
> Hence, the documents do not really need to be normative.

Okay, that these bits can be ignored should be stated in the doc!

Mirja



> 
> Ciao
> 
> L.
> 
>

v2.23.0 | Report a Bug | By Email