[lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax

Ronald Bonica <rbonica@juniper.net> Sat, 11 October 2014 23:17 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C63D01A1AEE for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 16:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 aeDYdQc2EK5N for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 16:17:12 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0127.outbound.protection.outlook.com [65.55.169.127]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2905F1A1BC6 for <lisp@ietf.org>; Sat, 11 Oct 2014 16:17:12 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.0.1049.19; Sat, 11 Oct 2014 23:17:09 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.91]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.91]) with mapi id 15.00.1049.012; Sat, 11 Oct 2014 23:17:09 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "lisp@ietf.org" <lisp@ietf.org>
Thread-Topic: draft-ietf-lisp-introduction-05 - EID/RLOC Syntax
Thread-Index: Ac/lqOiufEtPdxYkT76OGFqr28xHEg==
Date: Sat, 11 Oct 2014 23:17:09 +0000
Message-ID: <fddce201eb144632a895d6c2f27bd637@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [66.129.241.10]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-exchange-antispam-report-test: UriScan:;
x-forefront-prvs: 0361212EA8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(108616004)(230783001)(110136001)(101416001)(87936001)(229853001)(77096002)(85852003)(95666004)(86362001)(85306004)(21056001)(92566001)(2351001)(76482002)(107046002)(40100003)(2656002)(2501002)(74316001)(122556002)(99396003)(20776003)(106356001)(107886001)(99286002)(64706001)(50986999)(80022003)(46102003)(97736003)(76576001)(105586002)(31966008)(4396001)(54356999)(120916001)(66066001)(33646002)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/uBFiu2lYm9DDPeCGd2wNFMfFzIY
Subject: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 11 Oct 2014 23:17:14 -0000

Folks,

Section 1 of draft-ietf-lisp-introduction-05 says:

"This document describes the LISP architecture, its main operational mechanisms as its design rationale.  It is important to note that this document does not specify or complement the LISP protocol.  The interested reader should refer to the main LISP specifications [RFC6830] and the complementary documents [RFC6831],[RFC6832], [RFC6833],[RFC6834],[RFC6835], [RFC6836] for the protocol specifications along with the LISP deployment guidelines [RFC7215]."

I interpret this as meaning that draft-ietf-lisp-introduction-05 MUST not contradict RFC 6830.

However, Section 1 of draft-ietf-lisp-introduction-05 also says:

"LISP creates two separate namespaces, EIDs (End-host IDentifiers) and RLOCs (Routing LOCators), both are -typically, but not limited to- syntactically identical to the current IPv4 and IPv6  addresses."

However, RFC 6830 says:

"An RLOC is an IPv4 [RFC0791] or IPv6  [RFC2460] address of an Egress Tunnel Router (ETR)."

It also says:

"An EID is a 32-bit (for IPv4) or 128-bit (for IPv6) value used in the source and destination address fields of the first (most inner) LISP header of a packet."

Given these statements, how can the RLOC or EID by syntactically different from an IPv4 or IPv6 address?

                                                                                              Ron Bonica