Re: [lisp] [Tsv-art] Tsvart last call review of draft-ietf-lisp-rfc6830bis-15

Dino Farinacci <farinacci@gmail.com> Thu, 30 August 2018 14:55 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 C99A3130E74; Thu, 30 Aug 2018 07:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JEaVforX8zA0; Thu, 30 Aug 2018 07:55:18 -0700 (PDT)
Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (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 6C38D130E4B; Thu, 30 Aug 2018 07:55:18 -0700 (PDT)
Received: by mail-pg1-x543.google.com with SMTP id b129-v6so3992034pga.13; Thu, 30 Aug 2018 07:55:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AS0zkAJIHzfUzOiTa9eIQDiF6nDNpN+J3OJYn5kWiVU=; b=fogMRDxNbHsAMPuk6l8LtmkBN3mbOcU5hpt5k6UC2imC4tOsd6fKb+jD3j9jV7Jyhh oIM/6JuHXjFWa758L34ndlKu/+QXq20lAA08Z8bpNNmED4/NVSUK5mO7ZbsNOmqU26rY vjFYjG/I9BFfkC1VztsMyz/X5zBkiyz5ViaQWNK+RUexrb563yqOYUjfqeQcigEjOO9i 4gjS2+ldlaGgp0Oll3vb+aHje4AJB7EpLiUwc7FxpeVQt2ZoUTvbM/vqa3UglIHxmV4r HBSr4gxPHp46Wbqby9E69blTICOYPYmP2I51YFpddVItn3+tDUR+v1i4/XQ+ohBLg8SC q51A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AS0zkAJIHzfUzOiTa9eIQDiF6nDNpN+J3OJYn5kWiVU=; b=NtjrHpgu1sk/wpWxWjK8RSxofyyNA8A1mOG7fw1EPQ0FHWzAiHTN0134+RQZ26DbMW XKR8fdDEBeQNgbBSANnL5LtRGoWjdcuOsBnlxUghcZ6hP9imSy61AWiWx97RxaBkuHE9 BANjfXTK5e45+IWahMKvHSsFK1os1xFQuQKmD2d48W7cy1sb7Il2bZHotFJOl/pSjdPJ xlJr8dde0Pfx5HcoBC3mOQ3qDU7U/WY/Ivh0Eq8IwdvJnGaZ2obimRXqnb/0Q/6q9oNF SgXgf2HW/4sdvaEziAd/Mt7UTML6RtHVZjNYWDR9gdpJOxAfLOgFgN3Hua/2+ux6DMcI wCEQ==
X-Gm-Message-State: APzg51Cy46IMu/V6zbIN7uND4MFzKVgEb2FY9zvO6RQOXcGL51/qN2nF XIY+sizTvH34quc8BbnMuVPw262r
X-Google-Smtp-Source: ANB0VdYw7Ran336tNkCyPnpgHU2alLFnfSk7KQZaBZbv6/fQpSdcQibmuz3qNWIsfFEq2WkuQlvbEQ==
X-Received: by 2002:a63:1823:: with SMTP id y35-v6mr10164283pgl.438.1535640917939; Thu, 30 Aug 2018 07:55:17 -0700 (PDT)
Received: from [10.31.79.28] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id l185-v6sm12399148pga.5.2018.08.30.07.55.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 07:55:17 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <B466126A-DBE8-4088-AC93-F7D49C534ABE@trammell.ch>
Date: Thu, 30 Aug 2018 07:55:16 -0700
Cc: draft-ietf-lisp-rfc6830bis.all@ietf.org, tsv-art@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E76EB141-5D80-4131-AB42-4DB326348B00@gmail.com>
References: <153538054829.30074.15428909912816972228@ietfa.amsl.com> <ED34F830-1FEF-42BB-BB6E-805D724AB339@gmail.com> <79FA52C8-94AC-43CE-B052-9F921A65E0D5@trammell.ch> <23680BD5-0DD3-4404-888D-D1C78A0A437D@gmail.com> <130902C2-9CEE-4931-8957-D32446723B89@trammell.ch> <CF5E3C7B-E492-4EE9-A2E6-A2D823C6610F@gmail.com> <1514B576-87FD-475F-B6C5-BBA1C2CA94ED@trammell.ch> <CE7ECD23-E8A2-4D48-B752-0D246C02F27E@gmail.com> <FBA13CF2-8E44-46DA-AB5D-9082B5288F05@trammell.ch> <5E2CBC85-87FF-48DC-950B-403E6E8E14BF@gmail.com> <C4425CD6-B44D-479A-819A-BEFCC83E9E33@gmail.com> <B466126A-DBE8-4088-AC93-F7D49C534ABE@trammell.ch>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/wAewJUHOQWeNF2f42JeK1cwJrrI>
Subject: Re: [lisp] [Tsv-art] Tsvart last call review of draft-ietf-lisp-rfc6830bis-15
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.27
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, 30 Aug 2018 14:55:20 -0000

> On Aug 30, 2018, at 2:57 AM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> 
> hi Dino,
> 
> Almost. How about:
> 
> 
> OLD:
> 
> When the UDP and LISP headers require integrity protection, the
> methods of using UDP checksums in [RFC8085] can be considered.
> 
> NEW:
> 
> Implementors are encouraged to consider UDP checksum usage guidelines in section 3.4 of [RFC8085]. Specifically, when the UDP, LISP, and outer IPv6 headers require protection against corruption, the use of non-zero UDP checksums is RECOMMENDED.

Well if we recommend it and when describing the UDP header in the packet format section we don’t that woudl be a contracdiction. And note the IPv6 outer header cannot be protected with a UDP checksum. The link-layer CRC will do that.

NEWNEW:

Implementors are encouraged to consider UDP checksum usage guidelines in section 3.4 of [RFC8085] when
it is desirable to protect UDP and LISP headers against corruption.

What do you think?

Dino