Re: [lisp] MS-SMR draft

Fabio Maino <fmaino@cisco.com> Fri, 06 April 2018 17:29 UTC

Return-Path: <fmaino@cisco.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 9634412025C for <lisp@ietfa.amsl.com>; Fri, 6 Apr 2018 10:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 OucvJtPwHaWn for <lisp@ietfa.amsl.com>; Fri, 6 Apr 2018 10:29:04 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC131200C5 for <lisp@ietf.org>; Fri, 6 Apr 2018 10:29:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2260; q=dns/txt; s=iport; t=1523035743; x=1524245343; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=zJnUuQwjXWPEJOMNsD9Ls3BQ3mZ8hX7nQNOtpLteIV0=; b=UHhQb5kEyD+3XJJmuGtzA9OPOahmGNwgwmYGZ4VkUeK6+WPBvY+R2siA QATBs0vHwoWaCXmAVlRiZ293zU9E4LINwEZT8Ek+cJccZ5F7BqpLmbpqH RfydM+gfIrVQDpmWu2XqkcopzO4d91NCQAtaVMT1qcaqHlwBj4AfWELO7 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AvAQDWrcda/4kNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYNCYW8og1+IAI0KgUsIIYEPhmKLdoF6CxgLhGACgjkhNBgBAgEBAQEBAQJsHAyFIwEBAQMBASEPAQU2GwsYAgImAgIhBjATBgIBAReEWgMVD6lTghyEV4I1DYErgX0FgQmGYoFUP4EuDIJWgk9CAQEDgTZvgjSCVAKMWIN0hkssCIVUhWKCdwaBMoYShHyHKYFzPIYugSUcOIFSMxoIGxU6gkOLEIVeHzCOGgEB
X-IronPort-AV: E=Sophos;i="5.48,415,1517875200"; d="scan'208";a="94721281"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2018 17:29:02 +0000
Received: from [10.41.33.250] ([10.41.33.250]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w36HT2IA023218 for <lisp@ietf.org>; Fri, 6 Apr 2018 17:29:02 GMT
To: lisp@ietf.org
References: <CA+YHcKFz=gJjSp-TXahA=65av6JX2G=EPJj=iV_XggKnqzV83g@mail.gmail.com> <C250775B-E482-4B03-9E13-1EF0E4D2B930@gmail.com> <CA+YHcKGp7m_ZD6er+Jc8kwO+eWHis10PPBG7N5dVzDj3N2pDmA@mail.gmail.com> <146E1710-D814-42F3-A9D7-FB5DBB2DED20@gigix.net> <BCAF7A0D-0ACB-4D7C-BF3B-5A6DD3F7111A@gmail.com>
From: Fabio Maino <fmaino@cisco.com>
Message-ID: <845781c5-9525-2308-5839-64840e24e348@cisco.com>
Date: Fri, 06 Apr 2018 10:29:02 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <BCAF7A0D-0ACB-4D7C-BF3B-5A6DD3F7111A@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/xeYpAWEm1CJyWvVp6_wjbhVst5Y>
Subject: Re: [lisp] MS-SMR draft
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Apr 2018 17:29:06 -0000

I agree with Dino.

Fabio

On 4/6/18 8:07 AM, Dino Farinacci wrote:
> Well it wasn’t a previous WG solution. It was an individual submission that one vendor implemented. Since the WG supports pubsub going forward, I think a forward pointer from the individual submission to the WG document is sufficient.
>
> Dino
>
>> On Apr 6, 2018, at 1:04 AM, Luigi Iannone <ggx@gigix.net> wrote:
>>
>> Hi,
>>
>> I was wondering….. why not putting this as an appendix in the pubsub document? Stating that was the previous solution for what pubs does and that is kept in appendix as informational material.
>>
>> any thoughts?
>>
>> L.
>>
>>
>>> On 5 Apr 2018, at 23:17, Alberto Rodriguez-Natal <rodrigueznatal@gmail.com> wrote:
>>>
>>> Sounds good to me Dino. I'll wait for the adoption call of lisp-pubsub to end and will update this document as appropriate.
>>>
>>> Thanks,
>>> Alberto
>>>
>>> On Thu, Apr 5, 2018 at 9:47 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> Just one editorial comment Alberto. If the pubsub draft is about to be a working group document, maybe this document should point to draft-ietf-lisp-pubsub-00?
>>>
>>> Dino
>>>
>>>> On Apr 4, 2018, at 11:49 PM, Alberto Rodriguez-Natal <rodrigueznatal@gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> We have just posted an updated version of the MS-originated SMRs draft [1]. The revised document discusses how/when the MS is supposed to send SMRs and includes a note pointing to draft-rodrigueznatal-lisp-pubsub as the preferred PubSub mechanism.
>>>>
>>>> Let us know if you have any comment. As discussed in London, we would like to move forward with this as informational (and preferably as a WG item).
>>>>
>>>> Thanks,
>>>> Alberto
>>>>
>>>> [1] https://tools.ietf.org/html/draft-rodrigueznatal-lisp-ms-smr-06
>>>>
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp