[tram] Mirja Kühlewind's Discuss on draft-ietf-tram-stun-pmtud-10: (with DISCUSS and COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Fri, 21 September 2018 08:48 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6AF8126CC7; Fri, 21 Sep 2018 01:48:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-tram-stun-pmtud@ietf.org, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Tolga Asveren <tasveren@rbbn.com>, tram-chairs@ietf.org, tasveren@rbbn.com, tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.84.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153751972590.7455.6938488192174769057.idtracker@ietfa.amsl.com>
Date: Fri, 21 Sep 2018 01:48:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/L927uXQTRSBK7lHL_rDgi-3LFII>
Subject: [tram] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?tram-stun-pmtud-10=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2018 08:48:46 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-tram-stun-pmtud-10: 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-tram-stun-pmtud/



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

Based on the transport review provided by Gorry (Thanks!), please clarify the
applicability (as you claim the "usage is not limited to STUN-based protocols")
and the relation to draft-ietf-tsvwg-datagram-plpmtud.

Further, more discussion on impact of reordering, loss, and congestion control
is probably needed (also see Gorry's review).

Regarding sec 4.2.5, as mentioned by Gorry, it is probably not possible to use
the UPD checksum because it might change on the path.

And finally, I have two questions on sec 4.2.6.:

1) I don't quite understand how the identifier "shim" is used. I guess this
would be needed on all UDP packet and it should be negotiated/indicated between
the client and the server. How is that done?

2) Also why does the sequence number needs to be "monotonically incremented by
one for each packet sent". I think all you need is a unique number. So you
actually don't need a sequence number but that an easy implementation to get a
unique number. I would like to see this clarifed because adding a sequence
number might not always be the best choice.


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

Sec 4.2.2 says: "If the Probe Indication identifier cannot be found in the Report
   Response, this is interpreted as a Probe Failure, as defined in
   [RFC4821] Section 7.5.  If the Probe Indication identifier cannot be
   found in the Report Response but identifiers for other packets sent
   before or after the Probe Indication can all be found, this is
   interpreted as a Probe Failure as defined in [RFC4821] Section 7.5"
However, RFC4821 seems to only see the second case as an failure.