Re: [lisp] I-D Action: draft-ietf-lisp-pubsub-05.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 20 March 2020 14:45 UTC

Return-Path: <jmh@joelhalpern.com>
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 D583B3A09D0 for <lisp@ietfa.amsl.com>; Fri, 20 Mar 2020 07:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 DrZKRWXvmKmm for <lisp@ietfa.amsl.com>; Fri, 20 Mar 2020 07:45:00 -0700 (PDT)
Received: from mxa2.tigertech.net (mxa2.tigertech.net [208.80.4.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2EDD3A09B8 for <lisp@ietf.org>; Fri, 20 Mar 2020 07:43:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 48kRNk0Jvnz6GDCJ; Fri, 20 Mar 2020 07:43:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1584715430; bh=IOZVXLV7sGtlOwPXNzMdSOUCGwLmlgQvw7i1EIzQCys=; h=Subject:To:References:From:Date:In-Reply-To:From; b=IXr3bWZ2O98ZXaPC9xY/0e0YbnR3QBJAq1ZlXJJR8Z+5nE3Rlo9f8kTkOe2dNBj0i CVs+jnHo8LzcUSouojVs9AYVMWpBNzM0GgNgme9JRaWaxaEyQGpu9P5BsdrLQpglyk +MXOWcbC3OlKdnEjupaQ28R9U8AtfMRbS/T1GN00=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 48kRNj2Mv9z6GDBy; Fri, 20 Mar 2020 07:43:49 -0700 (PDT)
To: mohamed.boucadair@orange.com, "lisp@ietf.org" <lisp@ietf.org>
References: <158457900549.29358.17328147055555531752@ietfa.amsl.com> <1ea47e11-546a-39a0-4d10-6fd62d74a377@joelhalpern.com> <787AE7BB302AE849A7480A190F8B933031479CA4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <871b7b56-6b38-3cbc-3f18-1c7daf2cb125@joelhalpern.com>
Date: Fri, 20 Mar 2020 10:43:48 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B933031479CA4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/3lGx-MUObk_VW3dFDMNaeBi_nBY>
Subject: Re: [lisp] I-D Action: draft-ietf-lisp-pubsub-05.txt
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: Fri, 20 Mar 2020 14:45:12 -0000

Thanks.  That will work fine.
Yours,
Joel

On 3/20/2020 5:50 AM, mohamed.boucadair@orange.com wrote:
> Hi Joel,
> 
> Good catch.
> 
> I think we just need to delete that second sentence. The behavior when pubsub is not supported is covered by this text:
> 
>     Upon receipt of the Map-Request, the Map-Server processes it as
>     described in [I-D.ietf-lisp-rfc6833bis].
> 
> The failure cases we wanted to cover are those in:
> 
>     The subscription of an xTR-ID to the list of subscribers for the EID-
>     Record may fail for a number of reasons.  For example, because of
>     local configuration policies (such as accept and drop lists of
>     subscribers), or because the Map-Server has exhausted the resources
>     to dedicate to the subscription of that EID-Record (e.g., the number
>     of subscribers excess the capacity of the Map-Server).
> 
> Cheers,
> Med
> 
>> -----Message d'origine-----
>> De : lisp [mailto:lisp-bounces@ietf.org] De la part de Joel Halpern
>> Envoyé : jeudi 19 mars 2020 17:25
>> À : lisp@ietf.org
>> Objet : Re: [lisp] I-D Action: draft-ietf-lisp-pubsub-05.txt
>>
>> I was reading this draft again to think about the questions Alberto
>> raised on the list.  In doing so, I came across something that I think
>> needs to be clarified.
>>
>> In section 5, I see the following two sentences:
>>    If the subscription fails, the Map-Server MUST send a Map-Reply to
>>    the originator of the Map-Request, as described in
>>    [I-D.ietf-lisp-rfc6833bis].  This is also the case when the Map-
>>    Server does not support PubSub operation.
>>
>> I understand the first sentence.  The second sentence appears to cover
>> two different cases.  One case is where the Map-Server understands
>> PubSub, but does not accept it.  Okay.  I can see an error in that
>> case.
>>    But, as written, this seems to be intended to apply to a Map-Server
>> that has never heard of the PubSub extension.  Such a Map-Server will
>> ignore the I bit and ignore the N bit.  It will not know that this is
>> a
>> PubSub request, and as such will not generate an error.  I have no
>> problem with generating an error in the known but not supported case.
>> Can we (when we revise the draft) clarify the text?
>> (It took me a little bit to realize that this text probably meant the
>> known but not supported case, as it was the unknown case that came to
>> mind first.)
>>
>> Yours,
>> Joel
>>
>> On 3/18/2020 8:50 PM, internet-drafts@ietf.org wrote:
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>> This draft is a work item of the Locator/ID Separation Protocol WG
>> of the IETF.
>>>
>>>           Title           : Publish/Subscribe Functionality for LISP
>>>           Authors         : Alberto Rodriguez-Natal
>>>                             Vina Ermagan
>>>                             Johnson Leong
>>>                             Fabio Maino
>>>                             Albert Cabellos-Aparicio
>>>                             Sharon Barkai
>>>                             Dino Farinacci
>>>                             Mohamed Boucadair
>>>                             Christian Jacquenet
>>>                             Stefano Secci
>>> 	Filename        : draft-ietf-lisp-pubsub-05.txt
>>> 	Pages           : 12
>>> 	Date            : 2020-03-18
>>>
>>> Abstract:
>>>      This document specifies an extension to the use of Map-Request
>> to
>>>      enable Publish/Subscribe (PubSub) operation for LISP.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-lisp-pubsub/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-lisp-pubsub-05
>>> https://datatracker.ietf.org/doc/html/draft-ietf-lisp-pubsub-05
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-pubsub-05
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>>
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp