RFC 7818 on URN Namespace for MEF Documents

rfc-editor@rfc-editor.org Thu, 31 March 2016 00:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F2C12D558 for <ietf-announce@ietfa.amsl.com>; Wed, 30 Mar 2016 17:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVFsCdeRE24Q for <ietf-announce@ietfa.amsl.com>; Wed, 30 Mar 2016 17:52:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C7E512D512 for <ietf-announce@ietf.org>; Wed, 30 Mar 2016 17:52:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A7C1E180011; Wed, 30 Mar 2016 17:52:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7818 on URN Namespace for MEF Documents
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160331005211.A7C1E180011@rfc-editor.org>
Date: Wed, 30 Mar 2016 17:52:11 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/c9Ml2tJcybdDvN98-RnGQrpmfSQ>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2016 00:52:48 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7818

        Title:      URN Namespace for MEF Documents 
        Author:     M. Jethanandani
        Status:     Informational
        Stream:     IETF
        Date:       March 2016
        Mailbox:    mjethanandani@gmail.com
        Pages:      5
        Characters: 8564
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mahesh-mef-urn-02.txt

        URL:        https://www.rfc-editor.org/info/rfc7818

        DOI:        http://dx.doi.org/10.17487/RFC7818

This document describes the Namespace Identifier (NID) "mef" for
Uniform Resource Names (URNs) used to identify resources published by
MEF Forum (https://www.mef.net).  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.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC