Re: [lisp] IPv6 examples in lisp documents

Dino Farinacci <farinacci@gmail.com> Wed, 06 April 2016 15:34 UTC

Return-Path: <farinacci@gmail.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 A0F4A12D1E7 for <lisp@ietfa.amsl.com>; Wed, 6 Apr 2016 08:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AqGuXv_rMj5a for <lisp@ietfa.amsl.com>; Wed, 6 Apr 2016 08:34:51 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::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 38CFB12D17D for <lisp@ietf.org>; Wed, 6 Apr 2016 08:34:51 -0700 (PDT)
Received: by mail-qg0-x232.google.com with SMTP id c6so39034871qga.1 for <lisp@ietf.org>; Wed, 06 Apr 2016 08:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZjLWkbGgwjZOx97TWo1eRNGZ1j0e2JmGmrQrRJDE1Uk=; b=FCWdOu3jq3FSlKRIRPThsly8BLtShirZUcETE9eq4mxgvEOCbkiUea7qI4M2OY5bbP TseYeKPrvx7iPZLkPOWbBubY/GGLMVnbs9vC03NtRYCtYfFQnQ9SdnBa/IeCzRfaot1C uYXnCo6JwJAkUI+9Jj/LkZGOuLHvRHNkyktdrRxshmekfUQbxmY71Vk68W6ZOsgi8QYX VTCLovxsMonBfL5uYozlLAu/Y+E5cjjKt2Pk/S7sMxIMKlIeBvibGP7Y3u1Tqh6HQ/cH Zd7+72rU3CkCl1MJBGRUkCrEGWPXdwsjzSkppw18ytYPEi0LEKsVAEvrmgZV2FkSkvTD SxJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZjLWkbGgwjZOx97TWo1eRNGZ1j0e2JmGmrQrRJDE1Uk=; b=VKjd71wijGSa7Hn2myHwY1J2sTYRigB6/Tt+D736e8z+Id/O2+0FmohfWiGQo6WlVo UzrDuudUoxXJPaaevGcUO0Fwn/QUblUK574SSJEERdG1EwuYC3Rc+edR5EEpNe1b96/3 9mBQXHV+Jk5tgyB02VgkNcax5x0ZutwKINgOrOjYZy99UFksjJOaE7OmeXtzux+sE7PM QbcJc+j4pVsZc69ARyVSqjWWu+exT8wZ0qSWW4AIceeBV9rX/WBgNWojxRFQlaI54a+P zrJj0KTRqlD+iCa9+Va0DtLbzjbfkZ5H12kiNnxuVEyt9e64tLjXDobT6XFnQ0FVLFas lHKw==
X-Gm-Message-State: AD7BkJJu0ELEWk7eTH86Q4e5tb1Rx7SBTTgxV/efR0NCq5x6ez0iN7x50RWQQUyHZ5fmYw==
X-Received: by 10.140.167.137 with SMTP id n131mr25724447qhn.73.1459956890280; Wed, 06 Apr 2016 08:34:50 -0700 (PDT)
Received: from dhcp-b1ec.meeting.ietf.org (dhcp-b1ec.meeting.ietf.org. [31.133.177.236]) by smtp.gmail.com with ESMTPSA id z64sm1470947qhz.32.2016.04.06.08.34.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2016 08:34:49 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <570528D8.70401@joelhalpern.com>
Date: Wed, 6 Apr 2016 08:34:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A352EAEB-4009-47F7-8247-846BD55BA27B@gmail.com>
References: <201604061501.u36F1ECF004051@irp-lnx1.cisco.com> <570528D8.70401@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/WHhuUrNOMvOGMtPdeKVfIsKOPy8>
Cc: Fred Baker <fred@cisco.com>, "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] IPv6 examples in lisp documents
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 06 Apr 2016 15:34:53 -0000

> First, the LISP protocol has been specified from the beginning to support and to run over IPv6.  Full IPv4 and IPv6 support has been in there.

And to carry IPv6 on the overlay as well.

> With regard to the examples in the lisp-threats draft, I would be very reluctant to try to make any such changes.  The draft is already in THE RFC Editor queue, and as such we would need a serious problem before we would even attempt to reopen the draft.
> 
> With regaard to lisp-ddt it is probably quite reasonable to add IPv6 examples to the draft before we complete work on that document.

Also, the LCAF draft that describes general encoding rules for many types of addresses and objects includes IPv6 addresses. Just an FYI.

Dino

> 
> Yours,
> Joel
> 
> On 4/6/16 11:01 AM, fred@cisco.com wrote:
>> Hello:
>> 
>> I'd like to bring something to your attention with regard to
>> draft-ietf-lisp-threats, if I may.  It uses IPv4 examples (examples
>> using addresses in 192.0.2.0/24, 198.51.100.0/24, or 203.0.113.0/24), but
>> presents no IPv6 examples (which would use 2001:db8::/32, as specified
>> in RFC 6890).  This suggests that at some future time the protocol will
>> likely need to be updated to use IPv6 in addition to IPv4.
>> 
>> draft-robachevsky-mandating-use-of-ipv6-examples makes a very practical
>> suggestion, which is that drafts should consider IPv6, as it is the
>> direction the Internet is headed, and therefore provide either only IPv6
>> examples or both IPv4 and IPv6 examples. This has not been agreed to in
>> the IETF, nor is it a mandate in any sense. However, it seems practical.
>> 
>> I can imagine that you just didn't think about IPv6,
>> on the assumption that it is not a current reality in the
>> Internet; while not true, that is a common perception.  However, as
>> https://www.vyncke.org/ipv6status/compare.php?metric=p&countries=be,ch,us,pt,de,gr,lu,pe,ec,ee,jp,fr,cz,my,fi,no,br,ca,ro,nl
>> displays, Google, APNIC, and Akamai are reporting that at least 39
>> countries worldwide have non-negligible IPv6 deployment (at least 1%
>> of the traffic each of them sees uses IPv6 in those markets), 20 of
>> them have at least 5%, and, in one case and one measurement, over 50%
>> of their traffic. Additionally, AT&T, Comcast, Google, and T-Mobile
>> indicate that a significant pecentage (around half to three quarters) of
>> their mobile handsets or home computers are using IPv6 - in some cases,
>> accessing IPv4 sites only through NAT64 translation.
>> 
>> In that spirit, would you please consider duplicating your IPv4 examples,
>> or augmenting them, to display both the IPv4 and IPv6 variants?
>> 
>> Thanks.
>> 
>> Fred
>> 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp