IETF Logo Mail Archive

[lisp] Review 6833bis-08 - General and NMR

"Victor Moreno (vimoreno)" <vimoreno@cisco.com> Mon, 19 March 2018 14:18 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 37141126FB3 for <lisp@ietfa.amsl.com>; Mon, 19 Mar 2018 07:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 iExCbuTI7F65 for <lisp@ietfa.amsl.com>; Mon, 19 Mar 2018 07:18:05 -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 2FC65126E64 for <lisp@ietf.org>; Mon, 19 Mar 2018 07:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9868; q=dns/txt; s=iport; t=1521469085; x=1522678685; h=from:to:subject:date:message-id:mime-version; bh=ffpNbZ3hffsg/zj//2E0eyoAfbqGA0zIpNMc20RCLtE=; b=OuxJi24a4fgTQ83ZKk+AR6RqlZM9+eQWZsZ9JIVaglXqd3L3rHiTNwgS On+C73hcV8Wo5be8a1+k4SDwqbpzVO11AQ4wZgDo7lmaGbKHDkbtdhyY5 hrtGsmbRJe2pT9YbRk16IZtOcD3i36Ku9MFhhoSfBSyWSiSMC5sKPIVHN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CcAgDqxa9a/5ldJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYMjLYFYMoNTmBSCfhuOcYUPFIF+C4UsgyYhNhYBAgEBAQEBAQJrKIVPaAFKAgQwJwSER2Sob4ImhG6DaYIOhTOCFYFVgVQogkUzhE4RDwKDHjCCMQOYNgkCjy+NLZAOAhETAYEpASUMJUCBEnAVZAGCGYIxG4EBAQiNFI4+gTGBGAEBAQ
X-IronPort-AV: E=Sophos; i="5.48,330,1517875200"; d="scan'208,217"; a="85671664"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Mar 2018 14:18:04 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w2JEI4TT007814 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <lisp@ietf.org>; Mon, 19 Mar 2018 14:18:04 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 19 Mar 2018 09:18:03 -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.1320.000; Mon, 19 Mar 2018 09:18:03 -0500
From: "Victor Moreno (vimoreno)" <vimoreno@cisco.com>
To: "lisp@ietf.org list" <lisp@ietf.org>
Thread-Topic: Review 6833bis-08 - General and NMR
Thread-Index: AQHTv40XPp8/qKn/L0Wt0SnoKHiq3Q==
Date: Mon, 19 Mar 2018 14:18:03 +0000
Message-ID: <6AB4517E-D36F-4B90-9D91-5EB77B109831@cisco.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.61.101.189]
Content-Type: multipart/alternative; boundary="_000_6AB4517ED36F4B909D915EB77B109831ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/yGqHUtun8-AFq2ryl-aYfWS5chA>
Subject: [lisp] Review 6833bis-08 - General and NMR
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: Mon, 19 Mar 2018 14:18:07 -0000

Dear WG,

I did a quick review of rfc6833bis-08. Some comments/suggestions



1. Section 5.8. Encapsulated Control Message Format. There is a reference to LH, it is not spelled out anywhere. I assume this means Lisp Header.

2. Section 5.8. On page 27, there is a figure/header format showing the AD Type and Authentication Data Content, which is not referenced anywhere. Looks like it needs to be removed.

3. Section 8.3/8.4. The text is limited to recommending exclusively a Native Forward action code. However the definition of the Map-reply message in section 5.4 allows 8 possible action codes and specifies 6 possible actions. If the WG agrees I can suggest text that would generalize the recommended processing behaviors described in 8.3 to allow the inclusion and use of the specified actions in the case of NMRs.

   8.3.  Map-Server Processing
   Once a Map-Server has EID-Prefixes registered by its client ETRs, it
   can accept and process Map-Requests for them.
   In response to a Map-Request (received over the ALT if LISP+ALT is in
   use), the Map-Server first checks to see if the destination EID
   matches a configured EID-Prefix.  If there is no match, the Map-
   Server returns a Negative Map-Reply with action code "Natively-
   Forward" and a 15-minute TTL.  This MAY occur if a Map Request is
   received for a configured aggregate EID-Prefix for which no more-
   specific EID-Prefix exists; it indicates the presence of a non-LISP
   "hole" in the aggregate EID-Prefix.
   Next, the Map-Server checks to see if any ETRs have registered the
   matching EID-Prefix.  If none are found, then the Map-Server returns
   a Negative Map-Reply with action code "Natively-Forward" and a
   1-minute TTL.

   8.4 …

   If the Map-Resolver does not have the mapping entry and if it can
   determine that the EID is not in the mapping database (for example,
   if LISP+ALT is used, the Map-Resolver will have an ALT forwarding
   table that covers the full EID space), it immediately returns a
   negative LISP Map-Reply, with action code "Natively-Forward" and a
   15-minute TTL.  To minimize the number of negative cache entries
   needed by an ITR, the Map-Resolver SHOULD return the least-specific
   prefix that both matches the original query and does not match any
   EID-Prefix known to exist in the LISP-capable infrastructure.


Regards,

-v

v2.23.0 | Report a Bug | By Email