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

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 12 October 2014 00:30 UTC

Return-Path: <jmh@joelhalpern.com>
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 ADC0D1A00FE for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 17:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.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] 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 HZp_zrP4huXb for <lisp@ietfa.amsl.com>; Sat, 11 Oct 2014 17:30:49 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19AED1A00CD for <lisp@ietf.org>; Sat, 11 Oct 2014 17:30:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 0471B240958; Sat, 11 Oct 2014 17:30:49 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.1.90] (107-194-85-212.lightspeed.nsvltn.sbcglobal.net [107.194.85.212]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 87DA0240329; Sat, 11 Oct 2014 17:30:48 -0700 (PDT)
Message-ID: <5439CBB7.50107@joelhalpern.com>
Date: Sat, 11 Oct 2014 20:30:47 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, "lisp@ietf.org" <lisp@ietf.org>
References: <fddce201eb144632a895d6c2f27bd637@CO1PR05MB442.namprd05.prod.outlook.com> <5439BE86.20302@joelhalpern.com> <c394e340963044988658ec26ea11a931@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <c394e340963044988658ec26ea11a931@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/V_ORxFvXR173TFBkyyYSsKREdXY
Subject: Re: [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: Sun, 12 Oct 2014 00:30:51 -0000

At the time of RFC 6830 that statement was true.  Note that we did not 
write "An RLOC MUST be an IPv4 or IPv6 address."  The statement was 
descriptive, not prescriptive.

Yours,
Joel

On 10/11/14, 8:05 PM, Ronald Bonica wrote:
> And strictly speaking, how do you reconcile your statement, below, with the following statement from RFC 6830:
>
> "An RLOC is an IPv4 [RFC0791] or IPv6  [RFC2460] address of an Egress Tunnel Router (ETR)."
>
>                                                   Ron
>
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>> Sent: Saturday, October 11, 2014 7:35 PM
>> To: Ronald Bonica; lisp@ietf.org
>> Subject: Re: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax
>>
>> The working group has other documents that define other formats for EIDs
>> and RLOCs.  These are defined with AFIs.  In fact, AFIs are used in 6830 so as
>> to allow compatible extension of the work.  At the time 6830 was published,
>> those were the two defined forms.
>>
>> Suggesting taht an extensible RFC prevents us from extending the work
>> would be odd.  Since we do have work under way (the LCAF draft) which
>> defines many other forms, it is quite appropriate to for the introduction to
>> indicate that a broader range is possible.
>>
>> Yours,
>> Joel
>>
>> On 10/11/14, 7:17 PM, Ronald Bonica wrote:
>>> 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
>>>
>>> _______________________________________________ lisp mailing
>> list
>>> lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
>>>
>