Re: [lisp] 6833bis - NMR with locator count !=0

"Victor Moreno (vimoreno)" <vimoreno@cisco.com> Tue, 22 August 2017 18:46 UTC

Return-Path: <vimoreno@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 D0516132026 for <lisp@ietfa.amsl.com>; Tue, 22 Aug 2017 11:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 EcpX8u0qltUG for <lisp@ietfa.amsl.com>; Tue, 22 Aug 2017 11:46:51 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC8D31323B8 for <lisp@ietf.org>; Tue, 22 Aug 2017 11:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3778; q=dns/txt; s=iport; t=1503427611; x=1504637211; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9BnMp7PInN8WZdz2GYPG1V5M9eMZfG6zG7mAXb8q5KI=; b=gJMvTsYMBMO09wXbU7Pu2qrkXla4BcNK53Pa6Ttv1eR3corOP+PNmO3e xXuyMpT8kyhYAVt1GIN5KpA0PdF5NQlVQTNFhWWWu0Tbo5v1VZTTxls8z GU2XTkDkbOSCqNnkJNSFY9Q3bjJFRyA6GRK8KEu+toM+NLf2x4xqTrlsQ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmAABde5xZ/4gNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1pkgRUHjgyQG4Fulh8OggQhC4UbAhqEFz8YAQIBAQEBAQEBayiFGAEBAQECAQEBIRE6CwULAgEIGAICJgICAiULFRACBA4FiikIEK0mgiaLYQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQ2CHYICgUyBYyuCfIQ9NoMTMIIxBaBVApRBghCFYopuligBHziBCncVSRIBhQQFF4FndooGgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,413,1498521600"; d="scan'208";a="474745597"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Aug 2017 18:46:50 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7MIknpA023953 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Aug 2017 18:46:50 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 22 Aug 2017 13:46:49 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1210.000; Tue, 22 Aug 2017 13:46:49 -0500
From: "Victor Moreno (vimoreno)" <vimoreno@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
CC: LISP mailing list list <lisp@ietf.org>
Thread-Topic: [lisp] 6833bis - NMR with locator count !=0
Thread-Index: AQHTGwzqsqFWeSwYqUmzA1VIigsqYqKQOQEAgAAFmoCAAIhUgIAARMYA
Date: Tue, 22 Aug 2017 18:46:49 +0000
Message-ID: <4AFEF314-C5C4-4F32-9D1A-0AA3DF8395AF@cisco.com>
References: <6467BB43-AB19-48C4-A3FD-34D5C2E092E8@cisco.com> <d6318116-0157-302d-abe3-4181c7859e19@joelhalpern.com> <CE2B6A47-99E2-4CA9-B28F-A55A24ADBF24@cisco.com> <3c4a398a-e8dd-07fa-f18e-4acb36779789@joelhalpern.com>
In-Reply-To: <3c4a398a-e8dd-07fa-f18e-4acb36779789@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.157.244]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3BE5F8B63CF9794894795288861636B1@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/rusjxWhiG4B0TDqWmfaB4lMnBJ8>
Subject: Re: [lisp] 6833bis - NMR with locator count !=0
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: Tue, 22 Aug 2017 18:46:53 -0000

Thanks Joel,

That would be ideal, could you please shed some light on what you see as “suitable indications” in a map-reply?

The two things that are compelling about the NMR are:

1. Dynamic calculation of covering prefix for the non-EID requested
2. short TTL of the mapping so that we continue requesting more specifics (the ITR implementations usually know to assign a short TTL when the map-reply is an NMR [loc-count == 0])

If I can continue to achieve those without manually configuring the PETR RLOCs at the ITRs, we have what we need. But I didn’t see a way to do this in the framework of the current spec.

-v

> On Aug 22, 2017, at 7:40 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> Now speaking only as an individual:
> 
> If you want the Proxy ETR to be in the mapping system, wouldn't it make more sense to have it register the address block for which it is serving as a proxy?  With suitable indications so that ITRs which learn of it get back the bits that tell them to continue askign about more specifics?  That would seem to result in existing ITRs working with these newer PETRs without any changes.
> 
> Yours,
> Joel
> 
> On 8/22/17 2:32 AM, Victor Moreno (vimoreno) wrote:
>> Would be mainly conveying the RLOCs of the feasible PETRs dynamically.
>> As PETRs are brought on-line in the network, they can be configured/added in the Mapping System, rather than touching a multitude of ITRs.
>> This would also allow a more elegant definition for the support of a default exit to the Internet in the Extranet case defined in the lisp-vpn draft. In this scenario, the RLOC record would convey the RLOC of the PETR plus the IID to which the Internet connects at the PETR.
>> -v
>>> On Aug 21, 2017, at 11:12 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>>> 
>>> Can you explain what information you are conveying with the RLOCs?  I think we would need a clear use case before changing the spec.
>>> 
>>> Yours,
>>> Joel
>>> 
>>> On 8/22/17 2:07 AM, Victor Moreno (vimoreno) wrote:
>>>> Dear WG,
>>>> As we put some of our specifications to the test in deployments, we have found the ability to return RLOCs dynamically in an NMR to be compelling in a variety of deployment scenarios. Particularly in Networks with multiple Internet exit points.
>>>> What are the thoughts of the group on allowing NMRs with a locator count !=0?
>>>> One option to indicate that a map-reply is an NMR could be to assign one of the reserved bits as an NMR flag.
>>>> Would like to gauge the inclination of the WG before proposing text/edits.
>>>> -v
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp