RE: draft-ietf-ccamp-gmpls-egress-control-00.txt

["Vishal Sharma" <v.sharma@ieee.org>]

Adrian,


> -----Original Message-----
> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> Behalf Of Adrian Farrel
> Sent: Thursday, April 08, 2004 3:29 PM
> To: Ong, Lyndon
> Cc: ccamp@ops.ietf.org; 'Lou Berger'
> Subject: Re: draft-ietf-ccamp-gmpls-egress-control-00.txt
>
>
> Hi Lyndon,
>
> First note that this draft does not update the protocols and
> procedures of RFC3473. It
> restates them more explicitly.
>
> If you look at the RFC index
> (http://www.ietf.org/iesg/1rfc_index.txt) you'll see there is
> very little precedent for this type of work.
> We can find BCP 75 and 76 ( and
> http://www.ietf.org/rfc/rfc3666.txt) which could sort of
> be said to update (or at least qualify) RFC 3261 and RFC 3264.
> Neither is listed with an "updates" clause.
>
> Nor does RFC 3481 (BCP 71) have any back/forward pointer with the
> TCP standard.
>
>
> However, I take your point: how does someone wanting to know
> everything about GMPLS know
> to read this new document?
>
> We will look to see how this can be managed.
>
> In return can you tell me: how does anyone wanting to see all of
> the RFCs related to (say)
> TCP find them all?

I guess that's when one consults either Stevens' tome, or one of Peter
Loshin's "Big Book of X RFCs" where "X" = technology or protocol in
question. :-)
(I am not actually sure whether he has a big book of TCP/IP RFCs.)

-Vishal