works for me --- >From ietf-bounces@xxxxxxxx Wed Dec 22 04:42:35 2004 X-Original-To: sob@xxxxxxxxxxxxxxxxxx Delivered-To: sob@xxxxxxxxxxxxxxxxxx Date: Wed, 22 Dec 2004 10:20:15 +0100 From: Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx> To: ietf@xxxxxxxx X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at alvestrand.no X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Subject: Consensus? Minor issue #743: Defining the IETF X-BeenThere: ietf@xxxxxxxx X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion <ietf.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@xxxxxxxx?subject=unsubscribe> List-Post: <mailto:ietf@xxxxxxxx> List-Help: <mailto:ietf-request@xxxxxxxx?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@xxxxxxxx?subject=subscribe> Sender: ietf-bounces@xxxxxxxx Errors-To: ietf-bounces@xxxxxxxx I'm trying to go through the list of open issues and resolve those that appear "easy", and this one caught my eye: > maybe define the IETF - maybe point to RFC 3233 Suggested resolution: Add to section 2.1 "Alphabet Soup": IETF: Internet Engineering Task Force (see [RFC3233]) _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf