Re: [tsvwg] A New Draft Uploaded (draft-qiang-tsvwg-udp-options-bounded-latency-00)

Joe Touch <touch@strayalpha.com> Fri, 08 March 2019 03:43 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D9E1312A9 for <tsvwg@ietfa.amsl.com>; Thu, 7 Mar 2019 19:43:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 ngORDqCmIVDf for <tsvwg@ietfa.amsl.com>; Thu, 7 Mar 2019 19:43:55 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1F35131298 for <tsvwg@ietf.org>; Thu, 7 Mar 2019 19:43:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=nigLBl5LFtu2ejo/3eOKnYWw3ONrD8MupPV6W3FUXPY=; b=SDbtBQdr+35+Nb84BY5bemtCU ZkK1gpM3gjMtNskVQNUkw6JYFSAMPjvqAOsuQ0ig8qQz7fsWRQZHIIvhXztCPvjEzCds5VdqkhWLn e7riS/3HWwzHPvSFtgG0OOGTdSvTZ6DcXikleCHh1Ha1AS3MrCzxLH7NlekhNWu5N6eHJIE2rZ7Sg IPs5TevIrOm/+4tpksn8uH8X0MN0Al/q9w3SGwGZoICHCAgiAYPlnWhVmWQ2dWhagwEXW7ZTVzr5E w/ea16aw+/FAw8xPVODxn0GV9ZSXFsSHDGjZ229B1qjQ1ZZiP34gHZb3PxTk4LF1z2xIwkmfV8KBs N/k6PbadQ==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:56522 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1h26QH-001ev7-AB; Thu, 07 Mar 2019 22:43:51 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_808C3E37-66A5-47F8-8C87-96B172259BBD"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <06C389826B926F48A557D5DB5A54C4ED45BE93CB@dggemi529-mbs.china.huawei.com>
Date: Thu, 07 Mar 2019 19:43:48 -0800
Cc: tsvwg <tsvwg@ietf.org>, Toerless Eckert <tte@cs.fau.de>
Message-Id: <0EA3C86F-B061-451D-A521-292728788B16@strayalpha.com>
References: <06C389826B926F48A557D5DB5A54C4ED45BE93CB@dggemi529-mbs.china.huawei.com>
To: "qiangli (D)" <qiangli3@huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/V_RkvLvbl-exhJhHJSr6dC6KOPg>
Subject: Re: [tsvwg] A New Draft Uploaded (draft-qiang-tsvwg-udp-options-bounded-latency-00)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 08 Mar 2019 03:43:57 -0000

Two points (the first is useful for everyone developing upcoming UDP options):

1. proposals for new UDP options should indicate a KIND value of “TBD” only; they should not ‘squat’ or preselect a value until assigned by IANA (when the UDP options doc is published) or - until the UDP doc is published - at least the doc is accepted as a WG doc.

2. a request for such assignment should be included in the IANA considerations portion of that document

These are common conventions for assigned numbers in general.

As a result, I encourage the authors to quickly issue an update to this doc that follows the above convention.

Additionally, if accepted, can you explain why it wouldn’t be sufficient to just request the next open value?

Joe

> On Mar 7, 2019, at 5:22 PM, qiangli (D) <qiangli3@huawei.com> wrote:
> 
> Hi All,
>  
> We have uploaded a new draft (draft-qiang-tsvwg-udp-options-bounded-latency-00) that explores the use of UDP options for bounded latency forwarding. Review and comment is highly appreciated.
>  
>  
> Best regards,
>  
> Cristina QIANG
>  
>  
> ==============================================
> A new version of I-D, draft-qiang-tsvwg-udp-options-bounded-latency-00.txt
> has been successfully submitted by Li Qiang and posted to the IETF repository.
>  
> Name:               draft-qiang-tsvwg-udp-options-bounded-latency
> Revision:  00
> Title:                  UDP Options for Bounded Latency
> Document date:       2019-03-08
> Group:               Individual Submission
> Pages:               9
> URL:            https://www.ietf.org/internet-drafts/draft-qiang-tsvwg-udp-options-bounded-latency-00.txt <https://www.ietf.org/internet-drafts/draft-qiang-tsvwg-udp-options-bounded-latency-00.txt>
> Status:         https://datatracker.ietf.org/doc/draft-qiang-tsvwg-udp-options-bounded-latency/ <https://datatracker.ietf.org/doc/draft-qiang-tsvwg-udp-options-bounded-latency/>
> Htmlized:       https://tools.ietf.org/html/draft-qiang-tsvwg-udp-options-bounded-latency-00 <https://tools.ietf.org/html/draft-qiang-tsvwg-udp-options-bounded-latency-00>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-qiang-tsvwg-udp-options-bounded-latency <https://datatracker.ietf.org/doc/html/draft-qiang-tsvwg-udp-options-bounded-latency>
>  
>  
> Abstract:
>    This document explores the use of UDP options for packet forwarding
>    with bounded latency.
>  
>                                                                                  
>  
>  
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
>  
> The IETF Secretariat