Re: [teas-3272bis-design-team] existing references in 3272

Loa Andersson <loa@pi.nu> Sun, 31 March 2019 20:21 UTC

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
Precedence: list

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