RFC 7067 on Directory Assistance Problem and High-Level Design Proposal

rfc-editor@rfc-editor.org Mon, 25 November 2013 23:10 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id BDE851AE0C6; Mon, 25 Nov 2013 15:10:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id u--i_WVne7KB; Mon, 25 Nov 2013 15:10:02 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5C11AE0BE; Mon, 25 Nov 2013 15:10:02 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1F72D75E01C; Mon, 25 Nov 2013 15:09:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7067 on Directory Assistance Problem and High-Level Design Proposal
From: rfc-editor@rfc-editor.org
Message-Id: <20131125230959.1F72D75E01C@rfc-editor.org>
Date: Mon, 25 Nov 2013 15:09:59 -0800
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 25 Nov 2013 23:10:04 -0000

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

        RFC 7067

        Title:      Directory Assistance Problem and  
                    High-Level Design Proposal 
        Author:     L. Dunbar, D. Eastlake 3rd,
                    R. Perlman, I. Gashinsky
        Status:     Informational
        Stream:     IETF
        Date:       November 2013
        Mailbox:    ldunbar@huawei.com, 
        Pages:      15
        Characters: 34720
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-directory-framework-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7067.txt

Edge TRILL (Transparent Interconnection of Lots of Links) switches
currently learn the mapping between MAC (Media Access Control)
addresses and their egress TRILL switch by observing the data packets
they ingress or egress or by the TRILL ESADI (End-Station Address
Distribution Information) protocol.  When an ingress TRILL switch
receives a data frame for a destination address (MAC&Label) that the
switch does not know, the data frame is flooded within the frame's
Data Label across the TRILL campus.

This document describes the framework for using directory services to
assist edge TRILL switches in reducing multi-destination frames,
particularly unknown unicast frames flooding, and ARP/ND (Address
Resolution Protocol / Neighbor Discovery), thus improving TRILL
network scalability and security.

This document is a product of the Transparent Interconnection of Lots of Links Working Group of the IETF.

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

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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