Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt

To: sob at harvard.edu (Scott Bradner)
Subject: Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt
From: Sam Hartman <hartmans-ietf at mit.edu>
Date: Thu, 14 Jul 2005 18:12:40 -0400
Cc: ietf at ietf.org
In-reply-to: <20050714165238.9899741F6D8@newdev.harvard.edu> (Scott Bradner's message of "Thu, 14 Jul 2005 12:52:38 -0400 (EDT)")
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <20050714165238.9899741F6D8@newdev.harvard.edu>
Sender: ietf-bounces at ietf.org
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

would it be reasonable to just say that we are going to always last
call IETF review documents?  Personally I'd approve of this option
unless people think it is too restrictive.


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

Follow-Ups:
- Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt
  - From: Scott Bradner

References:
- Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt
  - From: Scott Bradner

Prev by Date: [Sipping] [Fwd: I-D ACTION:draft-hilt-sipping-session-spec-policy-03.txt]
Next by Date: RE: [Ltru] Compatibility (Was: Last call: Private UseTags)
Previous by thread: Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt
Next by thread: Re: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt
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: I-D ACTION:draft-narten-iana-considerations-rfc2434bis-02.txt

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