[tsvwg] Benoit Claise's No Record on draft-ietf-tsvwg-rfc5405bis-18: (with COMMENT)
"Benoit Claise" <bclaise@cisco.com> Wed, 12 October 2016 08:32 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CB9821296F1; Wed, 12 Oct 2016 01:32:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benoit Claise <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147626116879.24211.3734705789648312991.idtracker@ietfa.amsl.com>
Date: Wed, 12 Oct 2016 01:32:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/kmlJY2F59uWAh1I7rNwjt-2xsXU>
Cc: draft-ietf-tsvwg-rfc5405bis@ietf.org, david.black@emc.com, tsvwg-chairs@ietf.org, tsvwg@ietf.org
Subject: [tsvwg] Benoit Claise's No Record on draft-ietf-tsvwg-rfc5405bis-18: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Oct 2016 08:32:49 -0000
Benoit Claise has entered the following ballot position for draft-ietf-tsvwg-rfc5405bis-18: No Record 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-tsvwg-rfc5405bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Before starting to read this document, a first reaction: let me stress that this type of document should really benefit from a "changes since RFC5405" section. I see in the abstract: This document obsoletes RFC5405 and adds guidelines for multicast UDP usage. I see in the intro section: [RFC5405] was scoped to provide guidelines for unicast applications only, whereas this document also provides guidelines for UDP flows that use IP anycast, multicast, broadcast, and applications that use UDP tunnels to support IP flows. Looking at the diffs, there is certainly more than this https://www.ietf.org/rfcdiff/rfcdiff.pyht => https://tools.ietf.org/rfc/rfc5405.txt => https://tools.ietf.org/id/draft-ietf-tsvwg-rfc5405bis-18.txt Background: https://datatracker.ietf.org/doc/draft-wilde-updating-rfcs/ and the related discussion on having a "changes since RFCxxxx", even for obsolete.
- [tsvwg] Benoit Claise's No Record on draft-ietf-t… Benoit Claise
- [tsvwg] Benoit Claise's No Record on draft-ietf-t… Benoit Claise