Re: [teas-3272bis-design-team] existing references in 3272
Loa Andersson <loa@pi.nu> Sun, 31 March 2019 20:21 UTC
Return-Path: <loa@pi.nu>
X-Original-To: teas-3272bis-design-team@ietfa.amsl.com
Delivered-To: teas-3272bis-design-team@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACB9120160 for <teas-3272bis-design-team@ietfa.amsl.com>; Sun, 31 Mar 2019 13:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 0WWDuYpdQTxA for <teas-3272bis-design-team@ietfa.amsl.com>; Sun, 31 Mar 2019 13:21:15 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E258612000E for <teas-3272bis-design-team@ietf.org>; Sun, 31 Mar 2019 13:21:14 -0700 (PDT)
Received: from [172.20.10.2] (37.250.152.78.bredband.tre.se [37.250.152.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 1077033F5AF; Sun, 31 Mar 2019 22:21:12 +0200 (CEST)
To: adrian@olddog.co.uk, teas-3272bis-design-team@ietf.org
References: <b0eb4797-b1b7-67ae-7dd4-bde9abf63b65@pi.nu> <002a01d4e7a8$84cd5c40$8e6814c0$@olddog.co.uk>
From: Loa Andersson <loa@pi.nu>
Message-ID: <dd82b5f5-9844-c4bf-b24c-00d768aa05a0@pi.nu>
Date: Sun, 31 Mar 2019 22:21:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <002a01d4e7a8$84cd5c40$8e6814c0$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-3272bis-design-team/RiLBn_5VV10cC1uWdsG1ORk7_6k>
Subject: Re: [teas-3272bis-design-team] existing references in 3272
X-BeenThere: teas-3272bis-design-team@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <teas-3272bis-design-team.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-3272bis-design-team/>
List-Post: <mailto:teas-3272bis-design-team@ietf.org>
List-Help: <mailto:teas-3272bis-design-team-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2019 20:21:18 -0000
Adrian, Yes - I agree about have to look at the obscure references once more. What was intended with the first round was to make sure that the existing references actually met the requirement on stability. Meaning if there is a reference in the text that we think should be kept we are sure that as a reference it is usable. Meaning that the reference that I updated from "Work in progress" to "RFC" is IK to keep if we want that, and that is no problem to remove if we want that. /Loa On 2019-03-31 12:00, Adrian Farrel wrote: > Loa, > > For some of the more obscure references, it may be worth looking at whether they are referenced by some of the more obscure text. > > If we are going to delete the text then you obviously won't have to worry about the references š > > A > > -----Original Message----- > From: Teas-3272bis-design-team <teas-3272bis-design-team-bounces@ietf.org> On Behalf Of Loa Andersson > Sent: 29 March 2019 09:09 > To: teas-3272bis-design-team@ietf.org > Subject: [teas-3272bis-design-team] existing references in 3272 > > Folks, > > I gone through the all references once. > > None the referenced RFCs has been obsoleted. > > One reference to an ID > > [DIFF-TE] Le Faucheur, F., Nadeau, T., Tatham, M., Telkamp, T., > Cooper, D., Boyle, J., Lai, W., Fang, L., Ash, J., Hicks, > P., Chui, A., Townsend, W. and D. Skalecki, "Requirements > for support of Diff-Serv-aware MPLS Traffic Engineering", > Work in Progress, May 2001. > > is now RFC 4214, I have update that one. > > For all the references to non-IETF documents it is possible to find > proof of existence e.g. via a Google search, though some of the points > to books that I'm not sure still is for sale. > > What do we do ? > > THe is one reference to [MATE]: > > [MATE] A. Elwalid, C. Jin, S. Low, and I. Widjaja, "MATE: MPLS > Adaptive Traffic Engineering", Proc. INFOCOM'01, Apr. > 2001. > > But there is also an un-published ID: > > Internet Engineering Task Force Indra Widjaja > Fujitsu Network Communications > INTERNET DRAFT Anwar Elwalid > Expired in six months Bell Labs, Lucent Technologies > August 1998 > > > MATE: MPLS Adaptive Traffic Engineering > <draft-widjaja-mpls-mate-00.txt> > > Do we want to add the ID? > > /Loa > -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64
- [teas-3272bis-design-team] existing references inā¦ Loa Andersson
- Re: [teas-3272bis-design-team] existing referenceā¦ Loa Andersson
- Re: [teas-3272bis-design-team] existing referenceā¦ Adrian Farrel
- Re: [teas-3272bis-design-team] existing referenceā¦ Jeff Tantsura
- Re: [teas-3272bis-design-team] existing referenceā¦ Adrian Farrel
- Re: [teas-3272bis-design-team] existing referenceā¦ Loa Andersson