[Idr] FW: RFC 8093 on Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243

"Susan Hares" <shares@ndzh.com> Thu, 16 February 2017 18:30 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B37AA1295EC for <idr@ietfa.amsl.com>; Thu, 16 Feb 2017 10:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1wsgORxaLsnS for <idr@ietfa.amsl.com>; Thu, 16 Feb 2017 10:30:24 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72141294F5 for <idr@ietf.org>; Thu, 16 Feb 2017 10:30:23 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
References: <20170216182405.7CE56B81548@rfc-editor.org>
In-Reply-To: <20170216182405.7CE56B81548@rfc-editor.org>
Date: Thu, 16 Feb 2017 13:25:27 -0500
Message-ID: <04fa01d28882$0c5f1690$251d43b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG1BqrGT4DXH1NWQ0ymUKZDqy+T3qGm9ndg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/8G1xQcHGSlxSBo6pVJ-N8KsQ-TQ>
Subject: [Idr] FW: RFC 8093 on Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:30:26 -0000

Congratulation WG  and Job Snijders on getting this protection to RFC

Sue Hares 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of
Sent: Thursday, February 16, 2017 1:24 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: drafts-update-ref@iana.org; idr@ietf.org; rfc-editor@rfc-editor.org
Subject: [Idr] RFC 8093 on Deprecation of BGP Path Attribute Values 30, 31,
129, 241, 242, and 243

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

        RFC 8093

        Title:      Deprecation of BGP Path Attribute 
                    Values 30, 31, 129, 241, 242, and 243 
        Author:     J. Snijders
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2017
        Mailbox:    job@ntt.net
        Pages:      3
        Characters: 5494
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-deprecate-30-31-129-02.txt

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

        DOI:        10.17487/RFC8093

This document requests IANA to mark BGP path attribute values 30, 31, 129,
241, 242, and 243 as "Deprecated".

This document is a product of the Inter-Domain Routing Working Group of the

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  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 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

The RFC Editor Team
Association Management Solutions, LLC

Idr mailing list