[lisp] Magnus Westerlund's Discuss on draft-ietf-lisp-gpe-17: (with DISCUSS and COMMENT)

Magnus Westerlund via Datatracker <noreply@ietf.org> Thu, 09 July 2020 09:15 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lisp-gpe@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org, Luigi Iannone <ggx@gigix.net>, ggx@gigix.net
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <159428610512.6828.2632219650433490342@ietfa.amsl.com>
Date: Thu, 09 Jul 2020 02:15:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/fsLa9M_IWMYDUo4yuPOB-ewYpPQ>
Subject: [lisp] Magnus Westerlund's Discuss on draft-ietf-lisp-gpe-17: (with DISCUSS and COMMENT)

Magnus Westerlund has entered the following ballot position for
draft-ietf-lisp-gpe-17: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 4.2:

To me it looks like this is normative reference to the :

Such new encapsulated payloads, when registered with LISP-
   GPE, MUST be accompanied by a set of guidelines derived from
   [I-D.ietf-tsvwg-ecn-encap-guidelines] and [RFC6040].


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 4.3.1:

Thanks for writing relevant guidance on how to mitigate the risks with zero
checksum. Especially the one on traffic separation from other traffic so that
it can be caught on the boundaries of the network to prevent the risk to other
networks from corrupted traffic.

[lisp] Magnus Westerlund's Discuss on draft-ietf-… Magnus Westerlund via Datatracker