Re: Last Call: Administratively Scoped Multicast to BCP

To: Masataka Ohta <mohta at necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: Administratively Scoped Multicast to BCP
From: Harald Alvestrand <Harald.Alvestrand at maxware.no>
Date: Mon, 18 May 1998 11:11:39 +0200
Cc: ietf at ietf.org
Delivery-date: Mon, 18 May 1998 06:41:51 -0400
In-reply-to: <199805151531.AAA01084@necom830.hpcl.titech.ac.jp>
References: <3.0.2.32.19980515142211.00c72940@127.0.0.1>

At 00:31 16.05.98 JST, Masataka Ohta wrote:
>When was it decided? Recently, there was a claim by Randy Bush
>that some proposed BCP is not a current practice that I don't
>think there is a consensus.

The first example of a BCP specifying an administrative procedure
(and something that was not a current practice before its publication)
is BCP 1, RFC 1818, which defined the term.

                     Harald T. Alvestrand

-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand at maxware.no

References:
- Re: Last Call: Administratively Scoped Multicast to BCP
  - From: Harald Alvestrand
- Re: Last Call: Administratively Scoped Multicast to BCP
  - From: Masataka Ohta

Prev by Date: Re: Last Call: Administratively Scoped Multicast to BCP
Next by Date: Last Call: POP3 Extension Mechanism to Proposed Standard
Previous by thread: Re: Last Call: Administratively Scoped Multicast to BCP
Next by thread: TCP and SACK
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Last Call: Administratively Scoped Multicast to BCP

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.