PS and AS (Re: [newtrk] new cruft draft due out today or tomorrow)

[Harald Tveit Alvestrand <[e-mail]>]

--On torsdag, september 16, 2004 09:10:06 +0300 Pekka Savola 
<[e-mail]> wrote:

>> Nit - ASes are supposed to be standards-track, not Informational. See
>> RFC  2026. However, some "applicability statements" are not what 2026
>> envisioned.
>
> Counter-nit: such protocols couldn't advance past PS if the AS was PS,
> unless AS was advanced at the same time. (Looking at the status from
> RFC-editor search page, it seems there are a couple of standards track
> AS's and a bit over a dozen Informational AS's.)

The way 2026 described ASes, ASes would refer to the protocols; the 
protocols would not refer to the AS. So the protocol could advance; 
certainly OSPF has managed to advance while leaving its applicability 
statement (RFC 1370) behind....

The following RFCs have "applicability statement" in their title:


1370 Applicability Statement for OSPF. Internet Architecture Board, L.
     Chapin. October 1992. (Format: TXT=4303 bytes) (Status: PROPOSED
     STANDARD)

1517 Applicability Statement for the Implementation of Classless
     Inter-Domain Routing (CIDR). Internet Engineering Steering Group, R.
     Hinden. September 1993. (Format: TXT=7357 bytes) (Status: PROPOSED
     STANDARD)

1722 RIP Version 2 Protocol Applicability Statement. G. Malkin.
     November 1994. (Format: TXT=10236 bytes) (Also STD0057) (Status:
     STANDARD)

1923 RIPv1 Applicability Statement for Historic Status. J. Halpern, S.
     Bradner. March 1996. (Format: TXT=5560 bytes) (Status: INFORMATIONAL)

2005 Applicability Statement for IP Mobility Support. J. Solomon.
     October 1996. (Format: TXT=10509 bytes) (Status: PROPOSED STANDARD)

2081 RIPng Protocol Applicability Statement. G. Malkin. January 1997.
     (Format: TXT=6821 bytes) (Status: INFORMATIONAL)

2333 NHRP Protocol Applicability Statement. D. Cansever. April 1998.
     (Format: TXT=20164 bytes) (Status: PROPOSED STANDARD)

2721 RTFM: Applicability Statement. N. Brownlee. October 1999.
     (Format: TXT=21200 bytes) (Status: INFORMATIONAL)

3197 Applicability Statement for DNS MIB Extensions. R. Austein.
     November 2001. (Format: TXT=8610 bytes) (Status: INFORMATIONAL)

3210 Applicability Statement for Extensions to RSVP for LSP-Tunnels.
     D. Awduche, A. Hannan, X. Xiao. December 2001. (Format: TXT=17691
     bytes) (Status: INFORMATIONAL)

3213 Applicability Statement for CR-LDP. J. Ash, M. Girish, E. Gray,
     B. Jamoussi, G. Wright. January 2002. (Format: TXT=14489 bytes)
     (Status: INFORMATIONAL)

3257 Stream Control Transmission Protocol Applicability Statement. L.
     Coene. April 2002. (Format: TXT=24198 bytes) (Status: INFORMATIONAL)

3346 Applicability Statement for Traffic Engineering with MPLS. J.
     Boyle, V. Gill, A. Hannan, D. Cooper, D. Awduche, B. Christian, W.S.
     Lai. August 2002. (Format: TXT=33754 bytes) (Status: INFORMATIONAL)

3410 Introduction and Applicability Statements for Internet-Standard
     Management Framework. J. Case, R. Mundy, D. Partain, B. Stewart.
     December 2002. (Format: TXT=61461 bytes) (Obsoletes RFC2570) (Status:
     INFORMATIONAL)

3612 Applicability Statement for Restart Mechanisms for the Label
     Distribution Protocol (LDP). A. Farrel. September 2003. (Format:
     TXT=35677 bytes) (Status: INFORMATIONAL)

3638 Applicability Statement for Reclassification of RFC 1643 to
     Historic Status. J. Flick, C. M. Heard. September 2003. (Format:
     TXT=8676 bytes) (Obsoletes RFC1643) (Status: INFORMATIONAL)


On scanning, for instance, RFC 3257, I find that it gives introductory 
material and advice - nothing that looks like a requirement anywhere.

But so does RFC 1722 (RIPv2), and it is not only standards-track, but full 
standard..... in fact, if you take away the "introduction to RIPv2" 
material, RFC 1722 might be a model for the John/John "this is what the 
standard consists of" document....

Perhaps "applicability statement" is a term for which we need an 
applicability statement....?

                          Harald



.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html