Last Call: <draft-mahesh-mef-urn-01.txt> (URN Namespace for MEF Documents) to Informational RFC

The IESG <> Thu, 07 January 2016 14:24 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 650C81A8A9D; Thu, 7 Jan 2016 06:24:12 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-mahesh-mef-urn-01.txt> (URN Namespace for MEF Documents) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 07 Jan 2016 06:24:12 -0800
Archived-At: <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Jan 2016 14:24:12 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'URN Namespace for MEF Documents'
  <draft-mahesh-mef-urn-01.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-02-04. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   This document describes the Namespace Identifier (NID) 'mef' for
   Uniform Resource Names (URNs) used to identify resources published by
   MEF Forum (  MEF specifies and manages resources
   that utilize this URN identification model.  Management activities
   for these and other resources types are handled by the manager of the
   MEF Assigned Names and Numbers (MANN) registry.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.