RFC 7775 on IS-IS Route Preference for Extended IP and IPv6 Reachability
rfc-editor@rfc-editor.org Mon, 29 February 2016 23:34 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9541F1A0371; Mon, 29 Feb 2016 15:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 UzmkJMGN3JCt; Mon, 29 Feb 2016 15:34:27 -0800 (PST)
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 484DC1A0366; Mon, 29 Feb 2016 15:34:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2E6D718019D; Mon, 29 Feb 2016 15:33:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7775 on IS-IS Route Preference for Extended IP and IPv6 Reachability
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160229233336.2E6D718019D@rfc-editor.org>
Date: Mon, 29 Feb 2016 15:33:36 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/fhtbew3S4VKkSGPfOz9i3jzZkHg>
Cc: drafts-update-ref@iana.org, isis-wg@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: <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: Mon, 29 Feb 2016 23:34:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7775
Title: IS-IS Route Preference for Extended
IP and IPv6 Reachability
Author: L. Ginsberg, S. Litkowski, S. Previdi
Status: Standards Track
Stream: IETF
Date: February 2016
Mailbox: ginsberg@cisco.com,
stephane.litkowski@orange.com,
sprevidi@cisco.com
Pages: 11
Characters: 23624
Updates: RFC 5308
I-D Tag: draft-ietf-isis-route-preference-02.txt
URL: https://www.rfc-editor.org/info/rfc7775
DOI: http://dx.doi.org/10.17487/RFC7775
In existing specifications, the route preferences for IPv4/IPv6
Extended Reachability TLVs are not explicitly stated. There are also
inconsistencies in the definition of how the up/down bit applies to
route preference when the prefix advertisement appears in Level 2
Link State Protocol Data Units (LSPs). This document addresses these
issues.
This document is a product of the IS-IS for IP Internets Working Group of the IETF.
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
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