Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-encap-guidelines-13.txt
Bob Briscoe <in@bobbriscoe.net> Tue, 10 March 2020 17:57 UTC
Return-Path: <in@bobbriscoe.net>
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 CE4013A077F; Tue, 10 Mar 2020 10:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=bobbriscoe.net
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 JLIOgAuPqSBE; Tue, 10 Mar 2020 10:57:06 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (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 C0E603A077E; Tue, 10 Mar 2020 10:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject: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=heJhVo9Nvkpkonmf2IIv09Vi8zUgcVx5tQhpl+4HAgE=; b=1PpSRbPFTj2Lcyb5qRFFc3z1/ 9phWrxZM0vhe4uABxAM98U9MaFwd0AiC78xSCPL9etGvmOSmoOxZqmz2kwtc1QTxEGJwGO/mATg6h Sw0fTeRwKvdezYq3i1LIrmTQD+a+Yj+Wgs8FdLSRJxxsYfAZBpWFFrzpDfBC5jhHWpCn42JVRNkzs mDzBkrTP1pblUrRL4WXx1L6UTXLi/TE/ZIEkeRKbyjhR0+HT0j7dza+l2ib1bGXg0E8gEka0/P0Qf RajNtNNQunaDXpEwypjwkh2+DZ1s3HVGHBA7+VLgUCxfNeViowsbSYuOPsgvDTEUUxcBYC75j4CI6 FyJU1m2Vg==;
Received: from [31.185.128.125] (port=47274 helo=[192.168.0.6]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <in@bobbriscoe.net>) id 1jBj7j-00060S-P2; Tue, 10 Mar 2020 17:57:00 +0000
To: "Andrew G. Malis" <agmalis@gmail.com>, draft-ietf-tsvwg-ecn-encap-guidelines@ietf.org
Cc: tsvwg IETF list <tsvwg@ietf.org>
References: <155839199921.12894.1422942310166180969@ietfa.amsl.com> <CAA=duU2xkabb=wzy70jQo6Ls5yokA6F_U=LYRtWpZE8xJYAkng@mail.gmail.com>
From: Bob Briscoe <in@bobbriscoe.net>
Message-ID: <f62450a9-48d5-18d5-f795-47a4a4b18ebf@bobbriscoe.net>
Date: Tue, 10 Mar 2020 17:56:59 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAA=duU2xkabb=wzy70jQo6Ls5yokA6F_U=LYRtWpZE8xJYAkng@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------217E98F0B583F0DE1A96F93D"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/hWXgkLDYt9pMlf1IPc5E4hpRpYc>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-encap-guidelines-13.txt
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: Tue, 10 Mar 2020 17:57:15 -0000
Andy, Just found this email. Apologies... On 21/05/2019 15:51, Andrew G. Malis wrote: > Bob, John, Pat, > > In your draft, I noticed that you reference RFC 5129 but not 5462. A > reference to 5462 would be useful, as it updates 5129. My understanding is that we should cite the relevant RFC, then any updates to that RFC automatically apply. I am aware of RFC5462, and I know you're only trying to be helpful, but I figured the /relevant/ RFC in this case was RFC5129, which defines ECN marking in MPLS. Given RFC5462 is not the technical definition of ECN marking in MPLS, but solely gives the EXP field a new name, I don't think it's necessary to cite it. Particularly as there is no mention of the field name (old or new) in the ecn-encap draft. Despite the length of ecn-encap, I do try to be parsimonious. But thanks anyway for taking the care to highlight this. Bob > > Cheers, > Andy > > > On Mon, May 20, 2019 at 6:40 PM <internet-drafts@ietf.org > <mailto:internet-drafts@ietf.org>> wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Transport Area Working Group WG > of the IETF. > > Title : Guidelines for Adding Congestion > Notification to Protocols that Encapsulate IP > Authors : Bob Briscoe > John Kaippallimalil > Pat Thaler > Filename : draft-ietf-tsvwg-ecn-encap-guidelines-13.txt > Pages : 38 > Date : 2019-05-20 > > Abstract: > The purpose of this document is to guide the design of congestion > notification in any lower layer or tunnelling protocol that > encapsulates IP. The aim is for explicit congestion signals to > propagate consistently from lower layer protocols into IP. Then the > IP internetwork layer can act as a portability layer to carry > congestion notification from non-IP-aware congested nodes up to the > transport layer (L4). Following these guidelines should assure > interworking among IP layer and lower layer congestion notification > mechanisms, whether specified by the IETF or other standards > bodies. > This document updates the advice to subnetwork designers about > ECN in > RFC 3819. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-tsvwg-ecn-encap-guidelines-13 > https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-encap-guidelines-13 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-ecn-encap-guidelines-13 > > > 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>. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org> > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > -- ________________________________________________________________ Bob Briscoe http://bobbriscoe.net/
- [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-encap-gu… internet-drafts
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-enca… Andrew G. Malis
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-enca… Bob Briscoe
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-enca… Andrew G. Malis