Re: [lisp] Way forward on 6830bis

Damien Saucez <damien.saucez@gmail.com> Thu, 05 November 2015 01:39 UTC

Return-Path: <damien.saucez@gmail.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 3B6141B35F6 for <lisp@ietfa.amsl.com>; Wed, 4 Nov 2015 17:39:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 zxZtvZQ5au53 for <lisp@ietfa.amsl.com>; Wed, 4 Nov 2015 17:39:56 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48D061A8788 for <lisp@ietf.org>; Wed, 4 Nov 2015 17:39:56 -0800 (PST)
Received: by wmll128 with SMTP id l128so833590wml.0 for <lisp@ietf.org>; Wed, 04 Nov 2015 17:39:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bb6mf/b0B/VttzMuTXdc7lk6i2rqvOay3KGbJ+4BhOc=; b=pPc7/oLut3woXvJc5cU5sDHfDEHkvS/UHfGE8i+beQO20Z/ePBoHE/Dy/rcab4cc9b FektRSUxaSes0Mko1XLkFIuF374eFEuoYIMBPniI7yWoQhAgkxcsjabAS0YaRQjgNTx5 BTUCdzwVIMg03032JtNj2xpC8kg8mnLJQM9o9pcbcuJZS6AH80iDViIuxR6wohbU/MVr aDYs30nCkzKc+g+s9LSySu9QCcN4NvBcLGC7Q4+8GJsCcFBUYBzf8VkkdBwdwpF4XVNZ 9Z4WffM0cjSlxyHEIOuJy9ovee2bYdY+3czzgqt5vtQxdQT2GE2zxeqXSVYINLuCXQkr WG4A==
X-Received: by 10.28.217.6 with SMTP id q6mr254152wmg.5.1446687594758; Wed, 04 Nov 2015 17:39:54 -0800 (PST)
Received: from dhcp-52-119.meeting.ietf94.jp (dhcp-52-119.meeting.ietf94.jp. [133.93.52.119]) by smtp.gmail.com with ESMTPSA id h4sm4249606wjx.41.2015.11.04.17.39.51 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Nov 2015 17:39:54 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <EE7AECD8-3EDB-407D-BACB-27EBDE8C88D3@gmail.com>
Date: Thu, 05 Nov 2015 10:39:46 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC20FC57-849D-46D5-BB5D-69CE081016CB@gmail.com>
References: <562E53EF.9070707@joelhalpern.com> <9181AA70-7967-4625-8F2A-981ED8C04724@gmail.com> <EE7AECD8-3EDB-407D-BACB-27EBDE8C88D3@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/fSi9pFzY_ypOhMhMltuKCWHPzxQ>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] Way forward on 6830bis
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: <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: Thu, 05 Nov 2015 01:39:58 -0000

On 05 Nov 2015, at 10:33, Dino Farinacci <farinacci@gmail.com> wrote:

>> Hello,
>> 
>> By seeing Alberts presentation on SFC today I was just thinking that we could
>> split 6830 in two documents.
>> 
>> One document to present the data-plane (mostly Sec 5).
>> 
>> One document to present the control-plane (mostly Sec 6).
>> 
>> As Albert said the mapping system is generic (with LCAF).  Therefore it would
>> make it more logical (to me at least) to have a document to strictly talk about
>> the mapping system and it would increase the appeal of the mapping system by
>> not requiring people to care about the LISP encapsulation if they only need the
>> mapping system function.
> 
> The mapping system is in a separate document and spread across alt, ddt, and ms specs. The control-plane text in RFC6830 is defining an API to the mapping system. And I think you want it all in one place for completeness.
> 

When  I was talking about mapping system, I was talking about the
“API” (Map-Request, Map-Reply, Map-Register… ).

I understand that it is not straightforward to make it in a nice way, but
the as LISP is about decoupling control-plane and data-plane it would
make sense to also decouple control and data-plane definition.

Imagine you want someone to only implement the control-plane, how
does he know what to implement exactly to be fully compliant? 

Damien Saucez 

> Dino
> 
>> 
>> Cheers,
>> 
>> Damien Saucez 
>> 
>> On 27 Oct 2015, at 01:25, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>> 
>>> It seemed to us that there was likely some confusiona bout how we expect to handle the revision of RCC 6830.  The following is what we currently expect.
>>> 
>>> Once we have a new charter approved, the chairs will appoint an editor for the revision of rfc6830.  That may be one of the existing authors, or a new person.  We will ask for volunteers.
>>> 
>>> Once we have an author, they will submit a starting ID called draft-ietf-lisp-rfc6830bis-00 which will be identical in content to the existing RFC.  That may require assistance from the RFC Editor to ensure that we get all the changes they made during final edit.
>>> 
>>> At that point, we will use the trouble ticket system to record issues that people bring up.  We will also discuss on the list what changes we wish to make according to the charter.  Things will tehn proceed in the usual fashion, using the trouble ticket system to help make sure we do not drop any of the issues.
>>> 
>>> Yours,
>>> Joel & Luigi
>>> 
>>> _______________________________________________
>>> 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
>