[lisp] Fwd: New Version Notification for draft-iannone-lisp-mapping-versioning-01
Luigi Iannone <luigi@net.t-labs.tu-berlin.de> Thu, 11 March 2010 07:35 UTC
Return-Path: <luigi@net.t-labs.tu-berlin.de>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23F9D3A6A48 for <lisp@core3.amsl.com>; Wed, 10 Mar 2010 23:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IasPbvQTlY8x for <lisp@core3.amsl.com>; Wed, 10 Mar 2010 23:35:08 -0800 (PST)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id 081873A6B10 for <lisp@ietf.org>; Wed, 10 Mar 2010 23:34:59 -0800 (PST)
Received: from dyn113.net.t-labs.tu-berlin.de (dyn113.net.t-labs.tu-berlin.de [130.149.220.113]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 842597000585; Thu, 11 Mar 2010 08:35:03 +0100 (CET)
From: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary="Apple-Mail-72-75410467"
Date: Thu, 11 Mar 2010 08:35:02 +0100
References: <20100308184820.B12773A6B1A@core3.amsl.com>
To: lisp@ietf.org
Message-Id: <89734075-C00B-4E5A-9E08-F388A0D88371@net.t-labs.tu-berlin.de>
X-Mailer: Apple Mail (2.1077)
Cc: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Subject: [lisp] Fwd: New Version Notification for draft-iannone-lisp-mapping-versioning-01
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 11 Mar 2010 07:35:09 -0000
Hi All, We recently updated the draft concerning lisp mapping versioning. Most important changes are the following: - Version numbers are now 16 bits - Detailed description of packet encodings. No new packets are necessary anymore, mapping versioning uses part of the reserved bits in both the LISP specific header and mapping records. - The proposed mechanism is totally transparent for nodes that do not support versioning, thus incremental deployment is feasible and discussion on the topic has been added to the draft. - We describe in more details the benefits introduced by mapping versioning including: - Versioning and interworking - Versioning and mapping synchronization - Versioning and unidirectional traffic - Versioning vs. checksum - Versioning and mobility - Security aspects All comments are welcome Luigi Begin forwarded message: > From: IETF I-D Submission Tool <idsubmission@ietf.org> > Date: March 8, 2010 7:48:20 PM GMT+01:00 > To: luigi@net.t-labs.tu-berlin.de > Cc: damien.saucez@uclouvain.be,olivier.bonaventure@uclouvain.be > Subject: New Version Notification for draft-iannone-lisp-mapping-versioning-01 > > > A new version of I-D, draft-iannone-lisp-mapping-versioning-01.txt has been successfuly submitted by Luigi Iannone and posted to the IETF repository. > > Filename: draft-iannone-lisp-mapping-versioning > Revision: 01 > Title: LISP Mapping Versioning > Creation_date: 2010-03-08 > WG ID: Independent Submission > Number_of_pages: 25 > > Abstract: > The present document sketches an optional approach to provide in- > packet information about EID-to-RLOC mappings used to encapsulate > LISP data packets. The proposed approach is based on associating a > version number to EID-to-RLOC mappings and transport such a version > number in the LISP specific header of LISP-encapsulated packets. > This versioning approach is particularly useful to inform > communicating xTRs about modification of the mappings used to > encapsulate packets. Modification of mappings could mean adding/ > removing an RLOC, or just a modification in the reachability, > priority, or weight of one or more RLOCs. Each time a mapping is > modified, a new version number is generated and propagated in the > LISP data packet. The use of version numbers allows to avoid > repeated Map-Request upon mappings change, limits the interaction > between Control and Data planes, improves security, offer support for > caching on Map-Servers, and could be used also in mobile scenarios. > > The proposed mechanism is optional and does not need any modification > on the base LISP encapsulation. Rather, it uses one of the reserved > bits of the LISP specific header and overloads the Locator Status > Bits. Similarly, no modification are necessary in the base LISP Map- > Reply records. LISP versioning uses part of the reserved bits. In > both cases, LISP encapsulation and Map-Reply records, bits used for > LISP versioning can be safely ignored by xTRs that do not support the > mechanism. Further, mappings can be distributed as usual through > both existing and future mapping distribution system (e.g., ALT). > The infrastructure build by each specific mapping distribution system > does not change anyhow. Even more, existing mapping distribution > protocol are able to rely LISP control plane packets containing > version numbers and do not need modifications. All of these features > make LISP versioning a completely transparent optional mechanism with > respect to the LISP base specification. > > > > The IETF Secretariat. > >
- [lisp] Fwd: New Version Notification for draft-ia… Luigi Iannone