RFC 8057 on Uniform Resource Name (URN) Namespaces for Broadband Forum

rfc-editor@rfc-editor.org Fri, 20 January 2017 16:17 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 988A81296F8 for <ietf-announce@ietfa.amsl.com>; Fri, 20 Jan 2017 08:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 eR2Xi8s66X7u for <ietf-announce@ietfa.amsl.com>; Fri, 20 Jan 2017 08:17:33 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D49A129487 for <ietf-announce@ietf.org>; Fri, 20 Jan 2017 08:17:33 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 46E44B81266; Fri, 20 Jan 2017 08:17:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8057 on Uniform Resource Name (URN) Namespaces for Broadband Forum
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170120161733.46E44B81266@rfc-editor.org>
Date: Fri, 20 Jan 2017 08:17:33 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UcJm2PS3395n1y6JmF27-0Fo_Wk>
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: Fri, 20 Jan 2017 16:17:35 -0000

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

        
        RFC 8057

        Title:      Uniform Resource Name (URN) Namespaces 
                    for Broadband Forum 
        Author:     B. Stark, D. Sinicrope, W. Lupton
        Status:     Informational
        Stream:     IETF
        Date:       January 2017
        Mailbox:    barbara.stark@att.com, 
                    david.sinicrope@ericsson.com, 
                    wlupton@broadband-forum.org
        Pages:      11
        Characters: 17889
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-bbf-bbf-urn-04.txt

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

        DOI:        10.17487/RFC8057

This document describes the Namespace Identifiers (NIDs) "bbf",
"broadband-forum-org", and "dslforum-org" for Uniform Resource Names
(URNs) used to identify resources published by Broadband Forum (BBF).
BBF specifies and manages resources that utilize these three URN
identification models.  Management activities for these and other
resource types are handled by BBF.


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