Re: RFC 2026 interpretation question

From: Keith Moore <moore at network-heretics.com>
To: dcrocker at bbiw.net
Cc: Lisa Dusseault <lisa at osafoundation.org>, Tony Hansen <tony at att.com>, ietf at ietf.org, sob at harvard.edu, John C Klensin <klensin at jck.com>, Pete Resnick <presnick at qualcomm.com>
Date: Thu, 02 Oct 2008 07:40:54 -0400
In-reply-to: <48E4197F.7020204 at dcrocker.net>
References: <F59D0E0653D1A97C2E9D0145 at p3.int.jck.com> <48E4197F.7020204 at dcrocker.net>

> First question is:  Why have any delay at all?  I presume the answer has
> to do with broader community exposure -- review and maybe experience,
> although 4 months is not enough for serious experience.
> 
> If indeed that reason is right, it seems that distribution doesn't
> happen until the RFC is officially announced.  Until that moment, the
> document is subject to some change.  So that's when broader public
> exposure starts.

concur.

Keith
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

References:
- RFC 2026 interpretation question
  - From: John C Klensin
- Re: RFC 2026 interpretation question
  - From: Dave CROCKER

Prev by Date: Re: Secdir Review of draft-stjohns-sipso-05
Next by Date: Re: Secdir Review of draft-stjohns-sipso-05
Previous by thread: Re: RFC 2026 interpretation question
Next by thread: Re: RFC 2026 interpretation question
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: RFC 2026 interpretation question

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