IETF Logo Mail Archive

Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)

Dino Farinacci <farinacci@gmail.com> Fri, 14 September 2018 16:50 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 54BDF12F1A5; Fri, 14 Sep 2018 09:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level:
X-Spam-Status: No, score=-0.598 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, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] autolearn=no 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 OnP5BR2CS7ip; Fri, 14 Sep 2018 09:50:45 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 48FB61292AD; Fri, 14 Sep 2018 09:50:45 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id 2-v6so4671208pgo.4; Fri, 14 Sep 2018 09:50:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=m/9b/CWEYrGSDNSV43NarrwGcV7XJLCs32WLetOp8tc=; b=UsM6cZLcD8ypVc297nESnMRdO0CFXMJyC5ixGXM5dp7UyeG2wdMIAgE0Lv/uVhud+s ghJBhs7UbXRUjwAad1Yys0G7u+AIjG7JJkzZRBUq83+i6M33VuJ5UNWA1t2fTiSVrBVg gAGFOTl2Dzy6KdY56tcyezCJcy51KnVsKB9SAVRW+NrnNWARWbkt4jL8FUd/uKajE2Yr I5UjacPeq6CGs0puEk9g8BD8EDD7Gj33n9/RzFwvoa6P3ucs4jN49cpjXYNHrmBBNXx6 qmVGyTJkzg8QYR2eCH1938Ry305cVZHFfbmIXLIkhpGuFT/3mk64PzD8PoHEu+s04XhV +RSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=m/9b/CWEYrGSDNSV43NarrwGcV7XJLCs32WLetOp8tc=; b=nIb3RO+cwr5EUJG47zXQug/BFGmsGazel+QENsubTaqil69ua2IptbNGux0j4Sd0sI nmQttmwKFA01rqBfN84WiWgiiNK+oC+ZrK6ltrzV58U3rrpAsdhJG5UtL3SNz04J+r63 5hHfSk+A34+HpNv6FRxKQylI7qNFbDdF5Q2U1drPerCc9dnsuclnk145FhjlTV/PqogK wK/nsXuDGAWwk18+ovL0NoacyjKmZHUx9EutVxMqXOMp9X5sshiGdAcmBgE4nduVtxri MpgkyoOjXJ8/7dLR1AWbn6a0Xomj26pQpqvaIlW8A7V1w/rk5BZMp91nEI67BXzcsAyw D0PA==
X-Gm-Message-State: APzg51DfVmYSwrn49O8qToQOFwRBT51HZcVu9ggMdSxCk4eiz9OYJKD0 hubT5kSHsHzZhg01cOwwFpM=
X-Google-Smtp-Source: ANB0VdaEVFbTq5bl+B78hFJPUouYoqulXheUd87w4Rlz5ZCVAWPdL++11ALZnM8rRRY3jw62O8Abrg==
X-Received: by 2002:a62:1605:: with SMTP id 5-v6mr13468340pfw.11.1536943844762; Fri, 14 Sep 2018 09:50:44 -0700 (PDT)
Received: from [10.31.79.252] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id x82-v6sm14836046pfe.129.2018.09.14.09.50.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Sep 2018 09:50:43 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <50DF2E0F-6BBC-47A5-996C-74445DF381FF@gmail.com>
Content-Type: multipart/mixed; boundary="Apple-Mail=_C7BCB5A8-EDC8-4A6E-BBFD-3081E939D131"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 14 Sep 2018 09:50:42 -0700
In-Reply-To: <20180914144714.GH48265@kduck.kaduk.org>
Cc: Luigi Iannone <ggx@gigix.net>, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>, draft-ietf-lisp-rfc6833bis@ietf.org, The IESG <iesg@ietf.org>
To: Benjamin Kaduk <kaduk@mit.edu>
References: <153667812809.16741.10796738054406466412.idtracker@ietfa.amsl.com> <9D08CA59-8AC4-4866-944E-98553C37E547@gmail.com> <9086A458-31C0-4EB2-BC5B-D9CB7B22469E@kuehlewind.net> <20180914144714.GH48265@kduck.kaduk.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/TccFipKLBENG4KdJxCySswvTZ7Y>
Subject: Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 14 Sep 2018 16:50:49 -0000

Changed. See diff enclosed. Uses prefix 2001:db8::/16 for the example.

Dino



> On Sep 14, 2018, at 7:47 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> On Wed, Sep 12, 2018 at 12:44:36PM +0200, Mirja Kuehlewind (IETF) wrote:
>> 
>>> Am 11.09.2018 um 20:13 schrieb Dino Farinacci <farinacci@gmail.com>:
>>> 
>>>> 
>>>> Further comments:
>>>> 
>>>> 1) The example given in 5.5 should probably used IPv6 addresses and use the IP
>>>> address space that is reserved for documentation purposes.
>>> 
>>> I disagree. I think its simpler with IPv4 addresses and shouldn’t matter. We want this complex concept to come across as clear as possible. And I believe IPv6 doesn’t do that. This is not a v4 versus v6 response. It is a notation preference.
>> 
>> I will let the INT AD to give further guidance, however, general guidance in the iETF is that IPV6 should also be provided in examples to avoid a bias towards IPv4. I disagree that an IPv6 example would be an more complicated than an IPv4 example.
> 
> There is an IAB statement that is relevant here
> (https://www.iab.org/2016/11/07/iab-statement-on-ipv6/):
> 
> [...]
> We recommend that all networking standards assume the use of IPv6, and be
> written so they do not require IPv4. We recommend that existing standards
> be reviewed to ensure they will work with IPv6, and use IPv6 examples.
> [...]
> 
> -Benjamin

v2.23.0 | Report a Bug | By Email